Transition Service Agreements: Key Considerations for Sellers in 2026

A transition service agreement is the bridge between the day a deal closes and the day the buyer can stand the business up on its own. Most founders hear the acronym for the first time in the final round of negotiation, then sign a four-page summary that quietly commits them to running payroll, IT helpdesk, and month-end close for the next year and a half. That is when the surprises start.

We work with founders on the buy-side of more than 60 active mandates each year and see the same TSA mistakes repeat: under-scoped fees, no early-termination penalty, no SLA cap, no key-person commitment, no plan for what happens when the buyer is six months late on standing up its ERP. This guide covers what a TSA is, when one is required, how the fee mechanics work, and the terms that protect the seller after the wire hits. If you are also mapping the broader exit timeline, our piece on the post-sale transition agreement and what to expect covers the ownership transition itself.

Key Takeaways

• TSAs are mandatory in most carve-outs. Roughly 60 to 80 percent of carve-out deals require one. Full company sales need them far less often.
• Term length is 3 to 24 months. The median is 9 to 12 months. Anything longer signals the buyer was not ready to close.
• Cost-plus 5 to 10 percent is market. At-cost giveaways are a seller mistake. Fixed-fee works only when scope is locked.
• Extension fees should escalate. Charge 125 percent of base in months 13 to 18 and 150 percent thereafter.
• SLA caps protect the seller. Liability for service failures should cap at fees paid in the prior three months, not at deal value.
• Key-person clauses cut both ways. If the buyer wants your CFO on the TSA, name the person and price the commitment.

What a Transition Service Agreement Actually Is

A transition service agreement is a standalone contract executed alongside the purchase agreement at closing. It obligates the seller to keep providing specified operational services to the buyer for a defined period after the business changes hands. The services are usually back-office functions the buyer cannot replicate on day one: IT, HR, payroll, accounting and finance, facilities, regulatory reporting, and sometimes customer support or procurement.

The legal structure is simple. The buyer pays the seller a defined fee for each service category, the seller delivers against agreed service levels, both parties exit on a defined end-date or earlier milestone. The TSA is not part of the purchase price. It sits on the buyer’s books as operating expense and on the seller’s books as service revenue. What makes it different from a normal services contract is mutual lock-in: the seller built every system the buyer now depends on, the buyer cannot easily switch providers, and the seller cannot easily walk away. That is why generic services-agreement templates fail in M&A.

When a Transition Service Agreement Is Required vs. Optional

TSAs are nearly universal in carve-outs and uncommon in full company sales.

Carve-out from a parent company. When a corporate parent sells a business unit, the unit was sharing the parent’s IT systems, ERP instance, payroll provider, benefits plans, and often facilities. The buyer is acquiring an operating business with no standalone back office. A TSA is required because the alternative is shutting down operations on day one. Roughly 75 to 80 percent of carve-outs from public companies include a TSA.

Full company acquisition of a founder-led business. The company already has its own IT, payroll, HR, and finance. The buyer inherits the entire operating apparatus. A TSA in this scenario is narrow and short, if it exists at all. Maybe 20 to 30 percent of founder-led deals include a formal TSA, and most that do are under six months.

Roll-up acquisition into a platform. The platform has its own back office and migrates the add-on onto it. TSAs here cover the migration period, usually 60 to 180 days, focused on payroll continuity and customer billing.

The Functional Scope

The functions most commonly covered under a TSA:

Why a Transition Service Agreement Exists at All

The fundamental reason a TSA exists is timing mismatch. The deal closes on a date driven by financing and regulatory approval. The buyer’s operational readiness is driven by ERP implementation timelines, hiring cycles, and IT migration plans. Those two clocks almost never line up.

For carve-outs from corporate parents, the gap is structural. The parent’s IT department serves dozens of business units on one shared ERP. Splitting out the acquired unit’s data, building a new instance, training new staff, and cutting over is a 12 to 18 month project even for a well-resourced buyer.

For PE-backed buyers in a roll-up, the calculation is different. The buyer often wants the add-on running on the platform’s systems within 90 days because that is where the synergies come from. The TSA here is shorter and the buyer is highly motivated to end it early. The seller should welcome that and price extensions punitively.

A second reason TSAs exist is knowledge transfer. The seller’s team knows things the buyer’s documentation will never capture: which vendor calls about the 30-day invoice, which customer signs off PO changes via text, which employee handles the manual reconciliation the ERP does not support. The TSA forces continued contact during the period when this tacit knowledge moves across.

How TSA Fees Are Structured

TSA fee structures fall into three buckets: cost-plus, fixed-fee, and at-cost. Each has tradeoffs, and the right choice depends on how clearly the scope is defined and how predictable the volume is.

Cost-Plus (The Market Default)

Cost-plus charges the buyer the seller’s fully-loaded cost plus a margin of 5 to 10 percent. Fully-loaded cost includes employee compensation and benefits, software licenses, allocated overhead, and third-party fees. The margin compensates the seller for management attention and the opportunity cost of staff tied up servicing the buyer instead of being redeployed.

Cost-plus is right when scope is variable. IT helpdesk volume depends on how often the buyer breaks things. Payroll scales with headcount. The trap with cost-plus is documentation: the seller must track time and expenses by service category, with a monthly invoice cadence and a 30-day dispute window.

Fixed-Fee

Fixed-fee locks in a monthly amount per service category. The seller absorbs the risk that actual cost runs higher. The buyer absorbs the risk that volume runs lower. Fixed-fee works only when scope is genuinely locked. A common compromise is a fixed base fee plus per-unit charges above a threshold. For example: 10,000 dollars per month for payroll up to 500 employees, plus 15 dollars per additional employee.

At-Cost (Avoid This)

At-cost means the seller charges only direct expenses with no margin. This is often pushed by buyers and accepted by sellers who want to be helpful or who fear the TSA will scuttle the deal. It is almost always a seller mistake. At-cost service consumes seller management bandwidth, ties up employees, creates liability exposure, and produces no compensating return. The 5 to 10 percent margin is the minimum needed to make the arrangement worth running.

Worked Example: 12-Month TSA on a 25 Million Dollar Carve-Out

Consider a corporate parent selling a 25 million dollar revenue business unit to a private equity buyer. The buyer needs IT and payroll for 12 months while it builds standalone systems. The seller’s actual costs:

• IT infrastructure: 2.5 FTEs at 130,000 dollars fully-loaded, plus 80,000 dollars in software licenses and cloud hosting allocated to the carved-out unit. Total: 405,000 dollars per year, or 33,750 per month.
• Payroll processing: 0.5 FTE at 95,000 dollars fully-loaded, plus 12,000 dollars in payroll software fees and tax filings. Total: 59,500 per year, or 4,960 per month.

Combined fully-loaded cost: 464,500 per year. At cost-plus 7 percent, the seller charges the buyer 497,015 per year, or 41,420 per month. The 32,515 dollar annual margin covers management oversight and creates a small incentive to honor the agreement.

If the buyer’s ERP implementation slips and they ask for an extension, the seller should charge 125 percent of base in months 13 to 18 (51,775 per month) and 150 percent in months 19 to 24 (62,130 per month). That escalation forces the buyer to commit resources to ending the TSA rather than treating it as cheap infrastructure.

Seller Liability and Indemnification Under a TSA

The single biggest seller mistake in TSA negotiation is accepting uncapped or poorly-capped liability for service failures. If the seller’s payroll processing fails one month and 200 employees miss their direct deposit, the resulting damages could run into hundreds of thousands of dollars in legal exposure plus reputational harm. The seller agreed to a 60,000 dollar TSA and is now staring at a 500,000 dollar claim.

Standard Liability Cap

The market-standard cap for TSA service failures is fees paid by the buyer in the trailing three to six months. Some agreements cap at total fees paid under the entire TSA. What is not defensible is accepting the same liability caps that apply to the purchase agreement itself, which often equal 10 to 15 percent of deal value. A 25 million dollar deal with a 10 percent indemnification cap means 2.5 million in seller liability under the purchase agreement. Pulling the TSA under that umbrella is a 40x escalation of seller exposure.

Carve-Outs From the Cap

Buyers will push for carve-outs covering fraud, willful misconduct, gross negligence, breach of confidentiality, and data privacy violations. Fraud and willful misconduct carve-outs are universal. Gross negligence is a gray area worth pushing back on because the standard varies by jurisdiction. Confidentiality and data privacy carve-outs are increasingly common given regulatory exposure under HIPAA, GDPR, and state privacy laws.

Indemnification Mechanics

A workable structure: Seller indemnifies buyer for direct damages caused by seller’s TSA breach, subject to the cap. Buyer indemnifies seller for third-party claims arising from buyer’s use of services under the TSA, including customer claims, employee claims, and regulatory actions tied to post-close operation. Mutual indemnification for IP infringement claims related to software the parties license to each other. The buyer indemnification side is often overlooked by sellers and is critical, since the seller is providing services to a business it no longer owns.

Key Terms Every Transition Service Agreement Needs

The TSA should be a detailed contract, not a four-page summary appended to the purchase agreement. A solid TSA runs 30 to 60 pages including schedules. The schedules are where the actual service definitions live and where most disputes get prevented or created.

1. Service Definitions

Each service must be defined with enough specificity that both parties know what is in and what is out. “IT support” is not a service definition. “Maintenance of the existing Microsoft 365 tenant, including user provisioning, security policy management, and tier-one helpdesk support during business hours 8am to 6pm Central, excluding application development and security incident response” is. Write the schedules carefully and price the add-ons in advance.

2. Term and Termination

The TSA should specify a hard end-date for each service. Different services can have different end-dates: payroll might end at month 6 while ERP access runs to month 18. Each service should also have early termination rights for the buyer (typically 60 to 90 days notice) and termination for cause for the seller in case of non-payment. Extension terms should be defined in advance: fee structure (125 percent in months 13 to 18, 150 percent thereafter), maximum number, and notice required.

3. Fees and Invoicing

The TSA should specify invoicing frequency (monthly), payment terms (net 30), late payment interest (1.5 percent per month), and a 30-day dispute window followed by mediation.

4. Service Levels (SLAs)

SLAs cover services where failure has real consequences. Payroll: accuracy 99.5 percent, on-time 100 percent. IT helpdesk: response within 4 hours during business hours. Financial reporting: close within 10 business days. The remedy for SLA breach should be service credits, not damages. A 10 percent credit on the monthly fee for a missed SLA is standard. Credits avoid the liability-cap problem and create the right incentive without exposing the seller to litigation.

5. Key-Person Commitments

If the buyer wants specific seller employees committed to the TSA, name them and price the commitment. A clause obligating the seller’s CFO to dedicate 25 percent of her time to the TSA for 12 months is a meaningful concession. The seller should be paid for that time and should be able to substitute another qualified employee if the named person leaves.

6. Intellectual Property

The TSA must address IP created during the engagement and licenses the buyer has to seller-owned IP used in delivering services. Custom code written during the TSA usually belongs to the buyer. License to seller-owned platforms is usually limited to TSA scope and TSA duration with no rights to use after termination.

7. Data Privacy and Security

The TSA should specify which party is the data controller and which the processor. It should require the seller to maintain security controls equivalent to those in place at closing, define breach notification timelines (24 to 72 hours is market), and address compliance with applicable privacy law. Carve-outs involving HIPAA-regulated data need a Business Associate Agreement; payment card data triggers PCI-DSS obligations.

8. Dispute Resolution

TSAs should specify a mandatory escalation path: operational disputes go to designated points of contact first, then senior executives, then mediation, then arbitration or litigation. The path forces the parties to talk before lawyering up, which is essential because both sides remain operationally dependent on each other during the dispute.

The Five Most Common Seller Mistakes

Mistake 1: Under-Scoping Fees

Sellers consistently underestimate the time their team will spend on TSA work. The CFO who plans for 5 percent of her time on buyer questions spends 25 percent. The IT manager who allocates one helpdesk ticket per week handles ten. Track time during diligence and price accordingly.

Mistake 2: No Early-Termination Penalty for the Buyer

If the buyer can walk away with 30 days notice and no penalty, the seller has staffed a service organization with no customer commitment. Insert a minimum-fee provision: buyer pays for at least 6 months even on earlier termination, or an early-termination fee equal to 50 percent of remaining fees.

Mistake 3: No Cap on SLA Penalties

SLA credits should cap at the monthly fee for that service. Without a cap, a bad month can wipe out a year of revenue.

Mistake 4: Accepting Purchase-Agreement Liability Caps for TSA Breaches

The TSA needs its own liability cap, much smaller than the purchase agreement cap, applied only to TSA breaches.

Mistake 5: No Plan for the Seller’s Wind-Down

The seller needs to know what happens to its TSA team when the TSA ends, whether that means redeployment, severance, or moving people back to other roles. Plan it now, not 60 days before the end-date.

How a Transition Service Agreement Differs From an Earnout or Consulting Agreement

Sellers often confuse the TSA with two related post-close instruments. They are different.

An earnout is contingent purchase price. The seller receives additional payment if the business hits defined milestones after close. Earnouts run through the purchase agreement. Our piece on how founders can transition out without crashing the business covers earnout mechanics.

A consulting agreement is a personal services arrangement with the founder for strategic advice or relationship continuity after close. It pays the founder personally, runs 6 to 24 months, and is advisory.

A TSA is operational service delivery from the corporate seller to the corporate buyer, paid as service revenue, scoped to specific back-office functions. TSAs do not pay the founder. They pay the company that used to own the business. A single deal can include all three instruments and each should be negotiated independently.

Practical Steps Before Signing a TSA

Sellers should do the following before the TSA is finalized.

1. Build a service inventory. List every back-office function the buyer might need, who provides it today, what it costs fully-loaded.
2. Track time during diligence. If your team is fielding buyer questions, track the hours. That data calibrates the TSA staffing model.
3. Map third-party dependencies. List every software license, vendor contract, and data feed that needs to be assigned or novated for the TSA period.
4. Draft SLA targets first. Decide what performance you can reliably deliver before the buyer dictates targets you cannot meet.
5. Price extension fees up front. Decide the escalation schedule before negotiation starts.
6. Plan the wind-down. Decide what happens to TSA staff when the agreement ends and build that cost into the fees.
7. Read the buyer’s diligence list for clues. The depth of the buyer’s operational diligence signals how heavily they will lean on the TSA.

Closing the Loop With CT Acquisitions

Most founders have never negotiated a TSA. The buyer’s deal team has done it 50 times. That asymmetry is where sellers give up value. We sit on the buy-side of the table for our PE and family office partners, which means we see the playbooks buyers use, and when we represent a seller we know which TSA terms buyers concede easily and which they will fight on. If you are weighing an exit, start with our guide to transitioning out of your business or a direct conversation via the call page or our capital partner network. We do not charge sellers.