TSA Exit Acceleration
Leave with your history secured, not stranded.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
TSA records retention handover secures the carved-out entity's historical records and retention obligations before Day One, along with agreed access to records the seller keeps. System separation moves the live data; the closed years, archives, and statutory records sit behind it and are easy to leave behind. This is core separation hygiene, which places it inside carve-out advisory. Get it wrong and the entity cannot answer for its own past.
A separation focuses on the live systems, because that is what the business runs on tomorrow. The records retention handover covers what sits behind those systems: the closed financial years, the archived contracts, the historical payroll and tax filings, the board minutes, the property and employment records, and everything else a company must keep but rarely touches. None of it is needed to process a transaction on Day One, which is exactly why it is so easy to leave with the seller.
The catch is that these records carry real obligations. Tax authorities can ask about prior years, regulators and courts can demand historical documents, and the entity has its own statutory retention duties that do not reset because it changed owner. An entity that migrated its live data perfectly but left its history in the seller's archive can find itself unable to support a prior year tax position or respond to a legal request, with the records it needs sitting in a building it no longer controls.
So the buyer treats the historical record as an asset to be secured, not an afterthought. The question is not only what data moves into the new systems, but what historical record the entity walks away with or can reliably reach. Answering that before Day One is far easier than reconstructing it years later when an obligation suddenly makes a closed year urgent.
The work starts with a map of the records the entity is obliged to retain and where they currently live. Tax records, statutory accounts, employment and payroll files, contracts, property documents, health and safety records, and regulated industry records each carry their own retention period, and those periods vary widely. The buyer builds a clear inventory of what categories exist, how long each must be kept, and which sit in the seller's systems, in central archives, or with third parties, because you cannot hand over what you have not located.
Format and condition matter alongside location. A record held in a live system the entity is leaving may need to be extracted into a durable form before access is lost, while a paper archive needs a physical handover or a clear custody arrangement. The buyer confirms that each category can actually be retrieved in a usable form for the full retention period, rather than discovering later that the record technically exists but is trapped in a system that has been switched off.
This inventory also feeds the wider separation. Knowing which historical records sit inside systems that are being migrated lets the buyer make sure the history is dealt with as part of that cutover, rather than lost in it. It connects directly to the master data management split, where the question of which data follows the entity and in what form is decided across the whole estate.
For each category, someone has to hold the record and the other side often needs to reach it. Some records transfer outright to the entity, some stay with the seller, which has its own obligations to keep them, and many are genuinely shared, where both parties may need the same historical document for their own tax or legal reasons. The buyer agrees this split explicitly and documents it, so there is a clear answer to who holds the original of every category rather than a vague assumption.
Access rights are the other half. Where the seller keeps a record the entity may later need, the entity needs a documented right to obtain it, and the same applies in reverse. These mutual access provisions cover how a request is made, how quickly it is answered, who bears the cost, and the confidentiality around sensitive records. A handshake understanding that the seller will help if asked is worth little years later when the people who made it have moved on and the request is now contentious.
Crucially, these rights have to outlast the TSA. The TSA covers a short operational window, but tax and legal retention obligations run for years beyond it, so the records access provisions are written to survive the TSA's end. Tying access only to the live TSA term is a common and expensive mistake, because it leaves the entity with a right that expires long before the obligation it was meant to support.
Historical records are full of personal data, so the handover carries data protection obligations. Employee files, payroll history, and customer records all contain information that must be transferred and held lawfully, with the right basis, the right security, and the right retention limits. The buyer makes sure the handover respects those rules rather than treating old records as inert archive, because a careless transfer of historical personal data is a breach regardless of how long ago the data was created.
Security travels with the records into the entity's own keeping. Once the historical record moves to the standalone entity, it has to be stored with controls that match its sensitivity, in a system or facility the entity actually manages, with access limited to those who need it. Records that arrive in an uncontrolled shared drive or an unlabelled box of files are both a security risk and practically unusable when a specific document is later needed under time pressure.
The physical and logical handover is then run as a defined event. The buyer confirms each category has actually moved or that access is in place, captures what was transferred, and closes off the seller's open obligations cleanly. Coordinating this handover alongside the rest of the separation, so the history lands in order rather than as a loose end, is the kind of sequenced execution the TSA Exit Acceleration service drives.
The handover is proven by a simple test: can the standalone entity, on its own, produce the records it would need if a tax authority, a regulator, or a court asked tomorrow. The buyer walks through the realistic demands, a query on a prior tax year, an employment claim reaching back several years, a contract dispute over an old agreement, and confirms the entity either holds the record or has a live, documented right to obtain it. If the answer is yes across the categories that carry the heaviest obligations, the handover is sound.
The gaps are fixed before the access closes, not after. Any category where the record cannot be located, cannot be retrieved in usable form, or has no access right behind it is a gap, and the time to close it is while the seller's systems are still live and the relationship is still cooperative. Once the TSA ends and the seller has decommissioned a system, recovering a record that was missed becomes slow, expensive, and sometimes impossible.
Records retention handover rewards the buyer that takes the boring history as seriously as the live systems. Mapping the obligations, agreeing who holds what, writing access rights that outlast the TSA, handling the data lawfully, and testing that the entity can actually answer for its past lets the standalone business stand fully on its own. Treating old records as the seller's problem is how an entity, perfectly operational on Day One, is caught defenceless when its history is finally called for.
It is the transfer to the carved-out entity of the historical records it needs to operate, prove its past, and meet its retention obligations, together with agreed access to records the seller keeps. The entity must leave with, or be able to reach, the documents that its tax, legal, and operational obligations depend on.
System separation moves the live data; records retention covers the historical record that sits outside or behind those systems, including closed years, archived documents, and statutory records. An entity can have working systems on Day One and still be unable to answer a tax authority about a prior year if the underlying records were left with the seller.
It depends on the record and the deal. Some records transfer with the entity, some stay with the seller who has its own retention obligations, and many are shared. What matters is that the split is agreed and documented, and that each side has the access rights it needs to records the other holds, for the full retention period.
As long as the underlying retention and limitation periods require, which for tax and certain legal records can run for many years. Records access cannot be tied only to the short TSA window, because obligations to produce historical records outlast the TSA, so the access rights are written to survive it.
Deciding which data follows the entity and in what form.
Read the article →Moving the contract record the entity has to keep and prove.
Read the article →Another estate cutover that leaves a historical trail to keep.
Read the article →The 90-day governance, IT, finance, HR and procurement separation plan we run on live carve-outs. Get the playbook plus the bi-weekly Day One Letter — short, signal-heavy, buyer-side.
No spam. Unsubscribe in one click. · Read the overview first →
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Seven buyer-side moves to exit a Transition Services Agreement on time and below budget. The mark-up, the extension-fee curve, exit sequencing, and the 11-month calendar.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →