Corporate Spin-Off HR: The Dual-System Window Nobody Plans
Spin-off plans treat Day One as the finish line. The real cost sits in the 12 to 24 months two HR systems run in parallel, and nobody staffs it.
Key Takeaways
Public spin-off filings put transition service agreements at 12 to 24 months. Honeywell's Solstice separation capped most services at 12 months, while GE Vernova and Aptiv both wrote 24-month ceilings into their agreements.
GE Vernova's TSA charges an escalating premium for extensions: 25 percent for the first three months past the exit date, 40 percent for months four through six, and 50 percent beyond seven.
Deloitte's 2026 Global Divestiture Survey, covering 981 sellers and 908 deals above $100 million, found a median sign-to-close of roughly three months. HR gets one quarter to plan for a two-year parallel run.
A standalone Workday HCM deployment runs 4 to 9 months on its own. Spin-off HR teams are asked to do that while still operating inside the parent's instance.
94 percent of Workday hiring requests in 2025 were contract or contract-to-hire, which tells you the market already understands this as spike work.
What does a failed HR separation actually look like?
It almost never looks like a system that doesn't work. It looks like a system that works twice. Payroll processes in the parent's instance for one population and the new instance for another, and someone in HR Ops reconciles the two by hand every cycle because the org structures no longer match.
That's the shape of it. A recruiter can't see the requisition history for a role she filled eighteen months ago, so she rebuilds the scorecard from memory. A manager approves a promotion in the new tenant and the compensation record still routes to a parent approver who technically doesn't work there anymore. Benefits enrollment opens on the parent's calendar while the spun entity's plan year starts eleven weeks later.
None of this shows up on the separation dashboard, because the dashboard tracks Day One readiness and Day One already happened. The failure is quiet, distributed across a few dozen people doing manual work that was supposed to be temporary, and it stays quiet until the TSA extension invoice arrives.
Why does the dual-run window outlast the project plan?
Because the TSA is priced as a cost curve, not a deadline. Companies read the 12 or 24 month ceiling as a runway and plan to land somewhere in the middle. The parent, meanwhile, has written escalating premiums into the agreement precisely because it expects the exit to slip.
Look at what GE Vernova actually negotiated. Extensions past the scheduled exit cost 25 percent above the pre-extension service charge for the first three months, 40 percent for months four through six, and 50 percent past that. Aptiv's agreement with Versigent goes further and allows the parent to push documented discontinuance costs, stranded costs, severance, and continuing third-party license obligations onto the recipient. GE Vernova requires 90 days of written notice just to terminate a service voluntarily. Aptiv requires 45.
Read those terms as a forecast. The lawyers who drafted them have watched enough separations to know the HR exit is usually the last one standing, and they priced accordingly. Your finance team booked the base TSA fee. It did not book the 40 percent.
Who owns the historical employee data after Day One?
Usually nobody, which is why the question stalls the migration. Employment history doesn't split along an org chart. An engineer who spent four years in the retained business and two in the divested unit has one continuous record, and both entities have a legitimate claim to parts of it.
The clean cases are the ones people plan for. Active employee, single business unit, never transferred: that record moves. Now take the harder ones. Someone who left the company in 2021 from a department that no longer exists in either entity. A performance review written by a manager who stayed behind about an employee who went. Compensation history that spans a job architecture the new company is about to replace. Open workers' compensation claims. Terminated employees whose records the parent must retain for statutory reasons while the spun entity needs them for reference checks and rehire eligibility.
Every one of those needs a decision, and each decision has a legal owner, a system owner, and a functional owner who all have to agree. Multiply that by seven or eight Workday modules. That's where the timeline actually goes.
The teams that handle this well make one call early: they define a historical cutoff, migrate everything after it, and leave everything before it in an archive the parent maintains under the TSA with a defined read path. It's an unsatisfying answer. It also lets configuration work start in week three instead of week eleven.
Why is the compressed timeline a staffing problem, not a technology problem?
Because the technology work is known and the capacity to do it is not. A Workday deployment is a well-documented sequence: 2 to 4 weeks of discovery, 4 to 8 weeks of design and configuration, 2 to 6 weeks of data migration and integrations, then 2 to 4 weeks of testing and training. Nothing about that is mysterious.
What breaks is that you need six to ten experienced people for about nine months and then you don't. Hiring them full-time leaves you overstaffed after go-live. Hiring them through a U.S. consultancy is what the market charges, and the market has opinions.
Role on a four-person spin-off pod | U.S. contract rate (KORE1, 2026) | One month at 173 hours |
|---|---|---|
Workday HR lead, senior functional | $120 to $165 per hour | $20,760 to $28,545 |
Configuration analyst, mid-level functional | $85 to $125 per hour | $14,705 to $21,625 |
Configuration analyst, mid-level functional | $85 to $125 per hour | $14,705 to $21,625 |
Configuration analyst, mid-level functional | $85 to $125 per hour | $14,705 to $21,625 |
Four-person pod, monthly | $64,875 to $93,420 |
Run that pod for a twelve-month parallel window and you're between $779,000 and $1.12 million, before the TSA fees you're paying the parent for the same twelve months. You are, in effect, funding two HR functions and the bridge between them.
The supply side doesn't help. Workday is deployed at more than 11,000 organizations, only 32 percent of leaders say their workforce has the skills they need, and 92 percent of Workday professionals now work remote or hybrid, which means the person you want is being courted by every other separation happening this quarter.
What did the companies that got through this cleanly do differently?
They staffed the parallel run as its own project with its own budget line. Not as overflow work absorbed by the HRIS team that already had a full roadmap.
Three things show up repeatedly in separations that exit their TSA on schedule. The first is a named exit owner, usually inside the Separation Management Office, whose job is to sequence service terminations and reject a service that gets marked complete before the receiving side can actually run it. The second is a data cutoff decision made in the first month rather than negotiated across four months of meetings. The third is a team structure that can change shape between the build phase and the migration phase without a hiring cycle in between.
That last one is where most internal HR functions have no good option. You can't recruit three Workday configuration analysts in three weeks through a normal req process, and you can't quietly release them in month ten without a conversation nobody wants to have.
This is the specific reason nearshore staff augmentation fits separation work better than it fits steady-state HRIS support. Pre-vetted analysts in Bogotá, São Paulo, or Buenos Aires overlap the full U.S. workday, which matters when the client-side HR lead, the parent's system owner, and the external consulting partner all need to be in the same design session. IDP has deployed exactly this shape, an HR lead plus three configuration analysts covering core HCM, security, recruiting, compensation, talent, time tracking, absence, and reporting, for a client running a business unit spin-off on an aggressive clock. The team scaled down after migration without a severance conversation.
How do you tell early that the parallel run is slipping?
Watch four signals in the first ninety days after Day One, before the TSA clock gets expensive.
Manual reconciliation that was supposed to last two pay cycles is still happening in cycle six. Ask HR Ops directly, because they will not volunteer it. Second, the data cutoff decision is still open past week five. Third, your configuration backlog is growing faster than it burns down, which usually means the team is sized for the plan rather than for the discovered scope. Fourth, and most telling, somebody has started asking what a TSA extension would cost. That question means the exit date is already gone and the organization hasn't said so out loud yet.
None of these require a steering committee to detect. They require one person whose actual job is the exit, asking every two weeks.
A spin-off is one of the few corporate events where HR's workload triples and its headcount doesn't. IDP places nearshore Workday and HRIS talent with U.S. companies working through exactly that window, on the timelines separations actually run on rather than the ones they're planned on.
Sources
More Articles
Corporate Spin-Off HR: The Dual-System Window Nobody Plans
Spin-off plans treat Day One as the finish line. The real cost sits in the 12 to 24 months two HR systems run in parallel, and nobody staffs it.
Cloud Migration Projects: The Nearshore Team Advantage
A hybrid AWS and on-prem migration is a knowledge-transfer project as much as a technical one. Here is why the team that stays matters more than the plan.
The Hidden Cost of High IT Turnover, and How to Fix It
Help desk turnover runs 13 to 42 percent a year. Every reassigned ticket costs two hours. Here is the fully loaded cost, and what actually fixes it.