When a merger, acquisition, or divestiture is announced, the spotlight is usually on the strategic story.
Market expansion. Portfolio optimisation. Synergies. Shareholder value.
Behind closed doors, deal teams are working intensely on valuation models, legal structures, and regulatory approvals. Leadership teams focus on how the new organisation will operate once the transaction is complete.
Technology rarely sits at the centre of these discussions.
And yet, once the deal is signed, it often becomes the hardest problem to solve.
Where the real complexity begins
In large enterprises, ERP systems sit at the centre of how the organisation actually runs. Finance reporting, procurement, supply chain operations, manufacturing processes, and compliance controls are all deeply connected through the same digital core.
Over time, these systems evolve into highly integrated environments. Multiple legal entities may share the same ERP instance. Business units that look independent on an organisational chart may rely on shared data structures, reporting frameworks, and operational processes inside the same system landscape.
This works well when the organisation remains intact.
It becomes far more complicated when the structure of the business changes.
When a company sells a division, spins off a business unit, or acquires another organisation, those shared systems suddenly need to be separated, replicated, or reorganised. Data structures that support several entities may need to be redesigned. Reporting environments must remain stable even as the underlying systems change.
And this often needs to happen under strict deal timelines.
Why ERP challenges appear late
One reason ERP complexity catches organisations by surprise is timing.
In many transactions, technology teams are brought into the conversation only after the deal structure is already defined. By that point, legal agreements are signed, Day-One deadlines are set, and the operational expectations of the new organisation are already clear.
What becomes visible at that stage is the gap between the business structure of the deal and the technical reality of the systems that support it.
Separating a business entity on paper may take weeks.
Separating it inside an ERP system can take months if the dependencies are not fully understood.
When technology risk becomes business risk
This is where technology stops being a purely IT concern.
If ERP systems cannot be separated cleanly, finance reporting may be affected. Regulatory obligations may become harder to fulfil. Supply chains and operational processes may experience disruption. Integration timelines can extend far beyond what deal teams originally expected.
In other words, ERP complexity can quickly become a business continuity risk.
This does not mean that mergers, acquisitions, and divestitures are inherently problematic from a systems perspective. Organisations execute these changes successfully every year. But the most successful programmes share a common mindset.
They recognise early that enterprise systems are not just operational tools. They are structural components of the business itself.
Treating ERP as part of the deal strategy
When ERP landscapes and enterprise data structures are considered earlier in the transaction process, organisations gain much greater control over execution.
Dependencies between business entities become visible sooner. Separation or integration scenarios can be evaluated earlier. Technology teams can design approaches that protect operational continuity while still supporting the strategic intent of the deal.
This shift in thinking is becoming increasingly important.
Modern ERP environments support far more than financial accounting. They underpin operational processes, regulatory reporting, supply chain coordination, and increasingly the data foundations that support analytics and AI.
Changing the structure of the business inevitably means changing the structure of the systems that run it.
For organisations navigating mergers, acquisitions, or divestitures, the real question is no longer just how to close the deal.
It is how to execute the change without destabilising the systems that keep the business running.
Over the coming weeks, the ONE.Ascent campaign will explore how enterprises approach ERP change during structural events such as mergers, acquisitions, and divestitures, and what separates high-risk programmes from those executed with confidence.
Continue the Conversation
If your organisation is navigating a merger, acquisition, carve-out, or divestiture, join our upcoming ONE.Ascent executive webinar where we explore the practical realities of managing ERP change during structural transformation.
Register for the session or explore the ONE.Ascent campaign hub to see how enterprises across the Asia Pacific are approaching modernisation with greater clarity and control.
Benjamin Ng
Head of Marketing, cbs Asia Pacific
As Head of Marketing, Asia Pacific at cbs Corporate Business Solutions. Benjamin focuses on enterprise modernisation strategy across SAP landscape transformation, data-driven innovation, and AI-enabled business models. He works closely with regional leaders and ecosystem partners to shape outcome-led transformation programmes across APAC.
