The purchase agreement is signed, the wire has cleared, and the business technically belongs to someone else. But the seller is still showing up most mornings, still answering questions from the new owner's staff, and still logging into systems nobody has transferred yet. That arrangement usually has a name: a transition services agreement, or TSA.
A TSA is a separate contract, negotiated alongside the main purchase agreement, that spells out what the seller will keep doing for the buyer after closing and for how long. It sounds like a minor detail next to the purchase price. In practice, a poorly scoped TSA can create months of friction, unpaid obligations, and confusion about who is actually running the business.
Photo by Ketut Subiyanto on Pexels
What a Transition Services Agreement Actually Covers
A TSA is not a formality tacked onto the deal at the last minute, even though it sometimes gets treated that way. It is a functional operating document that answers a narrow but important question: which parts of the old ownership structure does the business still depend on, and who is responsible for keeping those functions running while the buyer builds its own capacity.
That can include the seller's accounting staff continuing to close the books for a few months, the seller's IT contractor maintaining servers until the buyer migrates to new infrastructure, or the seller personally introducing the new owner to long-standing customers and vendors. Some TSAs cover a single function for thirty days. Others run a year or more across several departments.
Because the scope varies so widely, one of the first topics to review with your business sale advisor is what the buyer is actually asking for and whether that request is proportionate to the deal itself. A TSA that quietly obligates the seller to run half the company for a year is a very different commitment than a two-week handoff of a few passwords.
Why Buyers Ask for a TSA in the First Place
Buyers rarely ask for a TSA out of caution alone. They ask because certain functions cannot be cut over on closing day without real operational risk. Payroll has to run. Customer orders have to ship. Software licenses have to stay active. If the buyer's own team is not ready to take over those functions immediately, a gap opens up, and the TSA exists to bridge it.
This is worth understanding from the seller's side too, because it reframes the negotiation. A TSA is not the buyer asking for a favor. It is the buyer identifying a dependency risk and asking the seller to help manage it during a defined window. Sellers who understand that framing tend to negotiate scope and pricing more effectively than sellers who treat the TSA as an afterthought.
Common Services Included in a TSA
IT and Software Systems
Software and infrastructure are among the most common TSA line items, and also among the easiest to underestimate. Accounting platforms, customer databases, point-of-sale systems, and internal file storage were often built around the seller's accounts and license agreements. Migrating everything to the buyer's systems on day one is rarely realistic.
A TSA will typically specify which systems the seller keeps running, for how long, and what happens if the migration takes longer than planned. This is a good area to review with whoever handled your due diligence, since IT transition timelines are notoriously optimistic in the first draft of a TSA.
Photo by Jakub Zerdzicki on Pexels
Finance and Accounting Support
Month-end close, accounts payable, payroll processing, and tax filings do not pause because ownership changed hands. A TSA often has the seller's bookkeeper or controller continue these functions for a set number of cycles, sometimes with the buyer's team shadowing them to learn the process.
This is a natural point to loop in your tax advisor, since who is responsible for filings that straddle the closing date, and how any errors during the transition period get handled, are questions worth clarifying in writing rather than assuming.
Vendor and Customer Relationships
Some relationships are personal rather than contractual. A long-standing customer may have dealt with the seller directly for a decade. A key vendor discount may exist because of a personal relationship rather than a formal contract term. A TSA sometimes includes a commitment for the seller to personally introduce the buyer to these contacts and support the relationship during a defined window, rather than simply handing over a spreadsheet of names and numbers.
How Long Should a TSA Last
There is no fixed answer, and the questions to ask an advisor resource is a useful starting point for structuring this conversation with your own team. What matters is that the length matches the actual complexity of the handoff, not the buyer's opening request or the seller's desire to be done quickly.
A short TSA, thirty to sixty days, usually fits businesses with simple systems and a buyer that already has operational capacity. A longer TSA, six months to a year, tends to show up in deals involving specialized software, regulatory licensing, or customer relationships that took years to build. Reviewing comparable timelines with your advisor team, rather than negotiating in the abstract, tends to produce a more realistic number.
Pricing and Fee Structures Worth Reviewing
TSAs are compensated in different ways, and the structure affects both sides' incentives. Some are billed hourly for the seller's time. Some are a flat monthly fee for a defined bundle of services. Some are folded into the purchase price with no separate compensation at all, which can quietly disadvantage the seller if the transition period runs longer than expected.
Topics worth reviewing with your advisor before agreeing to a structure include whether the fee covers the seller's opportunity cost of not pursuing other work, what happens if the buyer requests services beyond the original scope, and whether there is a mechanism to extend or shorten the agreement if circumstances change.
Photo by Graziele Rosa on Pexels
Questions to Ask Before You Sign
A few topics are worth raising directly with your legal and financial advisors before finalizing a TSA:
- What specific services are included, and what is explicitly excluded.
- Who bears liability if the seller makes an error while performing transition services.
- What the termination process looks like if either side wants to end the arrangement early.
- Whether the seller's obligations under the TSA conflict with any non-compete or consulting arrangement negotiated separately.
- How disputes during the transition period get resolved without derailing the broader relationship between buyer and seller.
None of these have a single right answer. They are simply topics that benefit from being addressed on paper rather than assumed, since a TSA that leaves them vague tends to generate friction exactly when both sides are already adjusting to a new working relationship.
Coordinating Your Advisor Team
A TSA sits at the intersection of the purchase agreement, the seller's ongoing tax situation, and day-to-day operations, which means it rarely belongs to just one advisor. Your transaction attorney will want to review the liability and termination language. Your accountant will care about how transition-period income and expenses get reported. If the sale itself is still being structured, your advisor verification process is worth revisiting to confirm everyone involved has actually handled TSAs before, since it is a narrower specialty than general M&A advice.
For sellers who have not yet finalized their advisor team, using a resource like Capivise's advisor match service can help identify professionals with relevant business sale experience before the transition terms are locked in, rather than after.
Common Pitfalls to Avoid
A few patterns come up often enough to be worth naming directly. Sellers sometimes agree to open-ended language like "reasonable transition support" without defining what that means in hours or deliverables, which invites disagreement later. Buyers sometimes underestimate how long a systems migration actually takes, leading to a TSA that gets extended repeatedly under informal verbal agreements rather than a documented amendment.
Background on deal structuring generally, including how TSAs fit into the broader mergers and acquisitions process, is available through resources like the Wikipedia overview of mergers and acquisitions, which covers the standard phases a transaction moves through. Organizations such as SCORE and the U.S. Small Business Administration also publish general educational material on business transitions that can be useful background before advisor conversations, and the U.S. Chamber of Commerce maintains resources on small business ownership changes more broadly.
Photo by Pixabay on Pexels
Where This Fits Into Your Broader Sale Planning
A transition services agreement is a relatively small piece of paper compared to the purchase agreement itself, but it governs a period when a lot can go wrong quietly. Treating it as a real negotiation, with defined scope, a realistic timeline, and clear compensation, tends to produce a smoother handoff than treating it as boilerplate to sign quickly so the deal can close.
If you are still early in planning a sale and have not yet mapped out which post-closing obligations you are willing to take on, that is worth discussing with your advisor team before a term sheet is even on the table. The shape of the eventual TSA often traces back to decisions made much earlier in the process.
