Don't replace the ERP. Surround it.
Every mid-market company hits this wall: the ERP runs the books but can't run the operation. The expensive answer is a rip-and-replace. We chose a different one — and it kept paying off for a decade.
The ERP answered "what is financially true" — and nothing else
Our client's ERP held customer master data, accounting, billing, and enterprise identifiers. It did that well — auditors knew it, finance trusted it. But a medical equipment repair operation asks different questions: Where is this device? Has the customer approved the quote? Did final QC pass? Which loaner replaced it? The ERP had no answers, and no realistic way to grow them.
ERP answered "What is financially true?" The platform answered "What is operationally happening right now?" Keeping those concerns separate is why both systems thrived.The architectural principle behind the whole engagement
Three paths. Two rejected.
The obvious options were the expensive ones. Here's the reasoning, as we presented it to the client's leadership.
Replace the ERP
Migrate everything — financials included — onto one new platform.
Customize the ERP
Build the repair workflows inside the ERP vendor's ecosystem.
Operational platform + integration
The ERP stays authoritative for finance and master data. A custom platform owns every operational workflow. Synchronization connects the two.
Clear ownership, disciplined boundaries
Integration succeeds or fails on one thing: knowing which system owns which data. We made that explicit from day one.
The ERP kept owning
- Financial accounting and billing
- Enterprise master data
- Corporate identifiers and audit surface
- What auditors and finance teams already knew
The platform took ownership of
- The complete repair lifecycle, intake to shipment
- Quality control, quoting, and customer approvals
- Customer and vendor collaboration portals
- Loaners, reverse logistics, field service, BI
Idempotent by design
Synchronization tolerated interrupted communication and could be safely re-run — reliability took priority over novelty in every integration decision.
One extra benefit nobody planned
Auditors kept working in the ERP they already knew. No retraining, no custom-system walkthroughs — a quiet but real cost saving, year after year.
Room to grow on both sides
The ERP evolved on the vendor's schedule; the platform evolved on the business's schedule. Neither ever blocked the other.
The boundary that held for a decade
Trying to force every business process into an ERP creates complexity. Letting specialized systems own specialized domains — connected through disciplined boundaries — creates adaptability.Why this platform survived even an acquisition-driven migration plan
More from this engagement
The platform its acquirer couldn't replace
The full eight-year story: 700k+ work orders, 2,000+ users, portals, contracts, BI — and the migration that never happened.
Read the story → Solution storySoftware for places where the internet doesn't reach
150+ van technicians, atomic snapshot sync, zero partial states — offline-first field service done right.
Read the story → Solution storyStaying fast at 700,000 work orders
Working vs. history tables — the lifecycle-aware data architecture that kept screens sub-second for eight years.
Read the story →Workflows trapped in — or around — a legacy ERP?
We map what the ERP should keep, what it shouldn't, and how to build the operational layer your team actually needs.
Book a Strategy Call