What happens to data when a transition services agreement ends

What happens to data at TSA exit?

At TSA exit, the seller switches off the services it has been providing, and with them access to the systems that hold the carved-out business's history. Whatever the new owner has not extracted, in a usable format, by the exit date is left to the seller's retention policy.

A transition services agreement (TSA) is a contract under which the seller keeps providing services such as IT, finance systems, payroll, hosting or HR platforms to a divested business for a defined period after closing, while the new owner builds its own. Sometimes a reverse TSA runs the other way. Either way, a TSA grants services, not ownership. Ownership of records is set by the purchase agreement: its definitions of the transferred business, books and records, excluded assets and any license-back.

That gap is where history gets lost. Separation plans tend to focus on open orders, active customers, open tickets and the finance data needed for statutory reporting. Closed tickets, lost deals, archived projects and old mailboxes often stay behind by default.

Why the TSA exit is a data decision, not only an IT cutover

Three features of a carve-out make data separation harder than it looks on the separation plan:

• Shared instances: the business ran inside the parent's ERP, CRM, ticketing system and email tenant, so its records are mixed with those of the parent and other divisions.
• Filtered extracts: the new owner usually receives an extract built for go-live, covering current records and a limited lookback, not the full history.
• Retained copies: purchase agreements commonly let the seller keep copies of transferred records for tax, legal and accounting purposes, subject to confidentiality obligations, so both sides may hold the same history.

Rights can also be split. Under US copyright law, ownership can be transferred in whole or in part, and any exclusive right can be transferred and owned separately, so a deal can give the buyer ownership of certain records while the seller keeps a license, or the reverse. Which split applies is a question for deal counsel, read against the actual agreement.

This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting on any reading of a purchase agreement.

Who owns the history? A rights map for carve-outs

Use this table at the TSA steering committee to decide, record set by record set, where history should end up and who could later authorize its use.

If the answer for a record set is unclear, park it. SourceX checks rights during qualification, and records whose ownership is disputed between buyer and seller cannot move forward until the parties settle it. The guide to excluded assets in an asset sale covers how sellers sometimes keep data when the business is sold.

TSA exit timeline: when to act on historical data

Work back from the exit date in the TSA schedule, service line by service line.

Extensions are often negotiated and priced separately, so treat the exit date as fixed unless the TSA says otherwise. Adding full-history extraction late in the TSA tends to cost more than writing it in at signing.

Who to talk to before the seller turns systems off

• Carve-out CEO: the likely sponsor for anything the company decides to do with its records, including licensing.
• Carve-out CFO and head of IT: owners of the data map and the archive.
• Separation management office lead: owns the exit plan for each TSA service line.
• Seller's TSA coordinator: confirms which extracts are possible and what the seller will retain.
• Deal counsel: reads the purchase agreement on ownership, retained copies and confidentiality.

What to preserve: a TSA exit checklist

• Full general ledger and subledger history, not just opening balances
• Closed tickets and cases with their resolution notes and timestamps
• Closed-won and closed-lost opportunities with activity history
• Project, engineering and change records, including archived projects
• Email, Teams or Slack history of transferred employees, as the agreements and policies allow
• Procedures and process documents specific to the carved-out business
• Field definitions and data dictionaries, so extracts stay readable after the source system is gone

Chat history is often the first casualty of a tenant split; the page on Slack to Teams migration history covers what tends to be dropped.

What to say

To the seller's TSA coordinator, about three months out:

To the carve-out CEO, at the steering committee:

Where licensing fits, once rights are settled

Some carved-out businesses hold years of connected operational records that AI labs and data buyers want for training and evaluating agents. Licensing becomes a question only after ownership is clear and the history sits safely in the company's own storage.

The company still has to clear the program baseline: US-based, 50+ full-time employees at peak (contractors excluded), a documented operating history of several years, rights to license the records and an authorized sponsor. See who qualifies for detail and what a data license agreement contains for how terms are set. The company keeps ownership, approves scope and price, and nothing is binding until it signs.

An operating partner who introduces the carve-out never touches the data. Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, and the reward becomes payable only after the buyer pays and SourceX receives its fee. Sponsor-side introductions are covered in more depth on the private equity operating partner page, and the introduction email builder drafts the note once the CEO agrees.

When to leave it alone

• Ownership of the history is unclear or disputed between buyer and seller.
• The records mainly belong to the business's own clients, as in many outsourcing carve-outs.
• The seller has already deleted the history, or nobody can extract it.
• Either party has already licensed the same records for AI training.

Next step

Put a historical data line in the next TSA steering committee pack. When a carve-out has its history archived and its rights settled, register as a partner and introduce the CEO, or share your referral link so the company can apply at sourcex.si/apply.