The Post-Acquisition Tech Stack Triage: A 90-Day Playbook for PE-Backed Staffing Platforms

Q1 2026 was the strongest M&A quarter for staffing in three years. Knox Lane's $437M acquisition of Cross Country is only the headline. Under it, dozens of PE-backed platforms are stapling smaller firms onto their operations and quietly hoping the tech sorts itself out.

It does not sort itself out. The first 90 days after close decide whether you keep the margin you paid for or watch it drain away while two systems fight each other.

Most integration plans fail for one reason. They try to fix everything at once. You cannot migrate the ATS, consolidate back office, retrain recruiters, and clean data in the same week. You will break billing and lose people. Sequence matters more than speed.

Here is the playbook I use with portfolio ops leaders. Three phases, 90 days, one goal: consolidate without leaking value.

Days 1 to 30: Freeze and Map

Do not migrate anything in the first 30 days. Your only job is to stop the bleeding and see clearly.

Start by protecting billable activity. Recruiters at the acquired firm keep using their current ATS. Nobody switches tools yet. If placements stall because someone got ambitious with a migration, you lose gross margin you already bought.

Then map both stacks side by side. You are looking for four things:

• Active usage. How many recruiters log into each ATS every day, not how many have licenses.
• Data quality. Duplicate records, dead candidates, and half-filled fields tell you how bad the migration will be.
• Integration cost. What does it take to connect each system to your payroll, invoicing, and reporting?
• Three-year cost. License, support, and switching cost over 36 months, not the sticker price.

Write it down. One page per system. This becomes the evidence you use when someone argues from emotion in week five.

One more thing in this phase. Freeze new tool purchases across both companies. The acquired firm will have three pilots running that nobody remembers signing up for. Kill the noise before you add more.

Days 31 to 60: Pick the Survivor and Sequence the Move

By day 31 you have data. Now you decide which ATS survives.

Do not let the loudest voice win. Leadership often prefers the platform they know. Recruiters prefer the one they actually use. When those two collide, the daily-use tool usually wins because adoption is the thing you cannot buy back later.

Score both platforms on the four factors from phase one. Add the numbers. Pick the winner. Then tell everyone the decision and the reason behind it in plain language. People accept hard calls when they understand the logic. They resist calls that feel random.

Once the survivor is chosen, sequence the migration in this order:

• Back office first. Payroll and invoicing cannot break. Migrate financial systems before candidate systems so cash keeps moving.
• Data second. Clean before you move. Do not carry 40,000 dead records into the new ATS. Migrate active candidates and open reqs, archive the rest.
• Recruiters last. Move people onto the surviving ATS only after the data is clean and the back office is stable.

Build a rollback plan for each step. If the payroll migration goes sideways, you need a way back to the old system inside a day. Assume something will break, because something always does.

Days 61 to 90: Migrate, Train, and Measure

This is where the actual switch happens. You have earned the right to move now because you spent 60 days getting ready.

Migrate in the sequence you built. Back office, then data, then people. Do it in batches, not all at once. Move one office or one desk first, watch it for a week, then scale. A staged rollout gives you a small problem instead of a company-wide one.

Training is not a slide deck. Sit with recruiters at their desks during the first week on the new system. The gap between what a system can do and what people actually do with it is where most integrations quietly fail. Adoption is a change problem, not a software problem. If you want that side handled well, treat it as its own workstream.

Then measure. Pick three numbers before you migrate and watch them daily:

• Placements per week. If this drops and stays down, your integration is leaking value right now.
• Time from req to submit. A new system that slows this down is costing you more than it saves.
• Recruiter logins. If people are not in the surviving ATS every day, you have an adoption problem hiding behind a green migration report.

Compare against your pre-close baseline. If placements dip in week one, that is normal. If they are still down in week four, stop and find out why before you move the next office.

Why the Sequence Beats the Deadline

PE timelines push for speed. I get it. The clock on the investment thesis is real. But a fast integration that tanks recruiter productivity for a quarter costs you far more than a sequenced one that takes 90 days and holds your margin steady.

The platforms that win at this treat the first 90 days as triage, not transformation. Stabilize first. Consolidate second. Improve third. When you try to do all three at once, you get none of them.

This week, do one thing. Pull the active daily-user count for every ATS across both companies. Not licenses. Logins. That single number will tell you more about which system survives than any vendor demo or leadership opinion. Start there.