One Group, Five ERPs

The deal gets celebrated properly. There is a press release, a photo, a line about scale and synergy, and a genuine sense that the company just got bigger and stronger. It usually did.

Then, a few months later, comes the quieter meeting. Leadership wants a simple combined picture. What was our total output and our reject rate last month across the original plants and the one we just acquired? And the answer comes back slowly, because the acquired plant records all of that in its own system, with its own codes, in its own format. Someone will have to map it by hand first.

You bought the company. Nobody mentioned you were also buying their spreadsheets.

Every deal adds a dialect

When you acquire a business or form a joint venture, you do not just inherit a factory, a team, and an order book. You inherit an entire way of recording reality. The acquired plant has its own ERP, or its own registers, or its own mix of both. It has its own name for a shade of defect, its own way of logging downtime, its own definition of a completed order.

The financial side of this gets attention, because it has to. Auditors and consolidation rules force the books to line up within a deadline. Nobody sends a legal notice about operational data. So the shop-floor side quietly slips down the list. The acquired plant keeps producing, keeps reporting the way it always has, and everyone moves on to the next priority.

Do this two or three times, which is exactly what a growing group does, and you end up with one logo, one board, one strategy, and five different ways of counting a reject.

The synergy you paid for, still on paper

Here is the part that stings. The case for most deals assumes you can see across the whole group. Shared best practice. Balanced loads across plants. A combined view of quality and delivery for customers who now buy from more than one of your sites. That was in the model.

In reality, for months and sometimes years, you cannot compare the acquired plant to your own on equal terms, so you cannot tell whether the operational synergy is actually landing. A better method at the parent plant does not travel to the new one, because the two measure themselves differently and nobody can line them up. A problem in the new unit surfaces late, through a customer complaint rather than a number. The value was real. It is just stuck behind a translation problem nobody was assigned to solve.

Two familiar answers, both heavy

Faced with this, most groups reach for one of two options.

The first is rip-and-replace: force the acquired plant onto the parent's ERP. It is thorough, and it is brutal. It is expensive, it takes twelve to eighteen months, it disrupts a plant that was working fine, and it is often resisted by the people who ran that plant successfully for years. Worse, during that long migration, you are more blind, not less.

The second is to leave the acquired plant alone. It stays productive and happy, and it stays a silo. Putting a BI dashboard on top does not help, because it faithfully shows two sets of numbers that were never defined the same way, side by side, still not comparable.

Neither option is wrong. They simply answer the question how do we standardise our systems. That is a real question, but it is not the one leadership is actually asking, which is how do we see across the whole group next month.

You do not need one ERP to get one view

The shift is to stop treating this as a systems migration and start treating it as a translation problem, because that is what it is.

Let each plant keep the systems that work for it. Capture the operational data each entity already produces, and curate it into a shared language, so that a reject, a delay, and a produced unit mean the same thing whether they come from the plant you built or the plant you bought. That gives you a consolidated view of production, quality, and delivery across the group in weeks, without ripping out anything that is working and without asking a productive plant to down tools for a year.

This is worth being precise about. It is decision support that sits above the plant-level systems. It does not replace the acquired plant's ERP, and it does not run either operation. It reads them both, at once, in one language. Consolidation without the rip-and-replace.

Questions for your next integration review

• If I asked for combined output and quality across our original plants and our most recent acquisition right now, how long would the answer take?
• Does a reject, a delay, and a completed order mean the same thing in the plant we built and the plant we bought?
• Are we currently planning a full systems migration for an acquired unit, and how many months will we be partly blind while it runs?
• Which best practice from our strongest plant has actually reached the acquired one, and can we prove it moved the numbers?
• When we modelled this deal, how much of the synergy assumed a group-level view we do not yet have?

The real test of an acquisitive group

Every deal is celebrated for what it adds to the top line. The quieter truth is that it also adds a dialect to how your company sees itself, and those dialects pile up faster than anyone plans for.

The groups that genuinely win from acquisitions are not the ones with the fewest ERPs. That race is unwinnable and beside the point. They are the ones who can read all of their systems at once, and turn five ways of counting into one view of the whole. Until you can do that, an acquisition adds a plant to your group and a blind spot to your map.

If your group has grown by acquisition, it may be worth looking at how manufacturers are getting one consolidated view across mismatched systems without a multi-year migration. Explore our use cases on unifying operational data across newly acquired plants.

FAQ