Zero Disruption During a Divestiture: How Techwave Ran an SAP S/4HANA Carve-Out to the TSA Clock

Divestitures are where SAP landscapes go to break. A parent company sells a division, a Transition Service Agreement (TSA) sets a hard date for the carved-out business to run on its own IT, and the clock starts. Miss the window, and the buyer keeps paying the seller for shared systems, or worse, the new company cannot invoice, ship, or close its books. Techwave used a recent automotive carve-out to demonstrate what a clean separation looks like when the deadline is non-negotiable.

An Aggressive Clock And A Live Business

An automotive manufacturer in Western Europe was facing an aggressive divestiture timeline. The mandate was specific: execute a rapid IT carve-out and stand up an independent digital operating model without disrupting operations or breaking business continuity. In plain terms, the newly separated entity needed its own SAP core, integrations, and governance up and running before the TSA expired, while production kept moving and customers kept getting parts.

Techwave’s answer was a greenfield-style separation onto SAP S/4HANA Public Cloud. The team executed the IT carve-out, deployed SAP S/4HANA Public Cloud as the digital core, built the surrounding cloud IT infrastructure, integrated SAP Business Technology Platform (BTP) and EDI, and put governance in place for a seamless transition to steady-state operations. The competencies on display- SAP Cloud ERP, SAP BTP, and digital manufacturing transformation- map to exactly the parts of a carve-out that usually slip.

The stated outcomes are operational and include post-divestiture continuity with seamless operations, operational independence achieved within TSA timelines, a modern cloud-based digital core, and improved transparency across production and supply chain.

Why Public Cloud

Choosing SAP S/4HANA Public Cloud for a carve-out is a real decision. It enforces a standardized, clean-core model, which is an advantage when the organization is building a new entity with no legacy customization to protect. There is nothing to carry forward, so the fastest path is the standard one. That aligns with where SAP is pushing the ecosystem. At Sapphire 2026, SAP framed migration as an AI-driven, clean-core process and positioned standardization as the accelerator rather than the constraint.

EDI is the part outsiders underestimate. In automotive, electronic data interchange is how the business talks to OEMs and tier suppliers, and a carve-out that loses its EDI connections loses its ability to trade on day one. Rebuilding those flows on SAP BTP, in step with the S/4HANA cutover, is what turns “the system is live” into “the business is running.”

The Market Context

Carve-outs are becoming more common as the ECC clock runs down. SAPinsider research shows 55% of organizations have deployed SAP S/4HANA, with 34% fully transitioned, and each migration adds system administration complexity across hybrid landscapes. A divestiture compresses all of that into a fixed TSA window. SAPinsider’s ERP Migration and Transformation 2026 benchmark, based on 296 SAP customers, found that 36% are still implementing, evaluating, or building a business case, which means many companies will face an M&A event before their core transition is complete. The lesson from Techwave’s automotive case is that the two efforts, transformation and separation, can be run as one clean-core cutover rather than sequenced.

What This Means for SAPinsiders

Treat the TSA date as the real go-live, not the technical one. In a carve-out, “live” means the separated business can transact independently before the seller ceases to host shared systems. CIOs should build their program plan backward from the TSA expiration, and make EDI and integration cutover, not just SAP S/4HANA deployment, the milestones they defend.

Use a carve-out as a forced clean-core reset. A new entity has no customization debt worth preserving, so SAP Public Cloud plus standard processes is usually faster and cheaper than replicating the parent’s system. Enterprise architects should resist the instinct to clone the old landscape, and inventory only the integrations and master data the new business genuinely needs to run.

Don’t wait for the core migration to finish before handling M&A. With more than a third of SAP customers still mid-transition, a divestiture will not wait for the roadmap. SAPinsiders should pre-qualify a partner with proven carve-out and TSA-driven delivery experience now, so a corporate event becomes a scoped project rather than an emergency.