The plant you just bought runs a different system. Decide what the platform has to fit before you pick one.
By Chris McCarthy, Founder & Chief AI Officer, OB.1
When an acquisition brings a second ERP, the fastest path to value is usually a shared view of the data across both systems, with a full consolidation decided later on its own business case. The question that sorts it out: does the platform fit what you're building? Answer it by writing down what the combined company has to do, then testing every platform against that list.
This is part three of our Pilot to Production series. This one is for owners and executives growing by acquisition.
Two plants, two systems, one set of promises
The deal model promised savings. Shared purchasing. One inventory picture. Combined scheduling. Then the integration team opens the new plant's systems and finds a different ERP, different part numbers, and a different way of closing the month.
Integration takes longer than the deal model assumes. EY-Parthenon research found that up to 70% of technology synergies are realized 18 to 36 months after a deal closes.
The usual answer is a full re-platform onto one ERP. That can be the right call. It is also long and expensive, and every month it runs is a month the savings the deal was supposed to deliver stay on paper.
Why the platform question comes before the platform
Platform decisions after an acquisition tend to follow whoever argues loudest. The acquirer's system wins by default. Or a vendor pitches a new platform that will fix everything at once.
Both skip a step. Neither starts from what the combined company has to do in its first year: which reports leadership needs, which purchasing gets combined first, which customers now span both plants. Without that list, nobody can say whether a platform fits.
More of these integrations are coming. McKinsey's February 2026 analysis of Census data found that more than half of small-business owners are now over 55. The Exit Planning Institute reports that roughly three in four owners of privately held companies plan an ownership transition within ten years. Each of those transitions can put another plant, with another system, into someone's portfolio.
The question to ask: does the platform fit what you're building?
Write down the jobs first. For most add-on integrations, the first-year list looks something like this:
| Job | Why it matters |
|---|---|
| One view of inventory across plants | Avoid buying what the other plant already has |
| Combined purchasing on shared materials | Capture the volume savings in the deal model |
| One customer and item reference | Stop quoting the same part two ways |
| Consolidated monthly reporting | Give owners and lenders one set of numbers |
Then test each option against the list. Some jobs need a shared data layer that reads both ERPs. Some need process changes and no software at all. A few truly need one system. Sorting them is the work.
Where AI fits in an integration
AI is useful here when it does a narrow job well. Matching part numbers and vendors across two item masters is one example. Reading both systems to answer a cross-plant inventory question is another. Both need clean mappings and an owner for each data source.
AI does not replace the integration decision. It can shorten the work inside it, once you know what the combined company is building.
How OB.1 fixes this
The Operational Blueprint maps how work runs at each plant today, with the people who run it. For an integration, that means tracing the first-year jobs across both companies and both systems.
You get the jobs list, ranked by the value the deal promised. You get a platform-fit view for each job, with options from shared data layers to full consolidation. And you get owners for every data source on both sides, so mappings get fixed instead of argued about.
Build partners then work to that spec. OB.1 does not sell software or build hours, so our read on platform fit has no stake in which system wins.
Read the rest of the series
- Costs climb faster than your prices
- Your ERP data sits in silos nobody trusts
- The plant you just bought runs a different system (this article)
- Staff paste pricing into public AI tools
- Your best tech retires, and the fixes leave too
- Automation could ship the wrong order
- Teams lean on the system and lose the judgment to step in
Sources
- EY, How CIOs can supercharge an M&A technology integration, August 2024
- McKinsey Institute for Economic Mobility, The great ownership transfer, February 2026
- Exit Planning Institute, State of Owner Readiness, 2025