When companies decide to sell a business unit or spin off a division, the strategic logic is usually clear.
The organisation wants to sharpen its focus, exit a market, unlock value, or reposition the portfolio. From a corporate strategy perspective, the decision may appear straightforward.
On paper, separating a business unit often looks relatively simple. The organisation identifies the entity being sold, defines the new structure, and prepares the legal and financial framework for the transaction.
But inside the company’s systems, things rarely look that simple.
The difficulty often becomes visible only after the deal begins moving toward execution.
The reality behind shared ERP systems
Most large enterprises operate on ERP platforms that have evolved over many years. These systems were designed to support the organisation as a whole, not individual business units that might one day need to be separated.
Over time, processes become tightly integrated across entities. Finance reporting structures span multiple legal organisations. Supply chain processes operate across shared environments. Master data is reused across divisions and geographies.
What appears to be a distinct business unit from an organisational perspective may actually be deeply embedded inside a shared digital foundation.
This is where the complexity begins.
When a divestiture or carve-out takes place, the organisation must effectively separate part of a business that was never designed to operate independently within the system landscape.
Data entanglement is the real challenge
One of the most underestimated challenges during divestitures is data entanglement.
Enterprise data rarely belongs neatly to a single business entity. Customers, vendors, materials, contracts, and financial records are often shared across multiple organisational units.
Separating these data structures requires careful analysis and controlled transformation. The goal is not simply to copy information into a new environment. The organisation must ensure that the new entity has the data it needs to operate while maintaining the integrity of the remaining system landscape.
At the same time, regulatory and financial reporting requirements cannot be disrupted.
Finance teams still need to close books accurately. Operational teams still need systems that support procurement, logistics, and production. Compliance obligations remain unchanged even while the underlying systems are being restructured.
The time pressure of deal execution
Divestitures and carve-outs rarely happen without strict timelines.
Once a transaction is announced, there are clear expectations around Day-One readiness. Buyers expect operational independence. Transitional service agreements may define how long shared systems can remain in place.
Therefore, technology teams face a difficult balance.
They must carefully separate systems to protect operational continuity while moving quickly enough to meet the transaction schedule.
This tension between speed and control is where many transformation programmes struggle.
Why early system visibility matters
Organisations that manage carve-outs successfully often take a different approach.
Instead of treating ERP changes as a technical step that follows the deal, they begin by understanding the system landscape early in the process. This includes mapping dependencies across entities, identifying shared data structures, and evaluating different separation scenarios before execution begins.
This visibility allows leadership teams to make more informed decisions about how the transaction should be implemented from a technology perspective.
Sometimes the answer is a full system separation. In other cases, organisations may adopt a phased approach in which operational independence is achieved first, while deeper transformation occurs later.
The key is understanding the system reality early enough to plan with confidence.
Structural change requires structural thinking
ERP platforms today are not just financial systems. They support core operational processes, regulatory compliance, supply chains, and increasingly the data environments that power analytics and AI.
When the organisation’s structure changes, the structure of these systems must evolve as well.
Divestitures and carve-outs, therefore, require more than technical execution. They require careful orchestration between business leadership, finance teams, and technology specialists.
Enterprises that recognise this early tend to navigate structural change with far greater confidence.
Those who underestimate the complexity often discover that the hardest part of the transaction begins after the deal is signed.
Over the coming weeks, the ONE.Ascent campaign will continue to explore how enterprises manage ERP change during structural events such as mergers, acquisitions, and divestitures, and how organisations can reduce risk while maintaining operational continuity.
Continue the Conversation
If your organisation is navigating a divestiture, carve-out, or system separation, join our upcoming ONE.Ascent executive webinar where we explore the practical realities of managing ERP change during structural transformation.
You can also explore the ONE.Ascent campaign hub to see how enterprises across the Asia Pacific are approaching enterprise 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.
