Glossary · Carve-outs
Transitional services agreement (TSA)
A contract under which the seller keeps running services the carved-out business cannot yet provide for itself. The workstream that most often overruns, because the seller's incentive to exit is weaker than the buyer's.
- Carve-outs
- Category
- 16 November 2026
- Updated
In one sentence
A contract under which the seller keeps running services the carved-out business cannot yet provide for itself. The workstream that most often overruns, because the seller's incentive to exit is weaker than the buyer's.
What it is
When a business is separated from a group, it rarely leaves with everything it needs. Its payroll may run on the parent’s system, its orders through the parent’s ERP, its email on the parent’s domain, its insurance under a group policy.
A TSA bridges that gap: the seller keeps providing those services for a period while the buyer stands up its own.
What it has to cover, service by service
Not one agreement with one end date. A schedule, with each line separately specified:
- The service, described precisely enough to be enforceable. “IT support” is not a service definition.
- The service level: response times, availability, who to call.
- The duration, and whether the buyer can extend, for how long, at what price.
- The price, usually cost plus a margin, stated per service.
- Exit criteria: what has to be true for the service to end, and who decides.
- Dependencies. Some services cannot end before others; separating finance before IT rarely works.
- Liability, which sellers usually cap tightly and buyers should scrutinise.
Kenvue is the public example. Under the TSAs Johnson & Johnson and Kenvue each provide services to the other. Most of those services ended 24 months after Kenvue’s IPO; the separate transition manufacturing agreements had initial terms of three months to five years.1
What goes wrong
- Scoped too late. TSA negotiation starts in the final weeks, when neither side has time to specify it properly, and the result is a document nobody can enforce.
- Underestimated duration. IT separation routinely takes twice the estimate. Build in extension rights rather than relying on goodwill.
- No named owner on either side. A TSA without a day-to-day manager on each side becomes an escalation queue.
- Priced at the wrong level. Services priced below cost give the seller an incentive to withdraw them; priced far above, they become a tax on the buyer’s whole integration plan.
- Standalone cost ignored. The point of a TSA is to buy time to build a standalone function, and that function costs more than the group allocation did. That gap is dis-synergy and belongs in the price, not in the surprise column.
See why separation is really two transactions in a carve-out is two transactions wearing one signature page.
Sources
-
Johnson & Johnson, Annual Report on Form 10-K for the fiscal year ended 28 December 2025, filed with the SEC. ↩
Frequently asked questions
What is a transitional services agreement?
An agreement in which the seller continues to supply the divested business with services it previously received from the group, IT systems, payroll, finance, HR, facilities, procurement, for a defined period after completion, at an agreed price, while the buyer builds or buys replacements.
How long does a TSA last?
Commonly six to twenty-four months, varying by service. IT separation is usually the longest and the most likely to overrun. Each service should have its own duration and its own exit trigger rather than sharing one end date.
Who pays for transitional services?
The buyer, normally at cost plus a margin. Pricing should be agreed per service, in writing, before signing, with a stated mechanism for extensions, because extensions requested late are priced by a counterparty that knows you have no alternative.