Can You Actually Leave? A Pre-Renewal Offboarding Audit for Small UK Teams

Ask a room of UK operations people how they chose their finance system and you will get a story. Ask them how they would leave it and you will get a shrug. That shrug is expensive, and it usually surfaces in the worst possible week — the one where the new tool is already bought and the old one is holding your invoices to ransom.

Offboarding is not a drama reserved for failed projects. Teams switch tools for perfectly boring reasons: a merger, a price rise, a feature that never arrived, a parent company standardising on something else. The question is not whether you will leave a platform. It is whether leaving will cost you a fortnight of exported CSV files, a support ticket you cannot escalate, and a lingering worry about where your customer records ended up.

Your data is only yours if you can carry it

Most contracts say you own your data. Fewer say what that looks like in practice. There is a world of difference between a data export and a useful data export — the first gives you a spreadsheet of names, the second gives you the thing you could actually rebuild on.

Before you sign anything, or before the next renewal lands on your desk, ask what comes out and in what format. Attachments, threaded comments, audit trails, custom field definitions, historical versions, permission structures, integrations and API keys all count. If any of that is classed as “platform metadata” and excluded, say so now rather than discovering it in month three of a migration.

Then do the thing almost nobody does: run a test export while you are still a happy customer. It takes an afternoon, it tells you more than any sales call, and it puts a dated copy of your own data somewhere you control. Do not rely on the export button being there after you have handed in your notice.

Watch the pricing too. Export assistance is a quiet favourite for “professional services, quoted at day rates”. Get the number in writing while you have leverage.

Admin rights: check who actually holds the keys

This one bites small teams hardest, because admin access tends to accumulate around whoever set the thing up in 2022 and has since moved on. A quick audit:

• Are the super admin accounts registered to your company domain, or to somebody's personal email?
• Who controls the recovery email address and phone number?
• Is single sign-on running through your identity provider, or theirs?
• Do you hold API keys and integration credentials that you can revoke without a support request?
• Are there at least two named admins, both currently employed?

If the only super admin is an account your former IT contractor set up with his personal address, you are one bounced email away from a support queue measured in weeks. Fix that before you need it.

Escrow, explained without the drama

Escrow gets discussed as though it is a magic word. It is a set of terms and a third party, and it is only as good as its release conditions.

For a hosted product, source code escrow is usually the wrong tool. What matters more is a continuity copy of your data plus a documented way to get it if the supplier stops trading. For self-hosted or heavily customised systems, code escrow genuinely helps — but only if it names you as a beneficiary, sits with an independent agent, gets verified on a schedule, and defines the trigger events precisely. “Insolvency” should not be the only trigger; “discontinuation of the product line” belongs in there too.

Escrow that has never been tested is a PDF and an annual fee. Ask when it was last verified.

Deletion, and the certificate worth having

Under UK GDPR you are the controller and your supplier is the processor, which means the duty to demonstrate that personal data has been dealt with properly sits with you. A line in a data processing agreement saying data is “deleted in line with our retention policy” is not a certificate.

What you want is a timetable (say, 30 days live, 90 days in backups), a defined scope, a named contact, and a signed attestation stating what was deleted, when, and from which systems. Get the template agreed at signature, not at exit. And be realistic about the other direction: HMRC expects records kept for around six years, so work out now how you will retain what you must after the platform is gone.

The one-page offboarding checklist

1. Diarise the auto-renewal date with a 90-day alarm. Contracts are won and lost in the notice window.
2. Confirm the notice period and how notice must be served — some still require a letter.
3. Run a full export test and store the output somewhere you control.
4. Get exit fees, export assistance fees and overage charges in writing.
5. Verify admin accounts, recovery contacts and SSO ownership.
6. Confirm a second admin exists and is documented in your leavers' process.
7. File the escrow or continuity-copy agreement with a named beneficiary.
8. Agree the deletion certificate template while everyone is still friendly.
9. Map what data lives where, including attachments and comments.
10. Note statutory retention needs and where that data will live afterwards.
11. Plan staff comms and a short read-only period so nobody loses access mid-project.
12. Reconcile the final invoice, credits and any unused prepaid term.

Put it in the contract, not the handover document

Handover docs get rewritten; contracts get renegotiated once and then sit quiet for three years. If the export format, the deletion window and the fee structure are not in the paperwork, they are subject to whoever is answering the support inbox on the day.

None of this is exotic procurement theory. A clean exit is simply a feature of a well-bought product, and it costs you an hour or two to check. The teams that ask early pay less, and they get to choose their timing. Everyone else gets a hostage situation with a renewal date attached.

This is general guidance, not legal advice — for anything involving personal data or a contract you cannot easily leave, take a view from someone qualified to give one.