Successful merger, ERP in ruins
In an industrial landscape marked by record consolidation in 2025 and 2026, confirmed by the economic results of GIFAS (Groupement des Industries Françaises Aéronautiques et Spatiales), external growth strategies have become an absolute weapon. For Tier 1 and Tier 2 equipment manufacturers, advanced subcontractors (Aerospace, Space, Defense, Automotive) or materials and testing specialists, acquiring production sites is the fastest way to gain capacity and achieve recognition in the market.
Yet, as soon as the champagne glasses are put away, operational reality strikes hard. The group finds itself at the head of a digital patchwork: a mosaic of competing, legacy ERPs, never designed to work together. And it is precisely within this system that drives inventory, purchasing, and production where the actual profitability of the acquisition is played out or collapses. Without an upstream convergence strategy, the synergies promised to investors go up in smoke, replaced by silos that threaten the overall margin.
1. The siloed ERP: the hidden cost secretly sabotaging the profitability of your acquisitions
An ERP is the nervous system of a company: inventory, production orders, purchasing, billing, planning. When each acquired entity clings to its own, the group does not have one information system, it accumulates three or four, completely sealed off from each other. And this lack of alignment does more than just slow the company down: it actively paralyzes the value chain, a critical blind spot while the industry faces historic delivery targets.
Invisible stocks, impossible consolidation: the core of the merger threatened
The siloing of ERPs creates a critical break: the inability to obtain a consolidated view of inventory at the group level. Yet, financial consolidation is the cornerstone of any external growth. When physical asset tracking is relegated to makeshift spreadsheets, the group's entire financial visibility collapses. Beyond operational delays, this disconnect prevents expected synergies from materializing, turning the merger into a managerial and financial abyss.
The immediate cost: mass purchasing becomes impossible
This financial opacity immediately translates on the ground into a cruel paradox: the number one argument for the acquisition, the economies of scale, evaporates. As long as ERPs do not share a common codification, the group is unable to consolidate its volumes. The result? Two separate sites continue to order the same raw material from two different suppliers, at two different prices, completely unknown to headquarters. The scale effect you just paid dearly for during the acquisition remains purely theoretical. Money leaks away, in silence.
Fragmented traceability: the peril of non-compliance
When Manufacturing Execution Systems (MES) or local quality tools remain disconnected from the core central ERP, the product history becomes incomplete. In highly regulated sectors, a gap in traceability is equivalent to a commercial death sentence during a client audit. In the event of a production batch anomaly, the lack of visibility turns crisis management into an ordeal.
Faced with such peril, urgency often pushes the urge to uniformize everything at once. Yet, that is exactly where the trap lies.
The technical assessment: imposing a single ERP in "Big Bang" mode right after an acquisition is the best way to cause an operational stroke. This blocks factories for months and destroys precisely the value and agility you just bought.
2. Ghost stocks, scattered purchases, nightmare audits: the painful truth
To measure the extent of the damage, here is how ERP heterogeneity silently blocks the vital data flows of your production sites.
The blockage of Master Data (Items and Bill of Materials): Without common codification, information is re-entered manually, in duplicate, or even triplicate, from one ERP to another.
The cash impact is immediate: inconsistent databases make it impossible to centralize raw material purchasing. You lose all the scale effect that the acquisition should bring you.
The failure of Planning (S&OP/Master Production Schedule):
When ERPs do not synchronize, multi-site planning migrates to spreadsheets. Every update becomes a manual exercise, prone to version errors and corrupted files. The promise of punctuality made to prime contractors then relies on the vigilance of a few people rather than on a system.
The breakdown in Production Tracking and Traceability: MES and local quality tools end up disconnected from the central ERP.
The product history becomes incomplete: in the event of a production batch anomaly, the time required to identify and correct the problem is multiplied by ten.
3. Don't choose between the Big Bang and inaction!
Akawan connects your ERPs without cutting off the machines
To break this deadlock without risking an industrial blackout, Akawan deploys an agile and pragmatic software urbanization approach, structured around three pillars from its expertise in systems architecture. As we detailed in our previous article on the ERP, PLM and Quality trio after a merger, ERP is never handled alone: together with PLM and the quality system, it forms the three pillars of an industrial IS whose overall consistency determines the success of integration. This article focuses on the first of them, the one most directly linked to cash.
Axis 1: Semantic alignment, or the art of speaking the same language
Before replacing any software, we must impose a common grammar. This is the role of Master Data Management (MDM): an item, a manufacturing bill of materials (MBOM) or an indicator must mean exactly the same thing on all of the group's sites, regardless of local ERPs. Akawan intervenes from this framing phase to model robust and shared data structures.
Axis 2: Interoperability through APIs and Data Hubs (the quiet strength)
The real revolution is not to replace, but to connect intelligently. Akawan designs and deploys modern interoperability layers (APIs, event-driven architectures, industrial Data Hubs). But the challenge is not only technical: strategic thinking must be carried out on how information actually flows between ERPs. No need to saturate a central system with the fine granularity of engineering, or a local site with data that does not concern it. Akawan directly supports your Business, Supply Chain and Procurement teams so that systems only exchange the right information, in the right format and at the right time.
By creating these automated and filtered gateways between ERPs, stocks are consolidated in real time, material requirements are sent in a unified dashboard at group level, and you obtain 360° visibility, without field operators changing their typing habits or daily tools.
Axis 3: Iterative rationalization by value
Total unification remains the long-term target, but it is done in waves. Akawan advocates migration trajectories based on real business value, prioritizing sites with the highest industrial synergies or the highest operational risks. More autonomous entities continue to run on their legacy ERPs, but remain solidly connected to the global integration platform.
4. The 3 well-kept secrets of elite CIOs for successful post-merger integration
Akawan's experience proves it: the success of this monumental project is only 30% technical. The remaining 70% relies on these three pillars.
Commando and cross-functional governance: break the ice between the IT Department, the Industrial Directorate, R&D and the Quality Directorate by bringing them together within a single decision-making steering committee.
Surgical respect for local specificities: standardize only what is mandatory (financial reporting, customer quality indicators, validation processes) and leave breathing room to factories on their essential business specificities.
Change management focused on team relief: we do not sell convergence with abstract concepts. We sell it by showing local teams how it will eliminate double entry, eliminate corrupted Excel files and avoid maximum stress before each audit.
Conclusion: from computer nightmare to war machine
The convergence of ERPs after multiple acquisitions is hell if endured, but it becomes a fearsome competitive advantage if mastered. In a sector that aligns nearly ten years of order books and openly calls for consolidation, knowing how to quickly integrate an acquired entity, without interrupting its production becomes a strategic skill in its own right.
By choosing an agile urbanization approach based on data interoperability, general management and CIOs secure their operations and transform a simple collection of SMEs into an integrated, scalable industrial group ready to absorb the next wave of growth. ERP ceases to be a burden inherited from the buyout and becomes the foundation of the size effect.
About Akawan
Akawan is an independent consulting firm in information systems architecture, digital transformation and agility. It supports organizations in redesigning, urbanizing and modernizing their software ecosystem. Thanks to a strong culture of engineering and "craftsmanship", Akawan helps technical and industrial departments to leverage their business data and secure the long-term future of their infrastructure.

Industrial M&A: The Billion-Dollar Bug
IT architecture secretly dictates the success of your mergers

Why 80% of factory mergers verge on a digital crash
and how to escape it…

The deadly trap of industrial hyper-growth
+28% to +66% in cadence…

Your digital transformation has everything except results.
Your software still doesn't talk to your machines…

Data centralization
The illusion of control, the risk of decline…

53% of MCP servers are hacker nests
Have you given the keys to your company to the whole world?

Heathrow, Brussels, and Berlin paralyzed.
The cause: two unchanged identifiers…

DeepSeek: the app that devours your company...
You hire quickly, your teams adopt AI even faster…

Don't your machines communicate with your information system?
The real cost of industrial "silence"…

Tech in Industry
Facing the challenges of disconnected environments…



