TSA Exit Acceleration
Off the seller’s Oracle tenant. Every pay run intact.
Fixed-fee proposal in 48 hours. Senior payroll team on day one. The first conversation is always free.
Oracle HCM TSA separation is the work of moving Newco off the seller’s shared Oracle Fusion Cloud HCM environment and onto its own, with clean worker records, intact payroll, and rebuilt approvals. The program sits inside the broader carve-out advisory plan. HCM holds payroll, time, and the employee system of record, so the separation cannot miss a single pay run or break manager access on Day One.
Oracle HCM separation starts with a full inventory of the seller tenant. The modules in use covering Core HR, Payroll, Absence, Time and Labor, Talent, Compensation, and Benefits. The legal employers and payroll statutory units. The active fast formulas, the element entries, and the document records. The integrations through HCM Extracts, HDL files, and OIC. Without that inventory the team is migrating payroll blind, and payroll is the one workstream where a quiet error becomes a legal exposure.
The seller usually runs one Fusion tenant spanning several business units sharing configuration, security, and a single payroll calendar. Newco worker data lives as assignments tagged to a legal employer, a payroll, and a department. Oracle does not split a tenant in place. Newco provisions a fresh Fusion environment, or carves into a separate legal employer structure, and migrates the population that belongs to it. The output is a configured tenant with a controlled data load, not a clone of the seller setup.
The tenant decision is shaped by carve-out timing and the Newco operating model. A lift approach mirrors the seller configuration and prunes what does not apply, which is fast but inherits technical debt. A greenfield approach builds a clean tenant to a target data model and imports only active workers, which is cleaner but slower. Most carve-outs land on a hybrid: keep the payroll and Core HR configuration that runs today, rebuild the talent and compensation pieces that were built for the seller.
A clean inventory drives every downstream call. The implementation partner scope. The migration sequence. The payroll parallel plan. It also gives the buyer the facts to challenge any seller charge during the TSA window, which is where the discipline of an independent buyer-side review earns its fee.
Oracle HCM Cloud is licensed per employee per month against the modules in scope. The seller subscription does not transfer in a carve-out. Newco signs a direct Oracle Cloud agreement sized to its real headcount and module footprint. Oracle reads a carve-out buyer as a captive account under timing pressure, so the negotiation is a single moment that sets the cost base for years. Pushing the employee count and module set down to the actual Newco need is the largest line item to control.
The implementation partner is the second commercial. Newco selects an Oracle partner with payroll separation experience and holds the engagement to a fixed-fee scope with disciplined change control. Time and materials billing is not the model for a carve-out under a deadline. Senior payroll continuity through parallel runs and cutover matters far more than the headline day rate.
Where the seller continues to run Oracle HCM for Newco through a TSA period, the price is held to cost-plus or fixed-fee with a defined exit ramp and audit rights. The seller cannot place a mark-up on a per employee cost it does not bear, and it cannot pass through inflated allocation. The buyer sets a clear exit date so the TSA does not drift into an expensive default that suits the seller.
The commercial discipline mirrors the approach used across other platform separations, including the Workday separation where the same captive dynamics apply at renewal.
Data migration covers worker records, assignments, salary and element entries, balances, absence plans, and document records. Oracle exposes the data through HCM Extracts for the outbound pull and HDL for the inbound load. The sequence loads the enterprise and legal employer structures first, then jobs and positions, then workers and assignments, then payroll elements and balances. Each object gets a defined extract, conversion, and load process with reconciliation against the seller source so nothing is silently dropped.
Payroll balance continuity is the technical heart of the program. Year to date earnings, tax, and deduction balances must arrive intact so the first Newco payroll and the year end filings are correct. Balance initialization through HDL is reconciled to the cent against the seller final run. Where the carve-out crosses a tax year, the team decides early whether Newco starts fresh balances or carries the full history, because that choice drives the entire migration design.
Parallel payroll runs are not optional. The team runs at least two full parallel cycles where the Newco payroll output is compared line by line against the seller production run for the same population. Gross to net, employer charges, and net pay must match within an agreed tolerance before cutover is approved. A failed parallel is the signal to delay, never to push through and reconcile later.
The reconciliation gate closes the workstream. Headcount, balance totals, and a sample of complex cases such as multiple assignments and mid period joiners are checked before sign off.
Oracle HCM rarely stands alone. It connects to the finance system for costing, to benefits and pension providers, to the identity provider for single sign on, to time collection devices, and often to a separate recruiting or learning platform. Each integration is inventoried, repointed to Newco endpoints, and tested in a staging window. The finance costing integration deserves special care because a broken costing feed corrupts the general ledger on the first close.
Security and approvals do not export cleanly. Oracle HCM roles, data security profiles, and approval rules are rebuilt in the Newco tenant from a documented inventory. The rebuild is the moment to retire the seller approval hierarchies that no longer match the Newco organization. Each role is reconstructed, tested with sample users, and signed off by the HR and payroll owners before go live.
Identity is the final boundary. Newco users authenticate through the Newco identity provider, and provisioning maps directory groups to HCM roles. The identity cutover is locked before manager self service training so test users hold the correct access. Where the seller identity provider granted access during the TSA, that access is revoked on a defined date written into the exit plan.
The integration discipline draws on the broader IT separation framework set out in the TSA exit IT separation playbook.
Cutover is the window where payroll and HR operations move from the seller tenant to the Newco tenant. It is planned around a pay period boundary with a data freeze, a final delta load, balance initialization, and the first live Newco run. The runbook covers freeze, delta migration, parallel sign off, integration activation, and a rollback trigger if the first run fails reconciliation. It is rehearsed before the real event.
Oracle HCM separation programs typically run between $150K and $700K depending on module scope, payroll complexity, country count, and integration volume. The cost discipline is to scope tightly to the modules Newco actually needs, hold the implementation partner to fixed fee, and resist migrating configuration that does not serve the Newco operating model. Multi country payroll is the largest cost driver and the largest risk.
The common failures are predictable. Underestimating payroll parallel effort and compressing it until errors surface in production. Missing a year to date balance and breaking the year end filing. Forgetting a downstream costing integration and corrupting the first finance close. Each is avoided by the inventory, the disciplined parallel runs, and a reconciliation gate that has the authority to delay cutover.
A clean Oracle HCM separation gives Newco its own tenant, licensed to its real headcount, with payroll intact and the freedom to evolve its HR model on its own timeline. The work is delivered through the TSA exit acceleration program under a Fixed Fee or Portfolio Retainer engagement.
No. Oracle does not offer an in place tenant split. Newco provisions a new Fusion environment or a separate legal employer structure and migrates its workers, balances, and configuration into it. The shared tenant stays with the seller.
Most run 12 to 24 weeks depending on module scope, payroll country count, and integration volume. Payroll parallel runs set the floor on the timeline. The cutover itself is aligned to a pay period boundary rather than a single weekend.
Because payroll is the one workstream where an error becomes an underpaid employee and a filing exposure. At least two full parallel cycles confirm gross to net and employer charges match the seller production run before any cutover is approved.
Sellers commonly bill a per employee allocation plus a mark-up on the underlying subscription. The buyer holds the price to cost-plus or fixed-fee with a defined exit ramp and audit rights, and confirms the seller is not marking up a cost it does not incur.
Tenant strategy, payroll cutover, and protecting worker data through a carve-out.
Read the article →Portal split, data export, and a disciplined plan that protects pipeline.
Read the article →The cross platform IT separation framework and how to sequence the workstreams.
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 payroll 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 →