How to hand a client over cleanly

Clients leave. A business closes, a project ends, or they simply choose a different provider — and how that is handled says more about your business than almost anything else you do, because it is often the last impression a client takes away, and the one most likely to be repeated to someone else. A clean handover costs you very little and protects a reputation that took considerably longer to build than it takes to lose.

Confirm the request properly

Get the cancellation or transfer request in writing, and confirm the timeline the client is working to. This matters for your own records as much as anything — a verbal request remembered differently by both sides later is an entirely avoidable source of a dispute.

1. Export everything, completely, promptly

   Provide a full, working copy of the site files and database, not a partial export that leaves the client's new provider to chase you for what is missing. Include email if it is part of the account — mailbox contents are often the thing forgotten in a rushed handover, and the thing a client notices missing first.

2. Sort out the domain, if it is yours to sort

   If you registered the domain on the client's behalf, you need to either transfer the registration to them or a registrar of their choice, or provide the EPP code that allows them to do so — see how to transfer a domain for the mechanics. If the client holds their own domain registration separately, this step is theirs to manage and does not involve you.

3. Settle the final invoice fairly

   Bill for exactly the period the client used, applying whatever cancellation terms were actually agreed at the start of the relationship — see what your hosting terms need to cover if this is not currently written down clearly. A dispute over a final invoice is a poor way to end an otherwise fine working relationship, and it is entirely avoidable if the terms were clear from the start.

4. Wait for confirmation before closing anything

   Do not suspend or remove the account the moment files are exported. Wait for the client, or their new provider, to confirm everything is live and working correctly on the new setup. Migrations occasionally reveal a missing piece only once the new environment is actually tested — and if that happens, you want the old account still available to fill the gap, not already gone.

5. Close the account, and keep a backup for a while

   Once confirmed, suspend and then remove the account per your normal process. Keep a final backup for a reasonable period afterwards rather than deleting everything the same day — a client occasionally realises something was missed only after the account is already gone, and being able to retrieve it costs you little and is worth a great deal of goodwill.

If they are moving to another host entirely

The client's new provider will typically be running a fairly standard migration on their end — see how to migrate a website to new hosting for what that process usually looks like from their side. Your job is simply to make sure they have everything they need, promptly and completely, so that process goes smoothly rather than becoming a back-and-forth over missing pieces.

Learn from why they left, if you can

Not every departure is worth investigating, but a pattern across several is. If clients are leaving for the same reason — price, a specific missing feature, a support experience that fell short — that is worth taking seriously rather than treating each departure as unrelated to the last. A short, genuine question about why they are leaving costs nothing to ask and occasionally tells you something worth acting on.

Handled well, offboarding a client costs you a small amount of time and, occasionally, a client you would rather have kept. Handled badly, it costs you a reference, a reputation, and sometimes a dispute that takes far longer to resolve than the handover itself ever would have. Treat every departing client as a future referral you have not received yet, rather than as a relationship that has already stopped mattering.