Can You Actually Leave? The Exit Clauses Nobody Reads Before Signing

Every contract negotiation focuses on getting in. Price, scope, service levels, start date. Almost nobody spends time on getting out, partly because it feels pessimistic at the moment you are agreeing to work together, and partly because the exit provisions are usually the dullest paragraphs in the document.

Then, two or three years later, you decide to move — and discover that serving notice was the easy part.

The clauses that govern leaving are where the real switching cost lives. Not the price difference between your current supplier and the new one. The cost of the transition itself, which is almost never estimated and almost always higher than anyone expects.

Notice is not the same as exit

Serving notice ends the contract. It does not, on its own, get you your data back, hand over the work, or oblige the supplier to help you move to a competitor.

Those are separate obligations, and if the contract does not create them, they do not exist. A supplier acting entirely within its rights can accept your notice, run the service to the final day, and then simply stop — with your data in their system and your new supplier waiting.

That is the gap. It has nothing to do with bad faith. Most suppliers behave reasonably at exit, and many will help far beyond what the contract requires. But "most" is doing a lot of work in that sentence, and the ones who do not cooperate tend to be exactly the ones you are leaving.

The five things that determine whether you can actually leave

1. Data return — in what format, and by when

The most common failure. A contract may promise your data on termination without specifying the format, and there is a wide gulf between a structured export you can import elsewhere and a 4,000-page PDF dump.

What to look for: the format is named, a deadline is stated, and it is free. If any of the three is missing, you have a negotiation on your hands at the worst possible moment.

Also check the deletion obligation. Data return and data deletion are separate promises — you want both, with confirmation in writing, and this is a UK GDPR expectation as well as a commercial one.

2. Transition assistance — and who pays for it

Better contracts include an obligation on the supplier to help you migrate: knowledge transfer, running the service during a handover, cooperating with the incoming supplier.

Two questions. Is it included, and is it charged? Transition assistance billed at the supplier's standard day rate, uncapped, is a blank cheque written at the moment you have the least leverage in the relationship. A capped number of days at an agreed rate, defined at signature, is worth more than a small discount on the annual fee.

3. Exit and termination fees

Distinct from the shortfall charges on a minimum spend commitment, though the two often appear together.

Watch for: early termination charges expressed as a percentage of the remaining term, "unamortised setup cost" recovery, equipment or licence buy-out clauses, and any fee triggered by termination for convenience. Each is defensible on its own; together they can make leaving cost more than staying another year, which is precisely their purpose.

4. Parallel running

The cost everyone forgets. In most migrations you run both systems for a period — you cannot switch a payroll, a warehouse system or an accounting integration overnight. For a month or three, you pay twice.

That cost is real, it is rarely budgeted, and it is the single most common reason a switching decision gets deferred. Knowing it in advance does not remove it, but it does stop the transition being abandoned halfway when the second invoice appears.

5. What happens between notice and exit

An underrated risk. Once notice is served, you are a departing customer for the remainder of the term — and service levels sometimes reflect that.

The protection is a clause stating that all obligations, including service levels, continue in full until the final day. It sounds obvious. It is frequently absent.

Add it up before you sign

Take a mid-sized software contract at £2,000 a month. The apparent annual cost is £24,000. Now consider what leaving actually costs.

Exit component	Typical range
Data extraction in a usable format	£0 – £3,000
Transition assistance (10 days, uncapped rate)	£8,000 – £15,000
Parallel running (2 months, both suppliers)	£4,000+
Internal time — your team, not theirs	Often the largest, never counted

Nothing here is unreasonable and nothing is hidden. But a switching cost somewhere north of £15,000 on a £24,000 contract changes the decision entirely — and it is the reason so many businesses stay with suppliers they have outgrown. Not inertia. Arithmetic.

The point of understanding this at signature is that every line above is negotiable then, and none of it is negotiable later.

What to ask for at signature

You will not get everything. Ask for these four in roughly this order.

A named data export format and a deadline. Cheap for the supplier, hugely valuable to you, and the easiest of the four to win.

Capped transition assistance. "Up to 10 days at £X per day" turns an unknown into a line item. Suppliers concede this more readily than you would expect, because at signature nobody is contemplating exit.

Service levels that survive notice. A one-sentence addition, rarely refused.

Clarity on exit fees. Not necessarily removal — sometimes an early termination charge is fair — but a single, stated number rather than three overlapping mechanisms.

The leverage for all of this exists only before signature. Once you want to leave, you are asking a supplier who is losing your business to make leaving easier, which is not a strong position. The same principle applies here as with index-linked price increases: the clause is cheap to fix at the start and expensive to fix at the end.

The renewal is your second-best moment

If your existing contracts have thin exit provisions — most do — the renewal is the only other point where you have real leverage. Not the week before it expires, when you have no alternative lined up and the supplier knows it, but early enough that switching is a credible option.

This is where knowing your notice dates matters for a reason that has nothing to do with avoiding auto-renewal. Three months before a notice deadline you can genuinely negotiate exit terms, because staying is a choice. Three days before, it is not a negotiation, it is a formality. Understanding the difference between an end date and a notice period is what makes the earlier conversation possible.

What to record for each contract

Alongside the dates you already track:

• Whether a data return obligation exists, and in what format
• Whether transition assistance is included, capped, or chargeable
• Any exit or early termination fee, and how it is calculated
• Whether service levels continue after notice is served
• Your own estimate of parallel running time, if you had to switch

That last one is not in the contract. It is your judgement, written down while you are calm, so that a future decision is made on a real number rather than a vague sense that switching would be a nightmare.

None of this means you should be planning to leave. Most supplier relationships should continue, and the ones that work are worth protecting. But a relationship you could leave is a fundamentally different relationship from one you cannot — and both parties know which kind they are in.

Timemy keeps exit terms alongside renewal and notice dates, so the question "can we actually leave?" has an answer before you need it. See how contract tracking works.

---

The short version: serving notice is not the same as being able to leave. Check five things before you sign — data return format, transition assistance and who pays, exit fees, parallel running, and whether service levels survive notice. All four of the negotiable ones cost nothing at signature and are close to impossible to win later.