Corporate Governance, Board Management & M&A ExitsPlaybook3 min readUpdated September 2026

Transition Services Agreements: IT Cutover in a Carve-Out

When a company sells off a division, the buyer almost never has payroll, email, and order systems ready on day one. A transition services agreement is the contract that keeps those systems running, usually with the seller providing them, for a defined window after closing.

Getting the scope, the price, and the end date right matters far more than the surrounding legal boilerplate. A vaguely written TSA is how a six-month handoff turns into an eighteen-month dependency that neither side wanted.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

What Actually Belongs on the Service Schedule

A TSA is only as good as its schedule of services, the exhibit that lists exactly what the seller keeps providing: payroll processing, benefits administration, help desk access, shared ERP or CRM logins, email domains, and sometimes a shared office lease. Each line should name the service, the team responsible, the service level, and the exit condition that ends it.

What belongs on the list is narrower than founders often assume. Strategic services (setting the buyer's own pricing, hiring their own controller) don't belong in a TSA; the point is operational continuity, not ongoing management. If a service isn't on the schedule, the seller has no obligation to keep providing it, so an incomplete list is the single biggest source of disputes once the deal closes.

Pricing and Term: Why Step-Down Pricing Works Better Than a Flat Fee

Most TSAs run three to twelve months, occasionally longer for complex ERP separations, and are priced either cost-plus (the seller's fully loaded cost plus a margin) or as a fixed monthly fee per service. A flat fee for the whole term gives the buyer no incentive to migrate off the seller's systems early, so many agreements now step the price up every 30 or 60 days past an agreed milestone.

That step-up does two things: it compensates the seller for the growing burden of running someone else's operations, and it gives the buyer's integration team a concrete reason to keep cutover on schedule instead of letting it drift.

Say a divested unit relies on the parent's finance system for the first six months at a flat monthly rate. If the buyer knows the rate jumps by half after month six and doubles after month nine, the finance team has a real deadline to plan against instead of an open-ended arrangement that quietly becomes permanent.

Running Governance So the Handoff Doesn't Stall

A TSA needs a named transition manager on each side and a standing steering committee that meets weekly, not a service description that everyone assumes will run itself. That committee tracks which services are still active, which have been cut over, and which change requests are pending.

Change control matters more than it sounds: once the deal closes, the buyer will inevitably ask for something not on the original schedule. Without a documented process for pricing and approving that request, scope creep becomes the norm and the seller ends up providing services it never agreed to.

Set a simple rule at the outset: any request that isn't on the original schedule gets a written change order with its own price and end date before work starts, not a verbal yes from whoever answers the phone. That single habit prevents most of the disputes that later show up as invoices nobody remembers approving.

The IT and Data Cutover Is Where TSAs Actually Fail

Migrating identity and access management, separating shared databases, and re-licensing software that was bought under the parent's enterprise agreement are the hardest parts of any carve-out, and they're where timelines slip. The seller usually can't simply hand over a software license negotiated for its own headcount; the buyer typically has to procure its own.

Data segregation carries its own risk during the transition: while systems are shared, someone at the seller can technically still see the divested unit's data, so access logging and a hard cutoff date for that access need to be spelled out, not left implied.

Common Mistakes That Stretch a TSA Past Its End Date

The same handful of mistakes account for most TSAs that overrun their planned term:

  • No named transition manager on one or both sides, so issues sit unassigned for weeks.
  • Underestimating how long data migration and access re-provisioning actually take, especially for finance systems.
  • The buyer delaying its own hiring or system procurement because the seller's services feel "free" during the flat-fee period.
  • Service definitions vague enough that either side can argue about what's actually included.
  • No pre-agreed exit checklist, so nobody can say definitively when a service is fully cut over.
Executive Capability Standard

What Good Looks Like

A well-run TSA names every service on a single schedule, prices it with a step-down or step-up structure that rewards a fast cutover, and assigns a transition manager on each side who reports into a weekly steering committee until the last service is off the list.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Read through the target's actual IT and HR service inventory before signing, so the schedule of services reflects what really needs to transfer rather than a generic template.
2. Do Manually:Draft the schedule of services and the exit checklist yourself, with outside counsel reviewing only the risk allocation and indemnity language.
3. Delegate:Put a integration lead in charge of the weekly TSA steering committee and give them authority to approve routine change requests without a full renegotiation.
4. Automate:Track each service line, its owner, its cutover date, and open change requests in a shared checklist tool instead of an email thread that nobody can search later.
5. Buy:Bring in a carve-out or post-merger integration specialist to run TSA governance end to end when the transition spans more than a handful of services.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Frequently Asked Questions

What happens if the buyer isn't ready when the TSA term ends?

Most agreements allow a short extension at a higher, pre-agreed rate rather than an automatic renewal at the original price. Build that step-up rate into the original contract so an extension isn't a fresh negotiation under time pressure, and set a hard outside date after which the seller can decline to extend.

Who owns data created while systems are still shared?

The divested business should own its own operating data from the closing date forward, even while the seller's systems host it. The TSA should say this explicitly and require the seller to segregate, export, and then delete that data on a fixed schedule rather than leaving it commingled indefinitely.

Can a TSA be negotiated after the deal has already closed?

It's far riskier to do it that way. TSA terms affect purchase price and risk allocation, so buyers and sellers usually negotiate the schedule of services and pricing alongside the purchase agreement, then sign the TSA at closing so operations never have a gap.

Is cost-plus or fixed-fee pricing more common?

Cost-plus is more common for complex, hard-to-estimate services like shared ERP hosting, since it protects the seller from underpricing effort it can't fully predict. Fixed fees work better for simple, well-understood services like email hosting or a shared office lease.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides