"We haven't touched it." That was one converter’s answer when we asked what happened to the business systems of the companies they acquired.
It is an understandable answer. The acquired plant was profitable when you bought it. Its people know their system. A migration means disruption, training, and risk during the exact months when you are trying to prove the deal was a good idea. Leaving the ERP or MIS alone feels like the safe choice.
It is not free, though. The cost just shows up somewhere else: in the finance team’s month-end, in the estimator’s inbox, in the scheduling call between plants that never quite happens. The question is whether leaving the systems separate costs more than bringing them together.
Where the cost shows up
Software and support appear in the budget. The work of bridging systems is harder to see. It shows up in five places.
Reporting. This is the one everyone notices first. An IT director at a multi-site label converter described the routine: “Someone has to compile data from all of those systems into consolidated sales reporting.” Every month, someone exports from each system, reconciles customer names and product codes that don’t match, and builds the roll-up by hand. Leadership gets numbers that are weeks old and still not quite comparable.
Quoting. Two systems can mean two cost models. The acquired plant quotes on its historical standards, your plants quote on yours, and the same job can come out at different prices depending on which site the salesperson calls. Different machines, freight lanes and capacity can justify different prices. The problem is when the group cannot explain the differences or apply consistent margin rules.
Scheduling. If the deal depends on using plants as one network, you need to move work to the site with the right machine, the open capacity, or the shorter freight lane. That requires a reliable view of capacity across sites. Without it, moving work depends on phone calls between production managers, and opportunities can be missed.
Inventory. Board, inks, tooling, and finished goods at the acquired site can be hard for the rest of the group to see. You risk duplicate stock and missed opportunities to share compatible tooling. It becomes difficult to answer a simple question like “how much of this grade do we have across all sites?” without three phone calls.
Finance. Separate charts of accounts, separate cost centers, separate period closes. The combined P&L is a spreadsheet exercise, and audit-ready consolidated numbers take longer every quarter. For a private-equity-backed group reporting to a board, this is the leak that gets noticed.
It compounds
One extra system is an inconvenience. Five is a different business.
The label converter we quoted above has made five acquisitions. Each one came with its own MIS, and each time, the decision was the same: leave it. Individually, every one of those decisions was defensible. Collectively, the group now runs multiple instances, and the IT director’s question has changed: “Now that we’re running multiple instances, we’re wondering: is there value in consolidating?”
The work grows with each system added: more customer codes to reconcile, more cost standards to compare, more interfaces to maintain. The scale depends on how the systems connect, but the burden often lands on experienced finance and IT staff. Those hours come out of other improvement projects.
There is a second-order cost too. When data is hard to assemble, leadership can’t ask useful questions. Which plant is most profitable per machine hour? Which customers are we serving from the wrong site? Where is waste trending the wrong way? Answers arrive too late to guide the next week’s decisions.
A corrugated executive described the same trap from the other end, while looking at a recently acquired plant’s legacy platform: “We’re looking at their systems right now trying to figure out: what can we extract? What data do we need to create the information we want?” The data exists. Getting it into a form the group can use is the work.
What the research says
Research reinforces the need to decide what the combined business will share.
PwC’s 2026 survey says integration choices should follow the deal’s value case, including what to combine or keep separate. Its sample covers businesses with at least $1 billion in revenue, rather than packaging SMEs.
McKinsey’s 2019 analysis found that more than half of synergies in many industries depended on the IT blueprint. That does not prescribe one system architecture. It makes systems planning part of the investment case.
The mechanism is simple. Procurement leverage, network scheduling, cross-selling, and overhead consolidation are the synergies that justify a packaging acquisition. Each needs usable data across the group. If the systems stay separate, the plan must explain how that data will be shared and who will maintain it.
Consolidate, connect, or leave it
There are three options after an acquisition, and each has a place.
Leave it. Right when the acquired business is small, operationally separate, and will stay that way. A niche specialty plant serving its own customers with its own equipment may not need to share anything but a P&L line. The test is whether you ever expect to move work, stock, or customers between it and the rest of the group. If not, keeping it separate may be the better choice, provided reporting and support costs remain manageable.
Connect it. Keep the systems separate and integrate the data and processes the group needs. A reporting layer can simplify consolidation; deeper integrations can also support quoting, inventory and planning. The trade-off is the cost of building, governing and maintaining those connections.
Consolidate. Move the acquired plant onto the group’s platform as one more site in a single multi-plant instance. This can address all five sources of friction, provided the plants adopt common data and working practices. One converter described the advantage of buying a business on the same system: “It makes it a lot easier to do integration.” The cost is a real migration project, which is why the next post in this series covers technology due diligence before you sign, so you plan the migration rather than discover it.
Cloud hosting can reduce another part of that cost: separate ERP servers and their upkeep. Hosting disconnected systems in the cloud, however, leaves the data and process gaps to solve.
The choice depends on the role of the acquired plant. If the deal thesis was to run it as part of the network, compare the full cost and capability of connecting the systems with moving to a shared platform.
Six questions before you decide
If you are weighing whether to consolidate an acquired plant, these are the questions that surface the real cost of the status quo:
- How many hours a month does finance spend building consolidated reports, and how old are the numbers by the time leadership sees them?
- Can a salesperson compare the cost of producing the same job at different plants and apply the group’s margin rules?
- When one plant is overloaded, how long does it take to move work to another, and how often does it actually happen?
- Can you see inventory of a given board grade or tooling across all sites right now, without calling anyone?
- How many people in the group know how to operate the acquired plant’s system, and what happens when they leave?
- What did the deal model assume about synergies, and which of those can you prove you have captured?
Put a number against the answers: reporting hours, duplicate stock, support costs and benefits delayed. Then compare that annual cost with the cost and disruption of change.
Next in the series
The best time to answer those questions is before the deal closes. The next post covers technology due diligence: what to look at in a target’s systems, data, and processes before you sign, so that consolidation is a plan rather than a surprise.
Running more than one business system?
Other posts in the series
- Packaging M&A in 2026: Faster Integration Is the New Edge
- The hidden cost of running multiple ERP or MIS instances, and what “we haven’t touched it” actually costs over five acquisitions.
- Technology due diligence: what to look at in a target’s systems before you sign.
- M&A speed as the payoff: how a single multi-plant platform changes the integration timeline.
- Becoming acquisition-ready: what sellers can do now to look like a low-risk target in a selective market.
Sources
- PwC: 2026 M&A Integration Survey (September 29, 2026; architecture choices should follow the deal thesis; respondents from businesses with at least $1 billion in annual revenue). https://www.pwc.com/us/en/services/consulting/deals/library/ma-integration-survey.html
- McKinsey: Eight basic beliefs about capturing value in a merger (April 2, 2019; IT blueprint and synergy capture across industries). https://www.mckinsey.com/capabilities/people-and-organization/our-insights/eight-basic-beliefs-about-capturing-value-in-a-merger
- Amtech: Cloud Hosting (managed infrastructure and adding plants without additional ERP servers). https://www.amtechsoftware.com/services/cloud-hosting/
