Home/Glossary/Transition Services Agreement
M&A Software Glossary

What is a transition services agreement?

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.

Why a transition services agreement exists

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 licensing risk inside a TSA

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.

How buyers should manage a TSA

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.

The TSA as a bridge to a standalone estateA process timeline: close, then tsa, then stand up, then exit.The TSA as a bridge to a standalone estateCloseCarve out completesTSASeller runs servicesStand upBuyer licenses and migratesExitTSA ends cleanly
What belongs in a TSA exit plan
ItemQuestion to answerRisk if missed
Service inventoryWhich services does the TSA coverGaps surface at exit
Underlying licensesIs the seller permitted to provide eachCompliance claim against both
End dateWhen does each service stopTSA overrun and extra fees
Standalone estateWhat must the buyer license itselfStranded gap at TSA end

Key takeaways

  • A transition services agreement is a temporary bridge while the buyer stands up its own software estate.
  • It is not a long term solution, and an overrun raises both cost and compliance risk.
  • The seller right to provide software under a TSA is often limited by the underlying licenses.
  • Exiting on time with a fully licensed estate is the only clean outcome.

Recommendations for buyers

  1. Treat the TSA as a project with a hard end date. Plan the exit from the day the carve out closes.
  2. Map services to underlying licenses. Confirm the seller is actually permitted to provide each service.
  3. License the standalone estate in parallel. Have the buyer own agreements ready before the TSA stops covering each service.
  4. Watch the clock. A TSA that overruns becomes the operating model and a quiet compliance exposure.

Related reading: see the M&A software glossary hub, plus carve out and divestiture.

Frequently asked questions

How long does a transition services agreement last?
It varies, but a TSA is usually scoped for months rather than years. The aim is to keep it as short as the buyer needs to stand up its own licensed estate, because every extra month adds cost and risk.
Can a seller provide any software under a TSA?
Not always. Many publisher agreements do not permit the parent to extend its licenses to a business it no longer owns. The TSA scope has to be checked against what the underlying licenses actually allow.
What happens when a TSA ends?
The buyer must be running its own fully licensed standalone estate. If any service was not migrated and licensed in time, the buyer faces an operational gap or a compliance exposure at the exit date.
Is a TSA a licensing risk in a carve out?
Yes, and an underestimated one. The risk is that the temporary arrangement relies on entitlements the seller is not permitted to extend, exposing both parties to a claim if it runs unchecked.

Request a confidential software M&A risk assessment.

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