Transition Service Agreement: Definition, How it Works (+ Template)

A Transition Service Agreement (TSA) is a post-close contract where the seller continues to provide specific operational services to the buyer for a defined period, typically 3 to 12 months across 8 workstreams: IT systems and infrastructure, ERP and accounting, HR and payroll, customer support, procurement and supply chain, tax filing, treasury, and marketing and brand co-use. The longest workstream is almost always IT and infrastructure (12 months on average), followed by ERP/accounting (10 months) and HR/payroll (9 months); marketing co-use and treasury typically wind down inside 3-6 months.

TSAs are essential in carve-outs from a parent company (where the target relies on parent-company systems that cannot be transferred at close) and standard in any deal where the buyer needs operational continuity to avoid disrupting customers. Below is the typical-duration chart by workstream, an interactive 60+ service scope checklist for drafting your TSA, and a calculator that recommends scope and duration based on your deal type, size, integration approach, and complexity.

DealRoom helps thousands of firms streamline processes for divestiture transactions, and in this article, we look at TSAs and their role in divestitures.

We built a free TSA scope checklist to help you make sure you're creating a comprehensive transition service agreement:

If you're wondering about the duration of a TSA service the free calculator we built can help:

The 8 Transition Service Agreement Workstreams in Detail

A Transition Service Agreement is organized around eight standard workstreams that together cover the operational continuity a buyer needs after deal close. Durations range from 3 months (Marketing and Brand Co-Use) to 12 months (IT Systems and Infrastructure), and the specific scope, pricing structure, and negotiation priorities differ for each. The eight workstreams below cover the full standard scope of a middle-market TSA.

1. IT Systems and Infrastructure

IT Systems and Infrastructure services in a TSA typically last 12 months and cover data center hosting, network infrastructure, and email and collaboration platforms. The buyer should specifically negotiate clear cutover criteria, change-control procedures, and dedicated access to seller IT staff during the transition.

IT is almost always the longest workstream in a TSA and the most operationally critical. The target business runs on infrastructure that physically belongs to the seller: data center racks, VPN concentrators, identity providers, software licenses tied to the seller's volume agreements, and a help desk staffed by people who report to the seller. None of this can be transferred at close. A 12-month runway is standard for moving systems to buyer-owned infrastructure, with the highest-risk migrations (ERP-adjacent databases, identity and access management, cybersecurity tooling) clustering in months 9-12.

The two failure modes that show up most often: the seller's best engineers are quietly reassigned to other projects within 60 days of close, and the cutover dates slip 2-3 months past plan because dependencies on parent-company systems were not fully mapped during diligence. Both are preventable in the contract.

• Typical duration: 12 months (can extend to 15+ months for complex carve-outs)
• Common services: Data center hosting, network infrastructure (LAN/WAN/VPN), email and collaboration platforms, endpoint device management, help desk support, cybersecurity tooling, identity and access management, software license assignments
• Pricing structure: Usually cost-plus given the scope variability
• Buyer negotiation focus: Clear cutover criteria, change-control procedures, named-engineer staffing commitments, third-party software consent obligations on the seller, penalty clauses for missed cutover dates

2. ERP and Accounting Systems

ERP and Accounting Systems services in a TSA typically last 10 months and cover ERP system access (SAP, Oracle, NetSuite), chart-of-accounts mapping, and month-end close support. The buyer should specifically negotiate a defined data-extraction protocol so financial data can be pulled out of the seller's ERP at any point during the TSA in a usable format.

ERP and accounting are the second-longest workstream because financial close cycles cannot be safely disrupted. A target that closes on the seller's SAP instance cannot suddenly close on the buyer's NetSuite without months of chart-of-accounts mapping, master-data reconciliation, and parallel-run testing. The buyer typically continues using the seller's ERP for general ledger close, accounts payable, and accounts receivable for 8-12 months while building or extending its own ERP to handle the acquired business.

Audit support is the hidden complexity. The acquired business has audit obligations for the pre-close period that require seller cooperation for years (not months). The TSA should explicitly carve out audit support obligations that extend beyond the TSA termination date, with clear pricing for ad-hoc support requests.

• Typical duration: 10 months (audit support often extends 2-3 years beyond TSA end)
• Common services: ERP system access, chart-of-accounts mapping, GL close, AP/AR processing, fixed asset register migration, month-end and quarter-end close support, audit support
• Pricing structure: Fixed-fee for monthly close support; time-and-materials for migration projects
• Buyer negotiation focus: Data-extraction protocols, audit support commitments that extend past TSA end, parallel-run windows before cutover, dedicated finance staffing

3. HR and Payroll Systems

HR and Payroll Systems services in a TSA typically last 9 months and cover payroll processing (US plus international), benefits administration, and 401(k) plan management. The buyer should specifically negotiate a parallel-run window where both seller and buyer payroll systems process the same cycle, so any exceptions are caught before the seller's system is shut down.

HR and payroll are operationally critical because employees notice immediately when something goes wrong. A missed payroll cycle in week one of buyer ownership is the kind of story that travels and damages morale during an already uncertain period. The TSA should pad timelines aggressively here. A parallel-run window of at least two full pay cycles is best practice: the seller's system and the buyer's system both calculate net pay for every employee, results are reconciled, exceptions are investigated, and only then does the buyer cut over.

Benefits administration is the second tripwire. The seller's health plan, 401(k) plan, and other benefits programs typically continue under the TSA for 6-9 months while the buyer's plans are extended to acquired employees. Coordination on COBRA notifications, ACA reporting, and 401(k) plan rollovers needs explicit ownership assignments in the contract.

• Typical duration: 9 months (parallel-run window of 2+ pay cycles included)
• Common services: Payroll processing (US plus international), benefits administration, 401(k) and pension plans, time and attendance, employee onboarding/offboarding, HRIS access, talent acquisition system, performance management, equity/RSU administration
• Pricing structure: Per-employee per-month fixed fee for processing; cost-plus for benefits
• Buyer negotiation focus: Parallel-run windows, COBRA and ACA notification ownership, 401(k) rollover support, named HR staffing commitments, international payroll vendor consents

4. Customer Support and Call Centers

Customer Support and Call Centers services in a TSA typically last 6 months and cover inbound customer support (voice, chat, email), order management, and CRM platform access. The buyer should specifically negotiate named-agent staffing commitments and SLAs on response time, since support quality is the most visible operational risk to the customer base during a transition.

Customer support is the most customer-facing TSA workstream, which makes it both the highest-stakes and the most negotiated. A missed customer call, a botched order, or a slow refund is a customer-retention event. The TSA needs to commit the seller to maintaining quality, with measurable SLAs and credits for misses. Generic "best efforts" language will not survive contact with reality.

The complication: the agents staffing the seller's call center are typically the seller's employees and will be looking for new jobs the day the deal closes. The TSA should require the seller to retain a named pool of agents for the duration of the workstream, with retention bonuses funded by the buyer if necessary. Some buyers prefer to take over support staff on day one rather than rely on the seller; this works but requires substantially more pre-close planning around hiring, training, and system access.

• Typical duration: 6 months
• Common services: Inbound customer support (voice, chat, email), order management, returns and refunds processing, CRM platform access, customer master data management, loyalty program operation, contact center routing
• Pricing structure: Per-ticket or per-call rate; fixed monthly fee for CRM access
• Buyer negotiation focus: Named-agent staffing, response-time and resolution-time SLAs with credits for misses, customer master data extraction rights, escalation procedures for high-priority issues

5. Procurement and Supply Chain

Procurement and Supply Chain services in a TSA typically last 6 months and cover existing supplier contract servicing under seller terms, procure-to-pay platform access, and warehouse and 3PL services. The buyer should specifically negotiate third-party consent rights so suppliers, landlords, and logistics providers cannot unilaterally terminate existing contracts during the transition.

The single biggest issue in this workstream is third-party consents. The target business has hundreds or thousands of supplier contracts, lease agreements, and logistics arrangements. Many include change-of-control clauses that give the counterparty the right to terminate or renegotiate when the business is sold. The TSA cannot fix this alone; the seller has to actually obtain consents from major counterparties pre-close. The TSA should list every material supplier contract and require seller to either confirm assignment, obtain a consent, or document the gap so the buyer can plan around it.

Warehouse and logistics services are the second pressure point. If the target operates in seller-owned warehouses or uses the seller's freight contracts, those need either physical relocation or contract assignment during the TSA period. Six months is usually enough for straightforward arrangements; complex multi-warehouse operations often need 9-12 months.

• Typical duration: 6 months (9-12 months for complex multi-warehouse operations)
• Common services: Supplier contract servicing under seller terms, procure-to-pay platform access, inventory management, warehouse and 3PL services, freight and shipping, vendor master file management, demand planning
• Pricing structure: Cost-plus for managed services; pass-through for third-party costs
• Buyer negotiation focus: Third-party consent obligations on the seller, list of material contracts and consent status, warehouse transition plan, freight contract assignment terms

6. Tax Filing and Compliance

Tax Filing and Compliance services in a TSA typically last 6 months (longer for cross-border deals) and cover federal income tax filing support, state and local filings, and sales/VAT/GST compliance. The buyer should specifically negotiate a clear allocation of responsibility for any pre-close tax exposures discovered during the TSA period, including audit support obligations that may extend years beyond the TSA itself.

Tax obligations do not align neatly with the close date. The acquired business has open tax periods that started before close and will be filed and audited after. The seller has the institutional knowledge to file those correctly: which positions were taken, what supporting documentation exists, who at the IRS or state revenue authority handles ongoing audits. The TSA needs to commit the seller to provide that support, and the buyer needs to know exactly what those obligations cost and when they end.

Cross-border deals complicate this dramatically. Transfer pricing studies, controlled foreign corporation reporting, value-added tax registrations in foreign jurisdictions, and tax-treaty positions all have multi-year tails. A cross-border TSA may need to commit the seller to 18-24 months of tax support, with explicit pricing tiers for ad-hoc help beyond a baseline scope.

• Typical duration: 6 months (12+ months for cross-border or complex restructuring deals)
• Common services: Federal income tax filing, state and local filings, international tax (foreign subsidiaries), sales/VAT/GST, payroll tax, transfer pricing documentation, tax audit support
• Pricing structure: Fixed-fee for standard filings; time-and-materials for audit support and complex issues
• Buyer negotiation focus: Pre-close exposure allocation in the SPA (not just the TSA), audit support obligations that extend past TSA end, named tax-specialist availability, transfer-pricing documentation hand-off

7. Treasury and Cash Management

Treasury and Cash Management services in a TSA typically last 4 months and cover bank account access and signatory transfer, cash management and forecasting, and FX hedging operations. The buyer should specifically negotiate early bank-account transfer dates, since delays here lock the buyer out of operating the business independently and can expose the buyer to seller fraud risk.

Treasury is the shortest of the operational workstreams because the underlying transfers are administrative rather than systems-level. Bank accounts can be re-titled and signatory authority transferred within weeks if the banks cooperate. The risk is not technical but operational: until the buyer controls the bank accounts, every payment runs through the seller, and the seller's treasury team has to authorize every disbursement.

FX hedging and derivatives are the complex piece. If the target has open FX forward contracts, interest-rate swaps, or other derivatives, those typically cannot be assigned to the buyer without counterparty consent. The TSA needs to clarify whether the seller continues holding those positions until natural expiry or whether they are unwound at close. Either choice has economic consequences that need to be priced into the deal.

• Typical duration: 4 months (FX hedges may extend until natural expiry)
• Common services: Bank account access and signatory transfer, cash management and forecasting, FX hedging, letters of credit and bank guarantees, investment account management, working capital financing, intercompany funding
• Pricing structure: Cost-plus for active services; pass-through for bank fees
• Buyer negotiation focus: Earliest possible bank-account transfer dates, dual-signature controls during transition, hedge treatment (unwind vs. assign vs. natural expiry), letter-of-credit replacement

8. Marketing and Brand Co-Use

Marketing and Brand Co-Use services in a TSA typically last 3 months and cover brand and trademark co-use rights, marketing automation platform access, and website hosting. The buyer should specifically negotiate clear co-existence rules during the brand-transition period (especially around customer communications) so neither party damages the brand value during the rebrand.

This is the shortest standard TSA workstream because the underlying need is narrow: just enough time for the buyer to register its own domain names, build its own website, stand up its own marketing automation, and begin transitioning customer-facing collateral away from the seller's brand. Three months is usually enough; six months is common when the acquired brand will be retained but co-presented alongside the buyer's parent brand.

The trickiest issue is co-existence during the transition. If the seller continues using the original brand for its remaining business while the buyer also uses it for the acquired business, there are non-obvious risks: customer confusion, contradictory marketing campaigns, and disputes over who owns customer relationships. The TSA should spell out exactly which markets, channels, and customer segments each party can use the brand in, with a clear sunset date when the buyer's brand-co-use rights end.

• Typical duration: 3 months (up to 6 months when the acquired brand will continue as a sub-brand)
• Common services: Brand and trademark co-use rights, marketing automation platform access, website hosting and CMS, social media account access, marketing analytics, print and promotional material rights, PR coordination
• Pricing structure: Usually fixed-fee for co-use rights; cost-plus for active marketing services
• Buyer negotiation focus: Co-existence rules by market and channel, customer-communication ownership during transition, social media handle and content rights, sunset date and rebranding plan

A note on pricing structures, durations, and complexity

The eight workstreams above represent the full standard scope of a middle-market TSA, but actual TSA designs vary substantially. Carve-outs from a parent company typically use all 8 workstreams with longer durations across the board (especially IT, ERP, and HR). Standalone private acquisitions usually need only 2-4 workstreams (commonly tax, treasury, and HR for legacy filings and benefits). Public-to-private take-privates need extra runway in IT, ERP, and tax to handle de-listing support, SOX wind-down, and corporate restructuring. Distressed and 363 sales typically compress every workstream by 30-50% and drop marketing co-use entirely. Use the interactive scope checklist and calculator above to model your own TSA design.

Understanding Transition Service Agreements

Divestitures are rarely a matter of identifying an underperforming asset, division, or subsidiary and deciding to sell it.

More often than not, each of these is far more integrated in the seller’s business than they’re aware. Several divisions are likely to share the same information technology, head office functions, and distribution. Customer contracts are also likely to be affected. Effectively carving out what needs to be sold can be complex and time-consuming.

Negotiating this complexity begins during the due diligence phase, when companies determine the milestones that need to be negotiated to ensure a smooth transition of ownership. Once these have been drawn up, they can be articulated in the Transition Service Agreement (TSA).

The TSA is a contract, usually involving consideration, that outlines support services the seller agrees to provide to the buyer for a defined period after the transaction closes.

Once the broad terms of the TSA have been agreed upon between the seller and buyer, estimates are made of the deadlines, costs, and cost drivers for fulfilling each task outlined therein.

Both sides need to be realistic here. Overly ambitious TSAs can create more problems than they solve. Both sides then need to engage fully with the process: a successfully managed transition period can generate value for both parties.

Forward vs. Reverse TSA

A distinction is sometimes made between a forward and a reverse TSA; a forward TSA covers the provision of services from seller to buyer.

A reverse TSA, on the contrary, covers the provision of services from the buyer to the seller.

Although forward TSAs are far more common, anecdotal evidence suggests that reverse TSAs are also on the increase.

When a TSA is Needed

TSAs are most commonly used when it’s not possible to fully separate the parties' businesses at closing. They’re used to maintain the status quo during the transition period until the buyer is ready to run the business independently.

The most common scenario is a carve-out situation. A carve-out is when a business unit is being sold from a larger parent company.

Often in these situations, the seller will continue to provide certain services to the business being carved out for a limited period after closing, until the new, standalone company can operate on its own. Those services are usually operational support functions, such as HR, IT, accounting, and payroll. The carved-out company often doesn’t have its own infrastructure or standalone systems in place yet, so the TSA is used to maintain business continuity until it does.

TSAs are also frequently used in regulatory spin-offs, where licenses or regulatory approvals can’t be transferred to the buyer until after closing. In those situations, the TSA can be used to require the seller to continue hosting any necessary processes or systems until the buyer secures the required licenses and approvals.

TSAs are also used in private equity exits, where a fund sells a portfolio company that may need to rely on the seller’s shared services for a few months after closing, most commonly for support functions such as ERP systems, data migration, or cybersecurity.

Typical TSA Services and Duration

Transition service agreements usually cover core business functions that support day-to-day operations. Common examples include: 

• IT services, such as network access, email, security monitoring, software licenses, and data hosting/migration.
• Finance and accounting activities like accounts payable/receivable, payroll, general ledger, and reporting.
• Human resources operations, including benefits administration, recruiting systems, and employee records.
• Procurement functions like supplier management, purchasing systems, and contract administration.
• Facilities and logistics, including building access, shared office space, security, and mailroom services.
• Legal and compliance support for ongoing litigation, intellectual property, and regulatory reporting.

The duration of a TSA depends on the complexity of the separation. Standalone IT or HR support may only be required for three to six months.

More complex or integrated business operations may require a TSA period of nine to twelve months or more, such as shared ERP systems, supply chains, or cross-border legal and compliance functions.

Effective TSAs are as short as is reasonably possible. The longer the buyer is dependent on the seller’s infrastructure and operations, the higher the risk of delays, additional costs, and blurred responsibility. For this reason, both parties typically agree to an exit roadmap with defined milestones and handover deadlines upfront.

The table below breaks down the typical service areas included in TSAs and their typical durations.

TSA Pricing: Cost-Plus, Fixed-Fee, and Time-and-Materials

TSA pricing follows three standard structures. The right choice depends on how predictable the service scope is, how much risk each side wants to carry, and how much administrative overhead the parties can tolerate.

Cost-plus pricing is the most common structure for carve-out TSAs. The seller bills the buyer for the actual cost of providing each service (typically loaded with a 5-10% markup to cover overhead and a small profit margin). Cost-plus is fairest when the scope is uncertain or likely to expand, since the buyer only pays for what is actually consumed. The downside is administrative burden: the seller must track and allocate costs at a service-by-service level, and the buyer must audit those allocations.

Fixed-fee pricing sets a flat monthly rate per workstream regardless of actual consumption. This works well when the scope is well-defined and stable (for example, payroll processing for a known headcount). The seller takes the risk of underpricing; the buyer takes the risk of overpaying for unused capacity. Fixed-fee TSAs are simpler to administer but typically command a 15-25% premium over equivalent cost-plus pricing because the seller is absorbing the variability risk.

Time-and-materials pricing is most common for project-style services that fall outside the standard TSA scope, like one-time data migrations, system integrations, or custom report builds. The seller charges blended hourly rates for technical staff (typically $150-$350 per hour for IT and ERP work, $200-$450 per hour for tax and treasury specialists) plus pass-through costs for any third-party software or services used.

Most middle-market TSAs use a blended approach: cost-plus for ongoing operational services (payroll, IT support, customer support), fixed-fee for predictable workstreams (marketing co-use, basic accounting close), and time-and-materials for project work (system migrations, audit support).

Benefits of Transition Service Agreements

The benefits of transition service agreements are as follows:

• Smoother transition: TSAs ensure that the small details of transactions, which may once have been overlooked, receive the attention they deserve. This, in turn, leads to smoother transactions.
• Define what is being sold: Business units cannot be sold with ‘one leg in and one leg out.’ It has to be all or nothing. TSAs help managers focus on this concept by highlighting issues that could later destroy value if left unaddressed.
• Value generation: The clarity provided by TSAs generates value for both parties to the transaction. Ultimately, both sides want to return to operations as quickly as possible after the transaction, and a TSA facilitates this.
• Reduced risk: As outlined at the beginning of this article, reducing risk is one of the principal aims of TSAs. Ensuring that small details don’t become big ones reduces risk on both sides of the transaction.

Key Considerations for Drafting an Effective TSA

Among the issues that need to be considered when drafting a TSA include:

• Envision an end state: The seller (or buyer) should consider what the company's end state should be after the transition period wraps up. This will help when setting goals within the TSA.
• Budget accordingly: Remember that almost everything is a cost to the business to some extent—office space, executive time, and even casual Zoom calls between buyer and seller. Ensure that these are accounted for at the outset.
• Ensure contract clarity: ‘Project creep’—the risk of projects moving outside their original scope—dogs many TSAs. By ensuring clarity in the TSA, this can be avoided, and deadlines are more likely to be met.

Collaborate: Whether you’re on the buy or sell side, work with the other side. Everyone stands to create value from the TSA. Collaborating also enables the process to wrap up more efficiently.

TSA in Carve-Outs vs Standalone Acquisitions

The role of a TSA varies dramatically depending on what kind of deal it is. Three patterns dominate.

Carve-out from a parent company. This is where TSAs are most critical and most complex. The target business has been operating inside the parent for years, sharing IT infrastructure, ERP systems, HR platforms, customer support contact centers, and procurement contracts. None of that can be cleanly transferred at close. A typical carve-out TSA covers all 8 workstreams, runs 9-12 months for IT and ERP, and represents 1-3% of total deal value in TSA fees. Sellers in carve-outs frequently struggle to maintain service quality because the people providing the services are no longer their long-term employees, and the buyer should pre-negotiate dedicated transition staffing commitments.

Standalone private acquisition. When the target operates on its own systems independent of the seller, the TSA is much narrower. Often only 2-4 workstreams are needed (typically tax and treasury for legacy filings, and sometimes HR for benefits transition). Durations are shorter (3-6 months for most workstreams) and total TSA fees rarely exceed 0.25% of deal value.

Public-to-private take-private. Take-privates need a specialized TSA that includes de-listing support, SOX wind-down assistance, and complex tax restructuring. The IT and ERP scope is similar to a carve-out, but the tax and finance workstreams are more involved (often 12+ months) because public-to-private deals typically restructure into a new corporate form that triggers significant tax filings and audit work.

TSA M&A Playbook/Template

When drafting a TSA playbook, our M&A Academy at M&A Science has already provided resources for companies going through a divestiture process and in need of TSA.

In summary:

1. Define what services would be required to manage business continuity from day one.
2. Check if the scope of services is appropriate.
3. Define measurables and auditable service levels.
4. Define the duration of services.
5. Check for regulatory and compliance issues.
6. Confirm for potential contractual issues with IT vendors.
7. Prepare indicative costing of TSA services.
8. Outline how governance would work post-close.

Get Your TSA Template Here.

Structure and Key Elements of TSAs

‍