Transition Service Agreements (TSAs) in Business Acquisitions

When a buyer acquires a business, operational continuity rarely happens automatically. The seller's IT systems, back-office processes, vendor relationships, and institutional knowledge don't simply transfer at closing. A Transition Service Agreement (TSA) bridges this gap by contractually obligating the seller to continue providing specified services to the buyer for a defined period after the deal closes.

TSAs are especially common in carve-out transactions - where a division or product line is separated from a larger parent company - but they also arise in full-company acquisitions when the buyer lacks the infrastructure to absorb certain functions immediately. A well-structured TSA protects the buyer from Day One operational disruptions while giving both parties a clear roadmap toward full separation.

This guide covers when TSAs are necessary, what provisions they should include, how to negotiate them effectively, and the pitfalls that catch first-time acquirers off guard.

A Transition Service Agreement is a contract between a buyer and seller in which the seller (or in some cases, the buyer) agrees to provide certain operational services for a specified duration after the transaction closes. The agreement defines the scope, quality, duration, and cost of each service, creating accountability and measurability during the transition period.

TSAs typically cover functions that the acquired business relied on from the seller's broader corporate infrastructure. Common examples include payroll processing, IT hosting and support, human resources administration, accounting and financial reporting, procurement systems, and facilities management. Without a TSA in place, the buyer would need to replicate or replace all of these functions before closing - an unrealistic expectation in most deals.

The TSA is generally negotiated alongside the purchase agreement and closing documents, though it may be executed as a separate agreement at closing. In practice, the TSA is one of the most detail-intensive documents in the entire transaction because it must accurately describe operational processes that may have evolved informally over many years.

Not every acquisition requires a TSA, but certain deal structures and circumstances make them essential. Understanding when a TSA adds value helps buyers plan their transition strategy during due diligence rather than scrambling after closing.

• Carve-out transactions:When a division is separated from a parent company, the division almost certainly shares corporate systems and services. The parent's ERP, email platform, payroll provider, benefits administration, and IT infrastructure must continue supporting the carved-out entity until the buyer establishes independent systems.
• Platform acquisitions by search funds: First-time acquirers, including search fund entrepreneurs, often need the seller to continue managing certain back-office functions while the new owner focuses on learning the core business operations.
• Complex IT environments: When the target business runs on proprietary or heavily customized technology that cannot be migrated quickly, a TSA ensures system continuity while the buyer plans a technology transition.
• Regulatory or licensing dependencies: Certain industries require licenses, permits, or certifications that are held by the seller entity. The TSA may cover the seller continuing to operate under those licenses until the buyer obtains its own.
• Shared facilities: When the acquired business operates in space owned or leased by the seller, a TSA (or a separate short-term lease) provides occupancy continuity.

Conversely, TSAs are less common in straightforward asset purchases of small businesses where the buyer steps directly into the owner-operator role and assumes all vendor relationships independently.

A strong TSA addresses dozens of operational details. The following provisions form the backbone of most agreements and should be carefully tailored to the specific transaction.

The TSA should include a detailed schedule (often called a Service Schedule or Exhibit A) listing every service the seller will provide. Each service entry should specify:

• A clear description of the service and its scope
• The personnel or department responsible for delivery
• Hours of availability (e.g., business hours only vs. 24/7)
• Any tools, systems, or platforms involved
• Dependencies on the buyer's cooperation or data access

Common service categories include information technology (hosting, help desk, network administration), finance and accounting (AP/AR processing, monthly close, tax compliance), human resources (payroll, benefits administration, recruiting support), procurement (vendor management, purchase order processing), and facilities (building access, maintenance, security). Vague descriptions invite disputes - aim for specificity comparable to a third-party vendor contract.

TSA terms typically range from three to twenty-four months, depending on the complexity of the services and the buyer's readiness to assume them. Best practices include:

• Staggered end dates: Different services may have different durations. Payroll migration might take three months, while ERP transition could take twelve.
• Extension options: The buyer should negotiate the right to extend individual services (typically in 30- or 90-day increments) at a pre-agreed rate, subject to reasonable advance notice.
• Early termination rights: The buyer should be able to terminate individual services early (with notice) as it completes migration, avoiding unnecessary costs.
• Maximum duration caps:Sellers often insist on a hard stop date - commonly eighteen to twenty-four months - after which no extensions are available regardless of the buyer's readiness.

TSA pricing generally follows one of three models:

1. Cost-plus:The seller charges its actual cost of providing the service plus a markup (commonly five to fifteen percent). This is the most common approach and aligns with the principle that the seller should not profit excessively but also should not subsidize the buyer's transition.
2. Flat fee: A fixed monthly fee for each service, regardless of usage volume. Simpler to administer but may not reflect actual costs if usage fluctuates.
3. Usage-based: Pricing tied to measurable metrics - per-employee for HR services, per-transaction for IT, per-square-foot for facilities. More complex to track but fairer when service volumes are uncertain.

Pricing should also address cost escalation for extensions. Many agreements include a step-up (an additional ten to twenty-five percent above the base rate) for service extensions beyond the initial term, incentivizing the buyer to complete migration on schedule.

SLAs define the quality and performance standards the seller must meet. At a minimum, the TSA should require the seller to provide services at the same level of quality, timeliness, and priority that existed before the transaction. Specific SLA provisions might include:

• Response time requirements for IT helpdesk tickets
• Uptime guarantees for hosted systems
• Processing deadlines for payroll and accounts payable
• Accuracy standards for financial reporting
• Remediation procedures and escalation paths when SLAs are missed

The baseline standard - "same level of service as provided prior to closing" - is important because it prevents the seller from deprioritizing the buyer's needs after the deal closes.

The TSA should include provisions that facilitate the buyer's eventual independence:

• Knowledge transfer obligations: The seller must provide documentation, training, and reasonable access to personnel to help the buyer build internal capabilities.
• Data migration support:The seller must cooperate in extracting and transferring data from its systems to the buyer's new platforms.
• Parallel run periods: For critical systems, the agreement may require a period where both the old and new systems operate simultaneously to verify data integrity.
• Post-expiration cooperation: Even after a service ends, the seller should remain available for reasonable questions and issue resolution for a limited period.

TSA negotiations often happen late in the deal process when both parties are focused on closing. This creates pressure to accept vague terms - a mistake that invariably leads to post-closing friction. Here are strategies for both sides:

• Start early in due diligence: Identify TSA-dependent services during your due diligence review and begin drafting the service schedule before the purchase agreement is finalized.
• Map every dependency:Walk through daily, weekly, monthly, and annual operational processes to identify every point where the target business depends on the seller's infrastructure or personnel.
• Price realistically:Buyers should accept that TSA services have a cost. Low-balling the pricing creates resentment and reduces the seller's motivation to provide quality service.
• Include governance mechanisms: Establish a joint transition committee with regular meetings, escalation paths, and defined decision-making authority.
• Build in flexibility: Neither party can predict every transition challenge. Include change-order procedures for adding, modifying, or removing services as circumstances evolve.
• Align incentives: Step-up pricing for extensions and early-termination rights give the buyer financial motivation to migrate quickly while protecting the seller from indefinite obligations.

Even experienced acquirers encounter TSA-related problems. The most frequent pitfalls include:

• Underestimating transition timelines: Buyers routinely assume they can migrate off TSA services faster than reality allows. IT system migrations, in particular, almost always take longer than planned. Build in at least fifty percent buffer beyond your initial estimates.
• Insufficient service descriptions:Vague language like "IT support" or "accounting services" invites different interpretations. Every service should be described with enough specificity that a neutral third party could determine whether the obligation has been met.
• Ignoring seller motivation:After closing, the seller has limited incentive to prioritize the buyer's needs. SLAs with teeth (financial penalties for missed deadlines) and positive incentive structures (bonuses for successful migration support) help maintain alignment.
• Failing to plan for Day One:Some functions - payroll, customer-facing systems, regulatory reporting - cannot tolerate any gap. Identify these "Day One critical" services early and ensure the TSA provides seamless continuity.
• No dispute resolution mechanism: Without a defined escalation and dispute process, disagreements about service quality or scope can fester and damage the post-closing relationship. Include mediation or arbitration provisions.
• Data access and privacy gaps:The TSA must address how the seller handles the buyer's data during the transition, including confidentiality obligations, data security standards, and return/destruction of data upon service termination.

While a standard TSA involves the seller providing services to the buyer, a reverse TSA works in the opposite direction: the buyer provides services to the seller. Reverse TSAs arise in specific circumstances:

• When the buyer acquires key infrastructure:If the acquired business owned shared systems or facilities that the seller's remaining operations depend on, the buyer may need to continue providing those services to the seller temporarily.
• In partial acquisitions: When the buyer acquires a controlling interest but the seller retains a minority stake and continues operating related businesses that share infrastructure with the acquired entity.
• When the acquired entity served as shared services center:The target business may have provided centralized services (IT, accounting, HR) to the seller's other divisions. Those services don't disappear at closing.

Reverse TSAs require additional care because the buyer is now in the unfamiliar position of being a service provider. The buyer must staff appropriately, maintain service quality for an entity it doesn't control, and manage the complexity of supporting an outside organization while simultaneously integrating the acquired business.

In deals involving both a TSA and a reverse TSA, the agreements are often cross-referenced, with netting provisions that offset fees owed by each party.

The best TSA is one that ends on time - or early. A disciplined exit plan, developed before closing and refined during post-acquisition integration, is essential for achieving clean separation.

1. Prioritize by risk and complexity: Rank TSA services by operational risk (what happens if this service fails?) and migration complexity (how long will replacement take?). Address high-risk, high-complexity services first.
2. Assign internal ownership: Each TSA service should have a designated internal owner responsible for planning, executing, and verifying the migration.
3. Select replacement solutions early:Don't wait until month six of a twelve-month TSA to evaluate replacement vendors. Begin vendor selection during due diligence or immediately after closing.
4. Run parallel systems: For critical functions, operate both the TSA service and the replacement system simultaneously for at least thirty days before cutting over.
5. Document everything:Capture process documentation, configuration settings, data formats, and tribal knowledge from the seller's team throughout the TSA period.
6. Conduct formal cutover reviews: Before terminating each service, conduct a readiness review confirming that the replacement system is fully operational and tested.

Active management of the TSA relationship is critical to a successful transition. Key governance elements include:

• Joint steering committee: Senior representatives from both parties meeting regularly (weekly or biweekly) to review service delivery, address issues, and track migration progress.
• Service delivery reports: The seller should provide regular reports documenting service performance against SLAs, any incidents, and resolution status.
• Change management process: A formal procedure for requesting changes to service scope, adding new services, or modifying SLAs, including cost implications and approval requirements.
• Escalation procedures: Clear escalation paths - from operational contacts to service managers to executive sponsors - ensuring issues are resolved promptly.
• Financial tracking: Regular reconciliation of TSA invoices against agreed pricing, with dispute resolution for billing disagreements.

Effective governance keeps the TSA on track and preserves the post-closing relationship between buyer and seller - a relationship that often matters beyond the TSA itself, particularly when the deal includes earnout provisions or seller financing that create ongoing interdependency.

TSA terms typically range from 3 to 24 months, depending on the complexity of services and the buyer’s readiness to assume them. According to Deloitte’s research on carve-out transactions, the median TSA duration is 12 months, with IT-related services often requiring the longest transition periods (12-18 months) due to the complexity of system migration. Payroll and HR functions typically transition in 3-6 months, while accounting and financial reporting may need 6-12 months. Best practice is to use staggered end dates for different services rather than a single expiration, with extension options available in 30- or 90-day increments at pre-agreed rates. Most sellers insist on a hard stop date of 18-24 months after which no extensions are available, creating urgency for the buyer to complete migration on schedule.

TSA pricing most commonly follows a cost-plus model, where the seller charges actual cost of service delivery plus a 5-15% markup. PwC’s research on TSA management reports that the total cost of a TSA typically represents 2-5% of the annual revenue of the acquired business. Pricing should address cost escalation for extensions, many agreements include a 10-25% step-up above the base rate for service extensions beyond the initial term, incentivizing the buyer to complete migration on schedule. Alternative pricing models include flat monthly fees (simpler to administer but may not reflect actual costs) and usage-based pricing tied to measurable metrics such as per-employee for HR services or per-transaction for IT. The buyer should also budget for the cost of building replacement systems in parallel with TSA services, which Ernst & Young estimates at 1.5-3x the annual TSA cost for full separation.

The most frequent and costly mistake is underestimating transition timelines. McKinsey & Company’s research on separation management shows that buyers routinely assume they can migrate off TSA services 30-50% faster than reality allows, particularly for IT system migrations. This optimism leads to costly extensions at step-up rates and, in worst cases, service disruptions when TSAs expire before replacement systems are fully operational. The second most common mistake is insufficient service descriptions, vague language like “IT support” or “accounting services” invites different interpretations and post-closing disputes. Every service should be described with enough specificity that a neutral third party could determine whether the obligation has been met. Building at least 50% buffer beyond initial timeline estimates and investing in detailed service schedules during negotiation prevents both problems.