TSA Exit Acceleration
Off the seller’s Workday tenant. On schedule.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
TSA Workday separation is the discipline of decoupling Newco from the seller’s Workday tenant so Newco operates its own HCM, payroll, and finance footprint with licensed entitlements, clean integration boundaries, and a defensible go forward configuration. The work runs through the broader TSA exit strategy framework and is the single most sensitive workstream because it touches employees on day one. Workday separation is a configuration program, not a database extraction. The integrity of payroll and benefits depends on it.
Workday separation starts with a complete tenant inventory. The production tenant. The implementation and sandbox tenants. The Foundation Data Model with company hierarchy, supervisory organizations, cost centers, and locations. The HCM configuration covering business processes, security domains, compensation plans, and benefits. The Payroll module configuration where applicable. The Workday Financials module where applicable. The integration catalog covering Workday Studio, EIB, Core Connectors, PECI, and PICOF feeds.
The seller typically runs one production tenant covering many legal entities. Newco data sits as one or more companies inside that tenant. The separation has to extract Newco data and rebuild it in a tenant that Newco controls with its own contract and its own admin governance. Workday does not support an in place tenant split as a standard service. The result is a configured rebuild with selective data migration.
The target footprint decision frames everything. Newco may take the existing Workday modules unchanged. Newco may add Payroll where the seller managed it elsewhere. Newco may drop modules that do not fit the new operating model. The decision is finalized in the first 60 days of the runway and reflected in the implementation partner statement of work.
A clean inventory and footprint definition unlocks every downstream decision. The licensing structure. The data migration plan. The integration redesign. The first payroll calendar. Where the inventory is incomplete, the first payroll run is at risk. The pattern aligns with the TSA exit HR payroll separation sequence and the broader day one HR readiness plan.
Workday licensing is straightforward in shape and consequential in price. Workday sells subscription seats by module with a tenant fee and a worker count fee. The seller agreement does not transfer. Newco signs a direct subscription with Workday covering HCM, the optional modules, and the implementation services. The negotiation is a one shot opportunity. Workday reads the situation as a captive buyer with carve out timing pressure.
The preparation covers worker counts, module selection, ramp schedules, and the BATNA. Where Newco can credibly select a different HCM platform, the negotiation has leverage. Where Newco has chosen Workday as the platform and has limited time, leverage is thin and must come from the commercial structure. The structure includes term length, price holds, free sandbox tenants, and committed implementation credits.
Implementation services are the second commercial. Newco selects an implementation partner from the Workday ecosystem. The selection criteria include carve out experience, fixed-fee willingness, senior team continuity through the program, and clean contractual remedies for delay. The implementation contract is fixed fee for defined deliverables with disciplined change control. Hourly time and materials is not the engagement model.
Where the seller is willing to extend tenant access through a TSA period, the TSA pricing is negotiated to a cost-plus or fixed-fee structure with a defined exit ramp. The seller cannot bill Newco a mark-up on Workday subscription costs that the seller is not actually incurring. The audit discipline runs through the TSA audit rights framework.
Tenant build is the central engineering activity. The implementation partner configures the new Newco tenant from a baseline Workday template. The Foundation Data Model is rebuilt with Newco company hierarchy, supervisory organizations, cost centers, locations, and matrix organizations. The configuration mirrors the seller where appropriate and adjusts where the Newco operating model differs. Business processes are configured with defined approvals, conditions, and step level security.
Compensation plans, benefits plans, time tracking rules, and absence plans are migrated from the seller tenant through extracts, transforms, and configuration loads. Where the seller used a custom configuration that does not fit Newco, the configuration is rebuilt rather than copied. The result is a tenant that reflects Newco operating decisions, not seller legacy decisions imposed by accident.
Security configuration is the most consequential piece. Domain security and business process security are rebuilt with Newco role definitions, segregation of duties controls, and approval routings. The configuration is reviewed against audit and SOX requirements before user provisioning starts. A security configuration error is the most common source of post go live remediation work.
Tenant migration tools accelerate the work. The Workday Tenant Refresh capability does not apply across customer boundaries, so the configuration migration uses Object Transporter, configuration packages, and partner accelerators. The accelerators reduce hand work and improve consistency. The discipline aligns with the day one HR payroll readiness sequence.
Data migration covers worker data, compensation history, benefits enrollments, time off balances, and payroll history. Worker data migrates first using EIBs or Core Connectors. The fields cover demographic data, employment data, organizational assignments, and compensation. Each domain has a defined extract, transform, and load process with data quality checks and reconciliation reports against the seller source.
Compensation history and benefits enrollments require careful handling. The history records establish accrual balances, vesting positions, and benefits eligibility. The migration approach typically loads two to three years of history and archives the rest. Payroll history migrates where Newco needs the data for year to date calculations and tax filings. Where payroll history stays with the seller, the seller commits to issuing the calendar year W-2 or equivalent and Newco starts a clean year to date in the new tenant.
Integrations are the workstream that most carve outs underestimate. Workday connects to dozens of third-party systems. Benefits carriers, the 401k provider, the stock administration platform, the background check vendor, the learning management system, the recruiting platform, the expense tool, the GL feed to finance, and the time tracking and badge systems. Each integration is inventoried, tested, and rebuilt in the Newco environment. Where integrations cross the seller boundary during a TSA period, the boundary contract defines who maintains the connection.
Identity integration is the final piece. The Workday tenant authenticates against Newco identity provider through SAML or OIDC. The user provisioning into downstream systems uses Workday as the source of truth for the new employee lifecycle. The identity boundary is locked before payroll testing begins so that test users have the right downstream access.
Payroll is the gate on the entire Workday separation. The first Newco payroll run has to land accurately, on time, and with correct tax filings. The path runs through configuration validation, mock payroll runs, parallel payroll runs against the seller production, and a final cutover decision. Each parallel cycle compares gross to net by employee against the seller output and reconciles the variance to the cent.
Two to three parallel cycles are typical. The first parallel identifies configuration gaps and integration errors. The second parallel validates the fixes. The third parallel confirms readiness for the go live cutover. Where variance persists after three parallels, the carve out PMO and the payroll lead decide whether to extend the TSA period or accept controlled go live with manual reconciliation.
Cutover is the window where Newco employees move from the seller Workday tenant to the Newco Workday tenant. The window is typically aligned to the first payroll period of a quarter or calendar year to simplify tax reporting. The cutover runbook covers communication, access changes, time entry continuity, and the first payroll run. The runbook is rehearsed twice before the actual cutover.
Hypercare runs for 90 days. The first three payroll cycles in the new tenant are the gate that confirms steady state operation. Production issues get triaged within defined service-level commitments. The TSA exit certification for HR services follows successful close of the third payroll cycle. The discipline runs through the TSA exit milestones framework.
Workday separation programs run between $1M and $8M depending on module scope, worker count, integration count, and the chosen partner. The cost dispersion is narrower than ERP because the platform is more standard. The economic discipline is to scope the program tightly to required modules, hold the implementation partner to fixed fee, and avoid scope expansion driven by the partner rather than the Newco operating need.
The most common cost overruns trace to integration discovery, security redesign, and uncontrolled compensation rebuild. The fix is the disciplined inventory before contract signing, the early integration discovery phase, and the change control process that prices every scope addition in writing. Where these controls are in place, the program lands within the original budget plus or minus 10 percent.
The most common timeline overruns trace to delayed data extracts from the seller, late confirmation of benefits carrier feeds, and unclear payroll boundary decisions. The fix is the explicit dependency map maintained by the PMO with named owners on both sides and a weekly governance rhythm that escalates blocks within 48 hours. A Workday separation that misses its target go live disrupts payroll and erodes employee confidence.
A clean Workday separation produces a Newco that runs its own tenant with licensed entitlements, supported configuration, and the optionality to evolve the HR operating model on Newco timeline. The work is configuration engineering. The economics depend on commercial discipline. The discipline runs through the TSA exit acceleration program and is delivered under a Fixed Fee + Portfolio Retainer engagement model.
SAP ECC and S/4HANA decoupling, license negotiation, and the typical carve out timeline.
Read the article →ADP payroll decoupling, tax filing transitions, and the integration boundary with the HCM.
Read the article →The cross platform HR and payroll 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 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 →