When a company sells a division that still shares payroll, IT, or accounting with its former parent, the acquired business cannot always stand on its own the day the deal closes. A transition services agreement, or TSA, bridges that gap. It is a contract in which the seller (occasionally the buyer) provides specified support services for a defined period after closing so the business keeps running while the parties separate and integrate systems. TSAs appear most often in carve-outs, where an integrated unit is peeled away from a larger enterprise and left temporarily dependent on shared infrastructure it does not yet control.
What a transition services agreement is
A TSA formalizes the temporary support one party owes the other after a transaction closes. The document typically travels alongside the purchase agreement and functions as an operational bridge: the buyer gains time to build or migrate to standalone systems, and the seller agrees to keep the lights on in the meantime. Because the divested unit may rely on the seller's enterprise resource planning system for billing, its email domain for communication, or its bank relationships for treasury, an abrupt cutoff at close would risk missed payroll runs, broken invoicing, and lost data. The TSA prevents that by defining exactly what continues, for how long, and at what cost. In practice the agreement pairs a legal framework with a set of detailed service schedules, one per function, that operational teams on both sides can execute against day to day.
The core tension a TSA manages is that closing a deal is a legal event, but separating two intertwined businesses is an operational process that takes months. Signing the purchase agreement transfers ownership on a single date, yet the systems, contracts, and people that made the divested unit run were built to serve the whole enterprise. A TSA gives both sides a governed way to unwind that entanglement in stages rather than all at once.
TSAs matter most in carve-out deals. A strategic acquirer that already runs its own back office may need little transitional help, while a financial buyer acquiring a carved-out business often lacks standalone infrastructure entirely and leans heavily on the agreement for continuity. The greater the operational entanglement at signing, the more services the TSA usually covers and the longer it tends to run.
What services a TSA typically covers
The services in a TSA track the shared functions the divested business cannot immediately replace. Common categories include:
- Information technology: access to core systems, ERP platforms, email, networks, and application support.
- Payroll and human resources: running pay cycles, benefits administration, and HR record management during separation.
- Accounting and finance: general ledger access, accounts payable and receivable processing, treasury, and financial reporting.
- Facilities and procurement: shared office space, vendor relationships, and purchasing support.
- Data migration: transferring historical records from the seller's environment into the buyer's.
Practitioners stress that the service schedules should be drafted at the level of individual services rather than broad functional headings. Vague scope is repeatedly identified as the most common source of post-closing TSA disputes, so a well-built schedule specifies which systems, which users, and which support hours are covered.
Service levels and standards
Beyond listing services, a TSA sets the standard to which they must be performed. A frequently negotiated point is whether the seller commits to a defined service level or simply provides services on an "as is" basis using commercially reasonable efforts. Sellers often prefer the lighter standard, arguing they are not professional outsourcing vendors and should not be held to standards a dedicated provider would offer. Buyers generally push for a benchmark tied to how the services were performed before the deal, so quality does not degrade the moment ownership changes. Service level provisions may reference historical performance, response times, and remedies if standards slip. Governance mechanics usually accompany the standard, including named service managers on each side, regular status meetings, escalation paths for problems, and a change-control process so any addition to scope is documented and priced rather than absorbed informally. Liability terms are also negotiated here, commonly featuring caps on direct damages and waivers of consequential damages, with carve-outs for issues such as negligence, data breaches, and confidentiality violations.
Duration and extensions
TSAs are meant to be temporary. Most run for an initial period of roughly six to twenty-four months, with many landing in the twelve to eighteen month range, though the right length depends on service complexity and how quickly the buyer can build replacement capability. IT and ERP migrations tend to require the longest runways, while functions such as customer support can often be handed over sooner.
Extension rights are a classic negotiation. Buyers typically want the flexibility to extend on comfortable timelines in case standalone systems are not ready, while sellers prefer a rapid, clean exit from responsibilities that sit outside their core business. Agreements often reconcile this tension with a limited number of extensions, defined notice periods, and stepped-up pricing that discourages an open-ended arrangement.
Pricing and cost-plus structures
How services are priced is among the most heavily negotiated elements of a TSA. Common approaches include:
- At-cost or fully allocated cost: the buyer reimburses the seller's actual cost of providing the service.
- Cost-plus: direct cost plus a defined markup, frequently a modest single-digit percentage, compensating the seller for administrative burden and retained capacity.
- Fixed fee: a set monthly charge per service, simpler to administer but potentially detached from actual cost.
- Unit or volume pricing: charges tied to usage, such as per transaction or per user.
Sellers often favor cost-plus because pure cost-based pricing can be hard to measure and can create disincentives inside profit-measured business units. Buyers scrutinize any markup closely. A recurring theme in the literature is that both the existence and size of a markup deserve careful negotiation, and that pricing should generally reflect the seller's real cost of service rather than becoming a profit center. Escalating fees on extensions are a common tool to keep the transition moving, since a rising monthly charge gives the buyer a financial reason to complete its standalone build on schedule rather than leaning on the seller indefinitely.
Exit, wind-down, and knowledge transfer
A TSA is only as good as its off-ramp. Strong agreements define exit criteria before signing, so both sides know what "done" looks like. Typical milestones include tested replacement systems, completed staff training, documented processes, and confirmed knowledge transfer from the seller's team to the buyer's. Wind-down provisions may allow the buyer to terminate individual services early as each one is migrated, rather than waiting for the whole agreement to lapse. Third-party consents can complicate exit as well: software licenses and vendor contracts sometimes require the licensor's approval before a seller may extend a system to a divested entity, occasionally involving many separate consents and fees.
Common pitfalls
Several problems recur across TSA-heavy deals:
- Scope creep: services expanding beyond the original schedule, turning a defined bridge into an ill-defined support obligation.
- Vague definitions: functional headings without service-level detail, which fuel disputes over what was actually promised.
- Underpricing: markups or fixed fees that fail to cover the seller's true cost and administrative load.
- Dragging on: transitions that outlast their purpose because the buyer underinvested in standalone readiness, sometimes making extension fees exceed the cost of building the capability outright.
- Last-minute drafting: TSAs relegated to the final rush before signing, without input from the operational experts who understand the real dependencies.
How TSAs fit a prepared sale process
For lower-middle-market owners, TSA exposure is easier to manage when a business enters the market with clean, documented, and reasonably separable operations. A company whose financials, systems, and vendor relationships are well organized before diligence tends to need a narrower and shorter TSA, which reduces friction in negotiation and lowers the risk of a lingering post-close entanglement. Preparation platforms such as Bankerly organize this kind of operational and financial documentation as part of readying a company for sale, which can make the eventual separation cleaner.
Educational note
This article is general educational information about how transition services agreements work in M&A. It is not legal, tax, or investment advice, and TSA terms carry significant legal and financial consequences that vary by deal. Anyone evaluating or negotiating a TSA is well served by qualified counsel and advisors familiar with the specific transaction.
Sources
Frequently asked questions
- What is a transition services agreement in an M&A deal?
- It is a contract in which the seller (or sometimes the buyer) provides specified support services such as IT, payroll, HR, and accounting for a defined period after closing, so the acquired business keeps running while systems are separated and integrated. TSAs are most common in carve-outs, where a divested unit remains temporarily dependent on shared infrastructure.
- What services does a TSA usually cover?
- Common categories include information technology and ERP system access, payroll and human resources, accounting and finance, facilities and procurement, and data migration. Practitioners recommend drafting service schedules at the level of individual services rather than broad functional headings, because vague scope is a leading source of post-closing disputes.
- How long do transition services agreements typically last?
- Most TSAs run for an initial period of roughly six to twenty-four months, with many falling in the twelve to eighteen month range. The right length depends on service complexity and how quickly the buyer can build replacement capability. IT and ERP migrations often need the longest runways, and agreements frequently include limited extension rights with defined notice periods.
- How are TSA services priced?
- Common models include at-cost reimbursement, cost-plus (direct cost plus a modest markup, often a single-digit percentage), fixed monthly fees, and volume-based unit charges. Sellers often favor cost-plus to cover administrative burden and retained capacity, while buyers scrutinize any markup. Pricing generally aims to reflect the seller's real cost rather than serve as a profit center.
- What are the most common TSA pitfalls?
- Recurring problems include scope creep, vague service definitions, underpricing that fails to cover the seller's true cost, transitions that drag on because the buyer underinvested in standalone readiness, and last-minute drafting without input from operational experts. Clear exit criteria and knowledge-transfer milestones help avoid a lingering, open-ended arrangement.
Considering a sale in the next few years? See what a prepared process looks like.
Keep reading