Transition Service Agreement
Definition
Transition Service Agreement
A transition service agreement is a separate, time-boxed contract under which one party keeps providing services to another after the main deal has changed hands. It exists to prevent a cliff edge, not to create a lasting relationship.
The classic case is a carve-out — a business is sold, the buyer has no payroll, helpdesk or accounts function of its own on day one, and the seller agrees to keep running them for twelve or eighteen months.
Outsourcing uses the same instrument at handover. An incumbent provider continues serving the client while a successor builds capability, or a client’s retained team keeps running a process it has just agreed to outsource.
Every transition service agreement has an expiry, and that date is the point of the document — extensions are normally priced punitively, because the whole design is to force both sides to finish the separation.
Key takeaways
- A transition service agreement is a standalone contract, not a clause in the main deal.
- Its purpose is temporary continuity while the receiving party builds its own capability.
- Scope, service levels and exit dates must be written service by service, not in the round.
- Extension pricing is the main lever that stops a temporary arrangement becoming permanent.
How it works
Each service is scheduled individually with its own description, duration, price and service level. Governance sits with a joint steering group, and a defined exit process transfers each service out as the receiving party becomes ready.
Public contracting has a close cousin in the Continuity of Services clause. It opens by recording that “The services under this contract are vital to the Government and must be continued without interruption”.
The obligation it creates is precisely the transition service agreement’s job. The contractor must “furnish phase-in, phase-out services for up to 90 days after this contract expires” and negotiate a handover plan with the successor in good faith.
Ninety days is generous for a helpdesk and hopeless for a finance system, which is why commercial agreements schedule each service separately rather than setting one global date.
| Service scheduled | Typical duration | Main exit risk |
|---|---|---|
| Payroll | 6 to 12 months | Statutory filing deadlines |
| IT helpdesk | 3 to 6 months | Knowledge held by named individuals |
| Finance and accounting | 12 to 18 months | Year-end close falling mid-transition |
| ERP hosting | 18 to 24 months | Data migration and licence transfer |
Pricing is usually cost plus a modest margin, because the provider is not competing for the work — buyers should still insist on a rate card, since undocumented cost-plus is where transition budgets quietly disappear.
UK government guidance treats handover as a pricing question too. The Sourcing Playbook advises structuring contracts to “minimise perverse or unintended incentives”, and an extension that is cheap for the incumbent is exactly such an incentive.
Examples
Transition service agreements appear wherever a business changes hands faster than its back office can follow. These four cases show the range, including one that outlived its purpose.
A manufacturer sells a division and keeps running its payroll for nine months. The buyer has no local entity registered yet, so the alternative is unpaid staff.
A bank outsources card operations and retains a transition service agreement for fraud analytics for a year. That capability was too specialised to move on the same timetable as the rest.
A retailer switches logistics providers and pays the incumbent for six months of parallel warehouse system access. The overlap costs real money and prevents a Christmas failure.
A private equity buyer signs an eighteen-month agreement for ERP hosting, then extends twice. Four years later the seller is still invoicing, which is what happens when extension pricing is too gentle.
Related terms
A transition service agreement is often confused with the delivery models it supports and with the costs it generates. The entries below draw those lines.
- Build operate transfer: a planned handover of a built operation, rather than a temporary service.
- Captive center: the client-owned operation a transition agreement often feeds into.
- Shared services centre: the internal function most commonly carved out under one.
- Joint venture outsourcing: a shared-ownership structure, not a temporary service arrangement.
- Vendor management outsourcing: the discipline that governs the agreement while it runs.
- Contract lifecycle outsourcing: the administration that tracks each scheduled exit date.
- Multi vendor outsourcing: the environment where handovers between providers happen most often.
FAQ
How is this different from transition costs?
A transition service agreement is a contract document. Transition costs are the money spent moving the work, which the agreement generates but does not define.
How long should a transition service agreement run?
Service by service, from three months for a helpdesk to two years for hosted systems. A single global end date almost always fits one service and fails the rest.
Who typically pays?
The receiving party pays the providing party, usually on cost plus a small margin. The margin is deliberately thin because there is no competitive tension.
What stops it becoming permanent?
Steeply escalating extension pricing, plus a named exit owner on both sides. Without a price penalty, extending is always easier than finishing.
Are service levels enforceable?
Yes, if they are written in. Many agreements inherit vague obligations from the main deal and end up unenforceable when performance slips.
Does it transfer employees?
Not by itself. Staff transfer is handled separately under the relevant employment rules, and the agreement only covers the service being delivered.
Compare providers experienced in carve-out handovers in the Outsource Accelerator directory.
Independent
