A divestiture creates a new legal entity that needs its own systems, its own licenses and its own support, usually under a transition services agreement (TSA) that is already counting down. oXya scopes the separation early, manages it end to end, and runs the new environment once it goes live.
Book a 30-minute scoping call
The Trigger
The deal closes on paper long before it closes in the systems
The moment a business unit is sold, its data has to leave a shared SAP landscape and stand up on its own. That work is rarely on the critical path when the deal is priced. It always is by the time the TSA clock starts.
The Main Challenges
What oXya does
One partner accountable for the whole separation
A carve-out is never a single discipline. It takes data extraction, functional work, licensing and infrastructure, usually from different specialists. oXya assembles that team and is accountable for it, so the new entity signs one contract and has one party to hold accountable.
Four ways oXya takes ownership
Early technical assessment
We map the SAP landscape and scope the separation while TSA deadlines are still negotiable. Scope discovered later becomes a schedule problem, and usually a cost problem too.
A single point of accountability
We select and manage the partners involved in the separation: extraction tooling, functional work and licensing. You work with oXya; we coordinate the rest.
Licensing for the new entity
We work directly with SAP to build the standalone company's license package, so Day 1 is covered contractually as well as technically.
Day 2 and beyond.
We host and manage the new landscape as a long-term managed service. The separation project ends; the operating model it leaves behind does not.
Two ways to look at the same problem
How the SAP separation plan affects deal price and TSA terms
Why the technical separation shapes the TSA, the schedule and the cost of the transaction, and what to settle before the deadlines are fixed.
Read the article
Data separation: how SAP carve-out slicing really works
What actually gets sliced out of a shared SAP S/4HANA system, where the company code selector stops working, and how every table gets its ruling.
Read the article
Start Here
See what your SAP landscape looks like once it’s separated
The assessment is a short, scoped engagement. It gives both sides of a transaction a defensible view of the separation before commitments are locked in.
- Enterprise structure map. Which organizational elements belong exclusively to the entity being sold, and which are shared.
- Scope and effort. Data volumes, the tables that need a ruling, and what that means for the timeline.
- Target and licensing view. What the new entity needs to run on Day 1, on-premises or in the cloud.
Talk to our technical team