Exit assistance is the clause you will need most.

Section 01

Why exit assistance decides the exit.

Every TSA ends. The buyer either stands up its own capability, migrates to a new provider, or absorbs the service into Newco. In every case the buyer needs the seller's cooperation to leave cleanly. The exit assistance clause defines that cooperation. Where the clause is strong, exit is a managed project. Where it is weak or absent, exit becomes a negotiation the buyer conducts from a position of weakness, often paying extension fees to buy the help the contract should have guaranteed.

The clause is routinely underweighted at signing because exit feels far away and the buyer is focused on Day One. That is exactly why sellers leave it thin. A seller that owes only vague cooperation at exit holds leverage the buyer will pay to overcome later. The buyer that negotiates specific exit obligations at signing converts a future negotiation into a present contractual right, which is far cheaper.

Exit assistance is also the clause that connects to the buyer's whole exit plan. The buyer cannot build a credible exit timeline if the seller's obligations are undefined. Data delivery dates, knowledge transfer sessions, and parallel running windows all depend on what the seller is required to provide. Without the clause, the exit plan is a hope. The link between the clause and the plan is set out in TSA exit timeline explained.

Section 02

The five exit obligations that matter.

The first obligation is data delivery. The seller must deliver the buyer's data in a usable format, on a defined schedule, with the documentation needed to load it into the buyer's environment. The clause should specify format, completeness, and the seller's duty to support reconciliation, because raw data without context is not usable. Data delivery is the single most common point of exit failure.

The second is knowledge transfer. The seller must make named personnel available to transfer the operational knowledge the buyer needs, through documented sessions, runbooks, and configuration records. The third is system access and configuration. The seller must provide the configuration, integration details, and access required for the buyer to replicate or replace the service. The fourth is parallel running, where the seller continues to deliver the service while the buyer tests its replacement, so the buyer is not forced into a single cutover with no fallback.

The fifth is transition support after the formal end date. Even a clean exit produces follow up questions and edge cases. The clause should require the seller to provide defined support for a tail period after the service ends, at agreed rates. Together these five obligations turn exit from a scramble into a project. How parallel running protects the cutover is covered in TSA exit parallel running strategy.

Section 03

Pricing the exit assistance.

The buyer should agree the price of exit assistance at signing, not at exit. A clause that says the seller will provide exit assistance at rates to be agreed hands the seller pricing power at the exact moment the buyer is most dependent. The seller knows the buyer must exit and prices the help accordingly. Agreeing rates, or a methodology for rates, at signing removes that leverage.

The cleaner approach is to include a defined volume of exit assistance in the base TSA price, with additional support priced on a cost-plus basis agreed before signing. That structure gives the buyer a known quantity of help at no extra charge and a known rate for anything beyond it. The buyer avoids the worst outcome, which is paying extension fees because the seller will not deliver exit help without a new negotiation.

The buyer should also separate exit assistance pricing from extension pricing. Sellers sometimes blur the two, so that the only way to get exit help is to extend the service. That couples two decisions that should be independent. The buyer wants the right to exit on schedule with full assistance, without being pushed into an extension to obtain it. How extension pricing works against the buyer is explained in TSA extension fees explained.

Section 04

Where sellers push back.

The first pushback is on specificity. The seller prefers a general duty to provide reasonable cooperation at exit, because vagueness preserves its leverage. The buyer should refuse and require named obligations with dates, formats, and personnel commitments. Reasonable cooperation means whatever the seller decides it means when the time comes, which is no protection at all.

The second pushback is on cost. The seller wants exit assistance to be a chargeable extra priced at exit. The buyer holds for a defined volume in the base price and agreed rates for the rest. The seller's argument that exit help is unpredictable is fair only at the margin. The core obligations, data delivery, knowledge transfer, and configuration handover, are predictable and should be priced in.

The third pushback is on the tail period. The seller resists any obligation that extends past the formal end date. The buyer should hold for a defined support tail, because the alternative is that every post exit question becomes a new commercial negotiation. A short, priced tail period covers the edge cases that always appear and prevents the seller from charging premium rates for routine follow up. The role of exit assistance in the broader knowledge transfer is set out in TSA exit knowledge transfer.

Section 05

Negotiating it before you need it.

Exit assistance is the clearest example of a clause that must be negotiated before signing because its entire value lies in the future, at the moment the buyer has least leverage. The buyer that pins down the seller's exit obligations at signing controls the exit. The buyer that leaves the clause thin pays for the help later, usually through extension fees or premium support rates the seller sets unilaterally.

The practical sequence is to define the five obligations, agree the pricing, separate exit help from extension, and align the clause with the termination rights and the exit timeline. These provisions form the buyer's exit architecture and must be read together. A strong termination right is worthless if the seller is not obliged to help the buyer actually leave.

The buyer that treats exit assistance as a signing priority rather than an exit problem changes the entire dynamic of the eventual exit. The seller arrives at exit already bound to deliver. The buyer runs a project instead of a negotiation. That is the difference a well drafted exit assistance clause makes, and it is available only to the buyer who negotiates it before the exit is in sight.

FAQ

Exit assistance questions buyers ask.

What does a TSA exit assistance clause cover?

It covers what the seller must do to help the buyer leave a service: data delivery in a usable format, knowledge transfer through named personnel, system access and configuration handover, parallel running, and a support tail after the formal end date. Together these make a clean exit possible.

Should exit assistance be priced at signing or at exit?

At signing. A clause that defers pricing to exit hands the seller leverage at the moment the buyer is most dependent. Include a defined volume of exit help in the base price and agree rates or a methodology for anything beyond it before signing.

Why is the exit assistance clause so often weak?

Because exit feels distant at signing and buyers focus on Day One, so the clause gets little attention. Sellers leave it vague on purpose, since a thin clause preserves leverage they can monetize later through extension fees or premium support rates.

How does exit assistance relate to termination rights?

They work together. A termination right lets the buyer leave a service, but exit assistance defines whether the buyer can actually do so cleanly. A strong termination right is worth little if the seller is not obliged to deliver the data, knowledge, and support the exit requires.

Related Reading

More on TSA negotiation.