TSA recruiting and ATS migration moves open requisitions, candidate pipelines, and the hiring workflow into Newco's own applicant tracking system before the seller cuts access. It is easy to underrate until a live offer disappears, and it sits inside the operational scope of carve-out advisory. The work is part data migration, part live process handoff, and the live part is what makes it risky.
An applicant tracking system looks like a minor piece of software next to the ERP or the payroll engine. It is not minor when the carved-out business is still hiring. The ATS holds every open requisition, every candidate in the pipeline, the interview history, scorecards, and the offer workflow that turns a yes into a start date. In a carve-out the seller owns the instance, and the buyer often defers it until late, assuming a recruiting tool can be stood up quickly. The trap is that the data inside it is live.
Hiring does not pause for a transaction. On the day the carve-out closes there are candidates mid interview, offers out for signature, and roles the business needs filled in the first quarter under new ownership. If the new entity cannot post a job, schedule an interview, or send an offer on Day One, recruiting stops, and the cost shows up as roles left open while the value creation plan assumes they are filled. A stalled pipeline is a quiet failure that nobody notices until the headcount plan slips.
The right framing is that the ATS migration is a live process handoff, not a back office data move. The buyer plans it the way it would plan any cutover of a system people use every day, with a clear inventory of what is in flight, a target system configured to match, and a moment where hiring switches from the seller's instance to Newco's without a candidate falling through the gap.
The first job is a clean inventory of what the carved-out business has in the system. That means every open requisition that belongs to Newco, every candidate attached to those requisitions, and the stage each one is at. Some requisitions are shared across the parent and will need to be split. Some candidates sit in talent pools that span the whole seller organization, and the buyer has to decide which records belong to the new entity. Getting this scoping right is the difference between migrating the right data and dragging across a tangle that belongs to the seller.
Within that inventory, the in flight items get special attention. An offer that has been extended but not yet accepted, a candidate scheduled for a final interview next week, a background check in progress: each of these is a live commitment that cannot be allowed to vanish. The buyer lists them individually, assigns an owner, and tracks each one through the cutover so that the candidate experience is unbroken. A candidate who went silent during a corporate transition will assume the worst and take another offer.
Historical records need a decision too. Closed requisitions, rejected candidates, and old pipelines carry value for future sourcing but also carry data retention obligations. The buyer chooses what to migrate as active data, what to archive for reference, and what to leave behind, rather than copying the entire history across by default. This keeps the new system clean and keeps the migration in line with the retention rules that govern candidate data.
Candidate records are personal data, and in several jurisdictions they carry specific obligations. Equal opportunity and diversity information, where it is collected, is governed by rules on who can see it and how long it can be kept. In Europe and other privacy regimes, applicant data has consent and retention limits, and a candidate has the right to know what is held and to have it deleted. The buyer cannot treat the ATS as a neutral pile of records to copy wholesale.
The practical answer is a retention decision made before the migration, not after. The buyer confirms what the applicable law requires, what the seller's prior consents allow, and what the new entity's policy will be, then migrates only what fits inside those limits. Records that must be kept for a defined period are archived under the right controls. Records that should not move are filtered out at source. This is the same discipline the wider carve-out applies to personal data, and it keeps the new entity clean from the start rather than inheriting a compliance problem.
Access matters as much as the data. In the seller's instance, recruiters, hiring managers, and agency users all have permissions, and some of those people do not move with the business. The buyer rebuilds the access model for Newco so that only the right people see candidate records, sensitive fields are restricted, and external agency access is re-granted deliberately rather than carried over. A migration that copies the old permission set without review is how a former colleague keeps seeing live candidate data after the close.
An ATS rarely works alone. It feeds new hires into the HRIS, pulls in background checks and assessments from third-party vendors, posts roles to job boards, and connects to offer letter and e-signature tools. Every one of these connections points at the seller's instance, and every one has to be rebuilt for Newco. The feed from the ATS to the HRIS is the one that hurts most if it is missed, because a new hire who is marked as started in recruiting but never lands in the HR system does not exist in payroll, and the first sign of the problem is a missing paycheck.
Third-party vendor connections need their own attention. Background check providers, assessment platforms, and reference tools may be under the seller's contract, which means the new entity needs its own agreements and its own integration credentials before it can run a check. The buyer inventories each vendor, confirms whether the contract transfers or has to be replaced, and re-establishes the connection so a check ordered on Day One actually completes. This connects to the broader work of moving third-party services, which the TSA Exit Acceleration service sequences across the separation.
Job board and careers site links round out the list. The careers page on the new company's website has to point at the new ATS, postings have to be re-syndicated, and applications from those postings have to flow into the new system. A candidate who applies through a stale link that still routes to the seller is a lost applicant nobody sees. The buyer tests the full path, from a job posting to an application landing in the new ATS, before relying on it.
The cutover is the moment hiring switches from the seller's system to Newco's, and it has to be choreographed. The buyer freezes changes in the old instance, migrates the live data, confirms the in flight requisitions and offers all arrived, then opens the new system for recruiters. A short freeze window communicated in advance is far better than a fuzzy period where some hiring happens in one system and some in the other. Clarity about which system is live, and when, prevents the split brain that loses candidates.
Proving it works means walking real scenarios end to end before the team relies on the system. The buyer posts a test requisition, runs a candidate through the stages, extends a test offer, and confirms the new hire flows into the HRIS, that a background check completes, and that the offer letter generates correctly. Testing the full hire path, not just whether records loaded, is what surfaces a broken integration before a real candidate hits it. This is the same proof discipline the buyer applies to the closely related Day One HR and payroll readiness work.
Recruiters and hiring managers need to be ready too. The new ATS has a different layout, different workflows, and different reports, and a recruiter who cannot find a candidate on the first morning will fall back to spreadsheets and email, which is where pipeline data goes to die. The buyer trains the users, documents the new process, and keeps support close in the first weeks. Done well, the migration is invisible to candidates and the pipeline keeps moving as if nothing changed.
An applicant tracking system holds open requisitions, candidate records, interview history, and the hiring workflow. In a carve-out the seller runs it, so Newco needs its own instance before it can hire. The data is live, with offers in flight and candidates mid process, which is why it gets a planned migration rather than a clean restart.
Losing live candidates and active offers. A candidate who stops getting updates, or an accepted offer that falls out of the system, costs a hire and damages the employer reputation. The buyer maps every in flight requisition and offer and confirms each one lands in the new system before the old access is cut.
Yes. Candidate records hold personal data and, in some jurisdictions, EEO or diversity information with retention and consent rules. The buyer decides what to migrate, what to archive, and what to delete under the applicable law and the agreed retention policy, rather than copying everything across by default.
The feed to the HRIS for new hires, background check and assessment vendors, job board postings, and offer letter and e-signature tools all connect to the seller's instance. Each one has to be re-established and tested for Newco, because a broken hire to HRIS handoff means a new employee who does not exist in payroll on day one.
The other people system that holds live records and compliance training history.
Read the article →The benefits side of the people transition new hires depend on from day one.
Read the article →Where new hires from the ATS must land for payroll to run correctly.
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.
Work backwards from the first payroll cycle. Tax registrations and HRIS data have long lead times the TSA clock does not forgive.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →