TSA Exit Acceleration
Off the seller’s S/4HANA instance. By a clean close.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
SAP S/4HANA TSA separation is the disciplined work of standing up a Newco instance that runs its own finance, procurement, and supply chain, then exiting the seller's system landscape before the close period forces a decision. The work sits inside the broader carve-out advisory program because SAP touches the general ledger, the purchase order flow, and every integration that feeds them. Treated as an afterthought, it becomes the line item that strands the whole deal in the seller's environment.
SAP S/4HANA separation starts with a full system landscape inventory. The buyer needs the production client, the quality and development clients, and the transport landscape that moves changes between them. It needs the module footprint covering Finance (FI and CO), Materials Management, Sales and Distribution, Production Planning, and any industry solution in use. It needs the deployment model, whether the seller runs S/4HANA on premise, on RISE with SAP, or in a private cloud edition, because that decision shapes Newco's contracting path.
The seller almost always runs Newco inside a shared production client. Newco data lives as one or more company codes, controlling areas, plants, and profit centers inside a ledger that also carries seller entities. SAP does not sell an in place client split as a standard service. The realistic path is a new Newco instance with selective migration of company codes, master data, and open transactions. That decision is the foundation for licensing, configuration, and cutover sequencing.
Target client strategy follows the carve-out timeline and the Newco operating model. A system copy approach clones the seller landscape, deletes seller company codes, and converts the remainder into the Newco client. A greenfield approach builds a clean S/4HANA configuration and migrates only the data Newco needs. A hybrid takes the seller configuration as a baseline and rebuilds what no longer fits a standalone company.
A clean inventory and a settled target decision drive every downstream choice: the licensing structure, the data migration scope, the integration redesign, and the cutover window. The sequence mirrors the broader TSA exit ERP separation framework and the carve-out IT plan.
SAP licensing does not transfer in a carve-out. Newco signs a direct agreement covering S/4HANA, the named user types, the package and engine metrics, and any RISE subscription. SAP reads a carve-out as a captive buyer working against a fixed exit date, so the commercial discipline is to settle the contract before that leverage erodes. The buyer prepares user counts by license type, the document and order volume that drives package metrics, and a credible alternative position.
Where Newco can credibly run a smaller footprint, such as a different finance suite for a simple entity, that option creates room in the negotiation. Where Newco has decided to stay on S/4HANA to preserve a complex operating model, leverage shifts to term length, price holds, ramp schedules, and indirect access protection. Indirect or digital access pricing deserves explicit attention because it is where SAP recovers margin when direct user counts fall.
Implementation services are the second commercial. Newco selects an SAP partner with genuine carve-out experience, fixed-fee willingness, and senior team continuity through go live. The implementation contract is fixed fee for defined deliverables with disciplined change control. Hourly time and materials is not the engagement model a buyer should accept for a scoped separation.
Where the seller extends system access through a TSA period, that pricing is negotiated to cost-plus or fixed-fee with a defined exit ramp. The seller cannot bill a mark-up on costs it does not incur. The audit discipline runs through the broader TSA license consolidation work so Newco does not pay twice for the same entitlements.
Configuration migration is the central engineering activity. The implementation partner provisions the Newco client and configures the enterprise structure: company codes, controlling areas, plants, sales organizations, and purchasing organizations. The financial configuration in FICO carries the chart of accounts, the ledger setup, document types, and posting rules. Where Newco can adopt a clean standalone chart of accounts rather than inheriting seller complexity, the separation becomes a simplification opportunity rather than a copy exercise.
Master data is the heavier lift. Material masters, customer and vendor master records, the bill of materials, routings, pricing conditions, and credit master data all migrate with cleansing and deduplication along the way. SAP master data carries number ranges and cross references that have to be preserved or remapped consistently. A master data error surfaces as a failed posting weeks after go live, so reconciliation against the seller source is built into every load.
Custom ABAP is the variable that drives both cost and risk. Z programs, custom transactions, user exits, BAdIs, and enhancement points written for the seller environment have to be reviewed, retained, or retired. Custom code authored without clean versioning becomes a code review exercise that the buyer should budget explicitly rather than absorb as a surprise. S/4HANA simplification items, where classic transactions have been replaced, are addressed during this rebuild.
Authorizations and roles are the most consequential security piece. Newco roles are rebuilt with explicit authorization objects, segregation of duties checks, and approval workflows that match the standalone control environment. A weak authorization design is the most common source of post go live remediation and audit findings.
Transactional migration covers open items, open purchase orders, open sales orders, inventory balances, asset balances, and the general ledger opening position. The sequence loads configuration and master data first, then balances, then open documents. The buyer decides how much transactional history migrates versus how much stays archived and accessible read only. Most carve-outs migrate open items and a defined number of closed periods, then archive the rest to control cost and the cutover window.
Integrations are the workstream that carve-outs underestimate most. S/4HANA connects through IDocs, RFC calls, OData services, and middleware such as SAP PI/PO, Integration Suite, or third-party platforms. The footprint typically includes bank connectivity, tax engines, the procurement and expense systems, the warehouse and transportation systems, EDI partners, and reporting feeds. Each interface is inventoried with its owner, its protocol, and its data contract, then rebuilt and tested against the Newco instance.
Bank communication deserves a dedicated track. Payment files, bank statement imports, and treasury connectivity have to be reestablished with Newco bank accounts and certificates before the first payment run. Tax determination and statutory reporting are reconfigured for Newco's legal entities so that the first close produces compliant filings.
The application cutover plan ties these threads together. The sequencing, freeze windows, and reconciliation gates are governed through the same discipline as a broader TSA exit application cutover plan, with a parallel run where finance risk warrants it.
Cutover for an ERP is timed around the financial calendar. The buyer plans go live at a period boundary so that opening balances load cleanly and the first close runs entirely in the Newco instance. The runbook covers the data freeze in the seller client, the final delta migration, the balance reconciliation sign off, the integration cutover, and the controlled open of posting periods. The runbook is rehearsed at least twice before the live event.
Close continuity is the most sensitive piece. Procurement has to keep raising and receiving purchase orders. Finance has to run payments, collections, and the month end close without interruption. A buyer protects this by aligning the cutover with a clean period close in the seller environment and confirming that the first Newco close has dedicated support from both the implementation partner and the seller's retained team during the TSA tail.
Stabilization runs sixty to ninety days. The first full month end close in the Newco instance is the gate that confirms steady state. Posting errors, failed interfaces, and authorization gaps are triaged within agreed service-level commitments. Only after a clean close does the buyer certify the SAP services for TSA exit.
Knowledge transfer is scheduled, not assumed. The seller's configuration decisions, custom code logic, and integration quirks are documented during the build so that the Newco team is not dependent on the seller after the exit date.
S/4HANA separation programs vary widely by module scope, custom code volume, integration count, and data history. The economic discipline is to scope tightly to the company codes and modules Newco actually runs, hold the implementation partner to a fixed fee, and resist replicating seller complexity that adds no value to a standalone business. Every scope addition is priced in writing through change control rather than absorbed quietly.
The common cost overruns trace to custom code remediation, integration discovery, and master data quality. The fix is the disciplined inventory before contract signing, early identification of every interface owner, and a master data cleansing track that starts months before cutover. Where these controls hold, the program lands close to its original budget.
The common timeline overruns trace to late integration ownership, slow bank onboarding, and unclear data history scope. The fix is an explicit dependency map maintained by the PMO with named owners on both sides and a governance rhythm that escalates blocks inside forty eight hours. SAP carries the financial backbone, so a slip propagates straight to the close calendar and the TSA exit date.
A clean S/4HANA separation produces a Newco that owns its own finance and supply chain, runs its own close, and holds the optionality to evolve the operating model on its own timeline. The discipline runs through the TSA exit acceleration program under a Fixed Fee plus Portfolio Retainer engagement model.
Almost never. A shared production client mixes Newco and seller company codes, ledgers, and master data under one system landscape. The practical path is a new Newco instance with selective company code, master data, and open item migration, not an in place split of the seller's client.
Module scope, custom ABAP volume, integration count, data history depth, and whether Newco adopts clean configuration versus replicating the seller. A buyer-side advisor scopes tightly to the company codes and modules Newco actually runs and holds the implementation partner to a fixed fee.
Most S/4HANA exits land in nine to fifteen months because finance close, procurement, and integrations all converge on the ERP. The TSA should price an exit ramp with milestone gates rather than an open commitment the seller can extend at a mark-up.
Late discovery of integration ownership and custom interfaces. Buyers that inventory the IDoc, RFC, and middleware footprint before signing avoid the cutover slips that push month end close back into the seller's environment past the exit date.
The Fusion ERP and EPM separation path, data migration, and the standalone close.
Read the article →The cross platform ERP separation framework and how to sequence finance cutover.
Read the article →The broader SAP estate separation across ECC and S/4HANA landscapes.
Read the article →The 90-day governance, IT, finance, HR and procurement separation plan we run on live carve-outs. Get the playbook plus the bi-weekly Day One Letter — short, signal-heavy, buyer-side.
No spam. Unsubscribe in one click. · Read the overview first →
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Seven buyer-side moves to exit a Transition Services Agreement on time and below budget. The mark-up, the extension-fee curve, exit sequencing, and the 11-month calendar.
The ERP TSA is the longest pole. Decide clone vs. rebuild early, scope the data tightly, and cap the extension before it runs the whole exit.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →