Two ERP Systems After an Acquisition: What to Do?
4 min read
The contract is signed, the consultant is already on the train back home. Now begins the part the purchase agreement barely mentions. The acquired company must keep delivering while headquarters scrambles to impose order. On the managing director’s screen, two ERP systems run side by side, oblivious to each other. The first decision here is not an IT question. It is a test of whether the buyer truly understands what they have just bought. The most dangerous answer is the one that feels the cleanest.
Key Takeaways
- The costly reflex. Migrating the acquired company onto your own system right away feels tidy. Often it destroys exactly what you bought.
- Three paths. Keep running, connect, or migrate. Pure migration belongs in the exception, not the default.
- The real bottleneck. Integration is decided by the key people in the acquired firm, not in the server room.
Related:Buy, Don’t Build / M&A in 2026: Opportunities and Risks at Exit
The reflex that erases purchase value
Most mid-market buyers instinctively reach for migration after closing. The subsidiary lands on the parent’s ERP, one system, one set of numbers, neat and clean. That is the mistake. An acquired company is often bought because it can do something the parent cannot. That something rarely lives in a slide deck; it lives in grown processes and a special logic no manual captures. Overwrite it and you pay the purchase price twice.
Three routes, three consequences
There are three options. What matters is not which sounds tidiest, but which consequence supports the deal.
| Path | Main risk | When it still fits |
|---|---|---|
| Keep running | locks two worlds in place, costs speed and money | short hold, clear separation |
| Connect | requires clear ownership of master data | heterogeneous processes, subsidiary tied to local IT |
| Migrate | grown processes and people are lost | processes can be merged without loss |
In most mid-market acquisitions, keeping the subsidiary running with a fixed end date or connecting it is the less destructive choice. Standardizing feels like control-and that is precisely why it is the most common error.
Four Questions to Ask Before Choosing an ERP System
These four questions can be answered at the kitchen table long before IT drafts a recommendation.
- How long should the acquired company remain independent?
- How different are its processes from those at headquarters?
- What share of its revenue depends on functions your current ERP cannot replicate?
- How quickly must the first consolidated financial statement be ready?
The Bottleneck Isn’t in the Server Room
The IT manager of the subsidiary sits in their office the morning after closing, waiting for a call from headquarters. When none comes, they defend their processes from week two onward instead of opening up. Local quirks live in people’s heads, not in the documentation. Speed isn’t dictated by the project plan; it’s dictated by when the subsidiary’s key people start speaking openly again. Moving too fast drives them out the door; moving too slowly burns cash in dual operations.
How Integration Works in Practice
Companies that choose the middle path integrate the subsidiary as a separate entity while centrally managing only shared master data. One approach is a multi-tenant ERP concept. Multidata, for example, uses separate clients within a shared structure; the subsidiary keeps its order management and only reports shared master data to headquarters. Other firms solve the same point with two instances and middleware in between, or let the subsidiary run entirely separate for a defined holding period.
This approach works when the subsidiary’s processes must stay independent. It fails when everything ultimately needs to be unified-then integration is just an expensive detour to migration.
What Goes Wrong Most Often
Three patterns recur. Migration is treated as a pure IT project with no process owner. Master data is pushed to some future date and collides at the first consolidated close. And the acquired team hears nothing for weeks until uncertainty turns to resistance. None of these failures are technical. Post-acquisition control is correct-but control that destroys the reason for the purchase isn’t integration.
Frequently Asked Questions
Should the acquired company always be migrated onto our system?
No. Migration is only one of three options and fits when processes are highly similar. With distinct processes it often destroys the value you paid for. In those cases, continued operation or integration is the smarter choice.
What does parallel operation really cost?
More than double the licenses. Expensive are the duplicated maintenance of master data, interface errors, and the question of which system is the source of truth. If you choose to continue operating separately, set a clear end date.
Should ERP be part of due diligence?
Absolutely. In many acquisitions IT has no voice in due diligence; balance sheets are examined, not whether the two systems can coexist. Addressing this early reveals integration effort before closing rather than after.
Editor’s Reading Picks
Read more on MyBusinessFuture
MyBusinessFutureWhen Every Order Email Has to be Manually Entered into the ERP SystemMyBusinessFutureInvestment backlog: How AI uncovers hidden budgetsMyBusinessFutureAI-Evaluation Before Succession: Preparing the Sales ValueMore from the MBF Media Network
cloudmagazinGermany Stack Goes Live: €250 Million for the Federal AI CloudDigital ChiefsVMware under Broadcom: The Exit Strategy as a LeverSecurityToday72 Percent of Cyber-defenses Originate AbroadImage source: AI-generated (June 2026)
