What is a transition services agreement, and what happens to data at TSA exit?
A transition services agreement (TSA) is a short-term contract under which the seller of a business or division keeps providing services such as IT, payroll, finance or hosting to the buyer after closing, until the buyer can run them itself. The TSA exit, when shared systems are cut over or retired, is the deadline for deciding who keeps which records.
Transition services agreement, defined
A transition services agreement (TSA) is a short-term contract, signed alongside the purchase agreement, under which the seller keeps providing services to a business it has sold until the buyer can provide them itself. TSAs are most common in carve-outs, where a division relies on the parent's IT, finance, HR and shared facilities and cannot run alone on the day the deal closes.
A reverse TSA runs the other way: the buyer provides services back to the seller, usually because the sold business housed functions the parent still needs. Both kinds are meant to end. The TSA exit, when each service is cut over to the buyer's own systems or switched off, is a hard deadline for deciding which records each side keeps.
What a TSA usually covers
| Service schedule | Typical services | Records question at exit |
|---|---|---|
| IT infrastructure and email | Network, identity, email hosting, file shares | Which mailboxes and shared drives move, and which are deleted? |
| ERP and finance | General ledger, payables, receivables, month-end close | Does transaction history migrate, or only opening balances? |
| HR and payroll | Payroll processing, benefits administration, HR systems | Which employee records transfer, and under what notices? |
| Customer operations | CRM, contact center platform, helpdesk | Does ticket and call history move with the customers? |
| Engineering and product | Code repositories, issue trackers, build systems | Are repositories split with commit history intact? |
| Reporting | Data warehouse access, dashboards | Does the buyer get extracts of the history it relied on? |
Key terms in a transition services agreement
- Service schedules describing each service, its scope and the standard it must meet, often by reference to how it was delivered before closing.
- Duration for each service, with notice rights to end services early and conditions for extensions.
- Pricing, commonly at cost or cost plus a margin, with rules for passing through third-party costs.
- Migration assistance, including data extraction in agreed formats before each cutover.
- Data ownership, access and return or deletion at exit, including copies left in the provider's backups.
- Third-party consents, because many software licenses do not let the seller run systems for a business it no longer owns.
- Confidentiality and security duties while the provider holds the buyer's data.
TSA vs similar agreements
| Agreement | Who provides what | How long it runs |
|---|---|---|
| Transition services agreement | Seller provides services to the buyer | Until the buyer can stand alone |
| Reverse TSA | Buyer provides services to the seller | Until the seller replaces them |
| Long-term commercial agreement | Ongoing supply or services between the parties | Years, on commercial terms |
| Purchase agreement | Transfers the shares or assets | Signed once; indemnities survive |
| Integration plan | Buyer's internal plan to combine the business | Months after closing |
The TSA exit usually overlaps with the buyer's post-merger integration, and TSA fees and stand-alone cost estimates are a common adjustment when buyers rebuild adjusted EBITDA for a carved-out business.
Why the TSA exit is a records deadline
At exit, shared systems are split, migrated or switched off, and the provider typically returns or deletes the buyer's data under the agreement. History left in a commingled ERP or a former parent's archive is hard to recover afterwards.
Ownership of the records is set by the deal documents, not by where the records sit. Under the Copyright Act, ownership of a copyright may be transferred in whole or in part, and any exclusive right may be transferred and owned separately (17 U.S.C. § 201), so a purchase agreement can allocate rights in documents and records between the parties. Customer data adds a further layer: FTC staff have warned that adopting more permissive data practices, such as using consumer data for AI training, and telling consumers only through a quiet, retroactive change to terms or a privacy policy may be unfair or deceptive (FTC, February 2024). This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.
Before the exit date, work through five items:
- Map each TSA service to the systems and record histories it touches.
- Confirm in the purchase agreement which party owns each category of historical records.
- Agree export formats and timing for full history, not just open items, ahead of each cutover.
- Ask whether either party could license any of those records for AI training, and whether customer contracts or privacy notices limit that.
- Keep a written record of what the provider deleted, and when.
Illustrative: a fictional industrial group sells its 140-person field-service division. The parent keeps hosting the division's email, ERP and service-ticket system under a twelve-month TSA. Three months before exit, the buyer's adviser asks for full-history exports rather than open work orders only, and confirms in the asset purchase agreement that nine years of service tickets and technician notes belong to the division. Those records can now be considered for a license; left behind, they would have been deleted with the parent's instance.
Why it matters for M&A advisors
Advisers draft or negotiate the TSA schedules, so they are best placed to add a data allocation schedule and a full-history export obligation. If the business that ends up holding the records is a US company with 50+ full-time employees at peak (contractors excluded), several years of history and clear rights, it may be worth an introduction; the who qualifies page has the detail. The page on referral opportunities for M&A advisors covers how to raise licensing without disrupting a process.
Next step
Add a records question to the TSA exit plan on your next carve-out. When a company looks like a fit, check it with the company fit checker and register as a partner to make the introduction.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
How long does a transition services agreement usually last?
Each service has its own term, set by how long the buyer needs to replace it. Simple services such as payroll may end quickly, while ERP and IT infrastructure often run longest because they depend on migrations. Most agreements let the buyer end individual services early on notice and set conditions, sometimes including a higher price, for extensions.
What is a reverse TSA?
A reverse TSA is a transition services agreement in which the buyer provides services back to the seller after closing. It arises when the business being sold performed functions, such as a shared service center or a data platform, that the seller's remaining operations still rely on. It follows the same structure as a standard TSA, with schedules, pricing and an exit date.
Who owns data created during the TSA period?
The deal documents decide. Many agreements say that data generated for the buyer's business during the TSA belongs to the buyer and must be returned or deleted at exit, but wording varies, and copies can linger in backups and logs. Check the TSA, the purchase agreement and any data processing terms, and get exports confirmed before each cutover.
What does TSA data access mean after closing?
It refers to the buyer's continued access to records still held in the seller's systems while the TSA runs, such as historical ledgers, tickets or customer files. Access usually ends at exit, so buyers should request full-history extracts in agreed formats well before the end date rather than rely on read-only access that will be switched off.
Can records from a carved-out business be licensed for AI training?
Possibly, if the records were preserved, the purchase agreement gives the carved-out company the rights, customer and privacy commitments allow it, and the company meets the size and history baseline. The company keeps ownership, and nothing is binding until it agrees price and terms and signs. Records left behind in a former parent's systems are usually out of reach.
Related pages
Free resources
- AI readiness assessment — Ten questions, five dimensions, a score out of 100.
- EBITDA calculator — Reported and adjusted EBITDA from net income.
- MOIC calculator — Multiple on invested capital from realized and unrealized value.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment