A transition services agreement, or TSA, is a temporary contract under which a seller continues to provide software and other services to a divested business after close.
What is a transition services agreement? It is a short term contract, usually called a TSA, under which the seller keeps running certain software, systems and services for a carved out or divested business after the deal closes. The carved out unit rarely has its own licenses and infrastructure on day one, so the TSA buys time to stand up a standalone estate. It is a bridge, not a destination, and the licensing risk inside it is one of the most underestimated parts of a carve out.
When a business is carved out of a larger parent, it often relies on shared software and systems that stay with the parent. On day one the carved out unit cannot simply keep using those licenses, because the entitlement belongs to the parent and many agreements restrict use to the parent organisation. A transition services agreement lets the seller continue providing those services for a defined period, giving the buyer time to procure its own licenses, migrate data, and build a standalone estate without an immediate operational gap.
The hidden risk is that the seller right to provide software under a TSA is not unlimited. Many publisher agreements do not permit the parent to extend its licenses to a business it no longer owns, even temporarily. If the TSA assumes a continuation that the underlying license does not allow, both parties can be exposed to a compliance claim. A TSA that runs longer than planned compounds the risk, because the temporary arrangement quietly becomes the operating model while the clock on the underlying entitlement keeps running.
The goal is to exit the TSA on time with a fully licensed standalone estate. That means treating the TSA period as a project with a hard end date, mapping which services depend on which underlying licenses, and confirming that the seller is permitted to provide each one. Where a license cannot be extended, the buyer needs its own agreement in place before the TSA covers it. Sequencing this against the TSA end date is what prevents both an overrun and a stranded compliance gap.
| Item | Question to answer | Risk if missed |
|---|---|---|
| Service inventory | Which services does the TSA cover | Gaps surface at exit |
| Underlying licenses | Is the seller permitted to provide each | Compliance claim against both |
| End date | When does each service stop | TSA overrun and extra fees |
| Standalone estate | What must the buyer license itself | Stranded gap at TSA end |
Related reading: see the M&A software glossary hub, plus carve out and divestiture.
Map and quantify the licensing exposure in your target or portfolio before it becomes a post close audit. Independent, buyer side, paid only by the acquirer.
Talk to a software M&A advisor