TSA Exit Acceleration
Off the seller’s Fusion pod. By a clean close.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Oracle Fusion TSA separation is the work of standing up a Newco environment for ERP, EPM, and the supporting Cloud applications, then exiting the seller's tenancy before the close calendar forces the issue. The work belongs inside the wider carve-out advisory program because Fusion carries the general ledger, procurement, and the integrations that feed both. Buyers that treat it as a back office detail discover that the entire deal stays tethered to the seller's pod.
Oracle Fusion separation starts with a complete inventory of the seller tenancy. The buyer needs the production and non production pods, the application footprint covering Financials, Procurement, Supply Chain, EPM for planning and close, and Human Capital Management where it sits in scope. It needs the enterprise structure inside that environment: the legal entities, business units, ledgers, and reference data sets that define where Newco data lives.
The seller typically runs Newco inside a shared pod. Newco transactions sit under one or more legal entities and business units inside a primary ledger that also carries seller entities. Oracle does not sell an in place tenancy split as a standard service. The practical path is a new Newco pod with selective migration of configuration, master data, and balances. That single decision shapes licensing, the migration scope, and the cutover sequence.
Target pod strategy follows the carve-out timeline. A configuration replication approach rebuilds the seller setup in a clean Newco pod and migrates only required data. A simplification approach treats the separation as a chance to retire seller complexity that a standalone entity does not need. The choice is made deliberately, with the close calendar and the audit posture in view, not by default.
A clean inventory and settled pod decision drive the downstream sequence: the data migration plan, the integration redesign, and the cutover window. The pattern follows the broader TSA exit ERP separation framework and aligns with the carve-out IT plan.
Fusion is sold as cloud subscriptions metered by hosted employees, application users, or transaction volume depending on the module. The seller subscription does not transfer in a carve-out. Newco signs a direct subscription covering the modules in scope and the metric counts it actually requires. Oracle reads a carve-out as a captive buyer working against a close date, so the discipline is to settle the commercial before that leverage fades.
The buyer prepares user and employee counts by module, the transaction volumes that drive consumption metrics, and a credible alternative. Where Newco could run a lighter finance stack, that option creates room. Where Newco stays on Fusion to preserve a complex model, leverage moves to term length, price holds, ramp schedules, and protection against metric reclassification. Universal Credits and any OCI consumption tied to extensions are scoped explicitly so Newco does not inherit a surprise infrastructure bill.
Implementation services are the second commercial. Newco selects an Oracle partner with carve-out experience, fixed-fee willingness, and senior team continuity through go live. The contract is fixed fee for defined deliverables with disciplined change control. Hourly time and materials is not the model a buyer should accept for a scoped separation.
Where the seller extends pod access through a TSA period, that pricing is cost-plus or fixed-fee with a defined exit ramp. The seller cannot mark up subscription costs it does not incur. The audit discipline runs through the broader TSA license consolidation work so duplicate entitlements are eliminated at exit.
Configuration migration is the central activity. The implementation partner provisions the Newco pod and configures the enterprise structure, the chart of accounts and its value sets, the ledger and subledger setup, and the procurement and supply chain reference data. Functional Setup Manager exports and configuration packages move setup data between environments. Where Newco can adopt a clean standalone chart of accounts rather than inheriting seller segments, the separation simplifies the close rather than copying its complexity.
Master data is the heavier lift. Suppliers, customers, items, the asset register, and bank account master records migrate with cleansing and deduplication. File Based Data Import templates and the import frameworks load this data with validation at each stage. Reconciliation against the seller source is built into every load because a master data error surfaces later as a failed payment or a blocked receipt.
Extensions are the variable that drives cost and risk. Fusion personalizations, Application Composer objects, Visual Builder pages, fast formulas, and custom OTBI subject areas built for the seller environment are reviewed, retained, or retired. Anything authored without clean documentation becomes a discovery exercise the buyer should budget rather than absorb.
Security is the most consequential piece. Newco roles are rebuilt from Oracle's role inheritance model with explicit data security, segregation of duties checks, and approval rules that match a standalone control environment. A weak role design is the most common source of post go live remediation and audit findings.
Transactional migration covers open payables and receivables, open purchase orders, inventory and 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 closed history migrates versus 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 the cutover window and cost.
Integrations are the workstream carve-outs underestimate. Fusion connects through Oracle Integration Cloud, REST and SOAP web services, and file based interfaces. The footprint typically includes bank connectivity, tax engines, the expense and procurement networks, EDI partners, payroll feeds, and downstream reporting. Each interface is inventoried with its owner and data contract, then rebuilt and tested against the Newco pod.
Bank communication is its own track. Payment file formats, bank statement imports, and positive pay are reestablished against Newco bank accounts and certificates before the first payment run. Reporting migration covers OTBI analyses, BI Publisher templates, and EPM data integrations, all of which are easy to undercount and slow to rebuild.
The application cutover plan ties the threads together with freeze windows and reconciliation gates, governed through the same discipline as a broader TSA exit application cutover plan.
Cutover is timed around the financial calendar and the Oracle release calendar at once. The buyer plans go live at a period boundary so opening balances load cleanly, while aligning the test and cutover windows with Fusion's mandatory quarterly updates so a forced update does not land mid event. The runbook covers the data freeze, the final delta migration, balance reconciliation sign off, integration cutover, and the controlled open of periods. It is rehearsed at least twice.
Close continuity is the sensitive piece. Procurement keeps raising and receiving orders, finance keeps running payments and collections, and the first month end close runs entirely in the Newco pod. The buyer protects this by confirming dedicated support from the implementation partner and the seller's retained team across the first close in the TSA tail.
Stabilization runs sixty to ninety days. The first full close in the Newco environment is the gate that confirms steady state. Failed interfaces, posting errors, and access gaps are triaged within agreed service-level commitments. Only after a clean close does the buyer certify the Fusion services for TSA exit.
Knowledge transfer is scheduled during the build. The seller's configuration choices, extension logic, and integration quirks are documented so the Newco team is not dependent on the seller after the exit date.
Fusion separation programs vary by module scope, extension volume, integration count, and data history. The economic discipline is to scope tightly to the legal entities and modules Newco runs, hold the 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.
The common cost overruns trace to integration rebuild, reporting migration, and master data quality. The fix is the disciplined inventory before contract signing, early identification of every interface and report 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 a quarterly update colliding with the test cycle. 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. Fusion carries the financial backbone, so a slip propagates to the close calendar and the exit date.
A clean Fusion separation produces a Newco that owns its own finance, procurement, and close, with 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.
Oracle does not offer an in place tenancy split as a standard service. The realistic path is a new Newco pod with selective migration of legal entities, business units, and balances. The seller environment retains seller data and is exited on a defined ramp.
Oracle ships mandatory quarterly updates to Fusion Applications. The cutover plan accounts for the seller and Newco environments sitting on the same or adjacent update levels, and the test cycle aligns with the Oracle release calendar so a forced update does not land mid cutover.
Most Oracle Fusion separations run nine to fourteen months because ERP, EPM, and the integration estate converge on the financial close. The TSA should carry an exit ramp with milestone gates rather than an open seller commitment.
Integration rebuild and reporting migration. Fusion connects through OIC and dozens of REST and SOAP services, and OTBI and BI Publisher reports are easy to undercount. Inventory both before signing the implementation contract.
The S/4HANA company code strategy, master data, and the standalone close.
Read the article →The cross platform ERP separation framework and how to sequence finance cutover.
Read the article →The broader Oracle estate separation across legacy applications and Fusion.
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 →