- A TSA is a separate contract (or a schedule attached to the purchase agreement) that sets out specific services the seller — or sometimes the buyer, in a partial sale — will provide for…
- IT and systems access Passwords, software licences, point-of-sale systems, cloud accounts, domain registrations, and email — these rarely transfer cleanly on their own.
- A TSA and a seller consulting agreement often overlap in practice but serve different purposes.
A business rarely runs itself the moment the ink dries on a purchase agreement. The seller usually holds knowledge, relationships, logins, and processes that the buyer needs help absorbing — sometimes for a few weeks, sometimes longer. A transition services agreement (TSA) is the document that formalizes that handover: what help the seller will provide after closing, for how long, and on what terms.
Without a TSA, transition support tends to happen informally — a few phone calls, some goodwill, and vague expectations that often don't survive the first disagreement. This article explains what a TSA typically covers in an Ontario business sale, how it differs from the purchase agreement itself, and what to negotiate before closing.
What a Transition Services Agreement Is
A TSA is a separate contract (or a schedule attached to the purchase agreement) that sets out specific services the seller — or sometimes the buyer, in a partial sale — will provide for a defined period after closing. It exists because a purchase agreement is built around transferring ownership, not around describing day-to-day operational help, and blending the two into one document tends to create confusion about what's actually owed.
A TSA typically addresses:
- What services are covered — described specifically, not just "general assistance."
- How long support lasts — a fixed term, sometimes with an option to extend.
- What it costs, if anything — whether support is included in the deal or billed separately.
- How disputes are handled — what happens if the buyer feels support isn't being delivered adequately.
- How it ends — notice requirements and what happens to any work in progress at termination.
Common Categories of Transition Support
IT and systems access
Passwords, software licences, point-of-sale systems, cloud accounts, domain registrations, and email — these rarely transfer cleanly on their own. A TSA can specify how long the seller will keep systems running, help migrate data, or maintain access during a cutover period.
Accounting and bookkeeping continuity
The seller (or their bookkeeper) often understands historical coding, vendor relationships, and payroll quirks that a new owner needs explained before taking it over independently. A TSA can define a period of ongoing bookkeeping support or simple availability to answer questions.
Customer and supplier introductions
Personal relationships with key customers, suppliers, and referral sources are frequently part of what the buyer paid for as goodwill. A TSA can commit the seller to a defined program of introductions — calls, joint visits, or written introductions — rather than leaving it to informal effort.
Employee and operational knowledge transfer
Where the seller has been the person who "just knows how things work," a TSA can require documented handover of processes, vendor contacts, and institutional knowledge, sometimes paired with a period of the seller being available to answer staff questions.
Shared services in a partial sale
If the seller is retaining part of a business (for example, selling one division and keeping another), a TSA often needs to cover shared back-office functions — payroll, IT infrastructure, or a shared premises — that both sides continue to depend on for a period.
How a TSA Differs From a Consulting Agreement
A TSA and a seller consulting agreement often overlap in practice but serve different purposes. A TSA is generally operational — specific, itemized services with defined scope, closer to a service-level agreement. A consulting agreement is more often about retaining the departing owner's broader judgment, strategic input, or personal relationships on an ongoing advisory basis. Some deals use one, some use both, and the choice depends on what the buyer actually needs the seller to keep doing.
Structuring the Agreement: Key Terms to Negotiate
| Term | Buyer's typical concern | Seller's typical concern |
|---|---|---|
| Scope of services | Wants specific, enforceable commitments | Wants to avoid open-ended "as needed" obligations |
| Duration | Wants enough time to become self-sufficient | Wants a clear end date, not indefinite availability |
| Compensation | Wants support included where reasonable | Wants to be paid for meaningful ongoing work |
| Standard of service | Wants defined service levels | Wants to avoid guaranteeing specific outcomes |
| Termination | Wants the right to end for non-performance | Wants protection from being cut off unfairly |
| Interaction with non-compete | Wants transition work to not blur into future competition | Wants clarity that transition help doesn't extend restrictive covenants |
Why a TSA Should Be a Written, Separate Document
A handshake understanding that "the seller will help out for a bit" tends to break down exactly when it matters most — when the buyer feels support is inadequate, or the seller feels the ask has grown beyond what was agreed. Putting the terms in writing, ideally as a schedule or standalone agreement signed at closing alongside the purchase agreement, gives both sides something concrete to point to if expectations diverge.
Frequently asked questions
Is a transition services agreement required by law?
No. It's a commercial tool the parties choose to use, not a legal requirement. Many smaller Ontario business sales close with informal transition help and nothing in writing — a TSA simply reduces the risk of disputes over what was actually promised.
Can a TSA be part of the main purchase agreement instead of a separate document?
Yes, some deals fold transition terms into a schedule of the purchase agreement rather than drafting a standalone TSA. Either approach can work; what matters is that the obligations are specific and clearly agreed, not the label on the document.
What happens if the seller stops providing agreed transition support?
That depends on how the TSA is drafted — whether it includes remedies like a right to withhold a holdback payment, terminate for breach, or claim damages. This is exactly why the agreement needs clear enforcement language, not just a description of services.
Does transition support affect a seller's non-compete obligations?
It can create ambiguity if the two documents aren't drafted together carefully — for example, whether ongoing customer introductions during a transition period could be read as inconsistent with a non-solicitation clause. Coordinating the TSA and the non-compete/non-solicitation language is worth specific legal attention.
This is a business purchase or sale question
Start a file online — flat, published fees, reviewed by a licensed Ontario lawyer before a dollar is owed.