How to end a client relationship without losing the record

A client tells you they are moving marketing in house, or the budget got cut, or they go quiet for three weeks and then send a polite note. Either way it is ending, and you have maybe two weeks of overlap left. What you do in those two weeks decides whether the next year is quiet or whether you get an email in November asking for a source file nobody can find and a copy of an approval nobody can prove happened.

Start offboarding the day you know it is ending, not the day the contract expires

The last two weeks of a client relationship are the only time you will ever have both the access and the attention to close it properly. After the final invoice clears, their marketing person stops answering, your login gets revoked in a password rotation, and the shared Dropbox link expires. Treat the notice date as the start of a short project with its own deliverables, not as an administrative afterthought.

Set a handover date and put it in writing. Everything below happens before that date. After that date, your access ends and any further work is quoted separately.

The client offboarding checklist

Work through this in order. Set aside a few hours for a normal small business client, longer if you have been running their ads and email.

1. Confirm the end date and the scope of the wind down in writing. One email, one paragraph, ask them to reply "confirmed." This is the document that prevents the argument later.
2. List every deliverable that is finished, in progress, or promised. Say plainly which ones you will complete, which you will not, and whether anything is being credited or refunded.
3. Chase the loose signatures. If the wind down agreement or the final change order is still waiting on a signature, it is not signed. Either get it signed or void it and note that it was never executed. An unfinished agreement in a folder is worse than no agreement.
4. Gather source files, not just outputs. Layered logo files, editable design files, raw video, the spreadsheet the report was built from. The client will remember signing off on the finished work. What they will not have is the file it was built from, and once the handover is done your archive may be the only copy left.
5. Inventory every account and who owns it. Domain registrar, DNS, hosting, CMS admin, analytics, search console, tag manager, business profile, ad accounts, email platform, plugin and theme licenses, form and CRM integrations.
6. Transfer ownership rather than sharing passwords. Most platforms have a real ownership transfer. Use it. Never send credentials in plain email or a chat message.
7. Say what does not transfer. Font licenses, stock photography, and premium plugin licenses are frequently tied to your account and cannot legally move. Tell them now, in writing, with the renewal cost, so they are not surprised when a plugin goes dark after the next renewal date passes.
8. Name the billing cutover. List every recurring charge you have been paying on their behalf, the amount, the renewal date, and the date you stop paying it.
9. Export the full record of the engagement. Details below.
10. Remove your access and confirm you did. Take yourself out of their accounts and send a short note listing what you removed and when.
11. Get written permission for portfolio use. One line in the final email. This is the cheapest thing on the list and the one most people skip.

What you hand over, what you keep, and how to decide

Hand over anything the client paid you to produce that they need in order to keep operating. Keep a copy of anything that documents what happened between you. Do not hand over your internal method.

That gives you three buckets, and almost everything falls cleanly into one of them:

• Theirs, hand it over: final files and source files, content they wrote or paid for, account ownership, documentation of how their site or funnel is built, anything with their name on it.
• Yours, keep it and do not send it: proposal templates, internal cost sheets, your project checklists, your code libraries and starter themes, notes about staffing and margin, anything you would not want read aloud.
• Shared history, both of you get a copy: the message record, approvals, signed documents, invoices, scope changes, and the dates attached to all of it.

Your contract may put the line somewhere else, and retention periods for financial records are set by law where you operate, not by preference. Check with your accountant and, for anything unusual, a lawyer. The buckets above are a working default, not legal advice.

Why you export the whole record before the account closes

Export because the reasons you will need the record are the reasons you cannot predict. A client who left on good terms in April disputes a charge in September. A new agency asks what was actually approved on the homepage copy and their contact has since left the company. Someone claims you never flagged that the hosting renewal was theirs to pay. A card gets charged back and you have a short window, often measured in days, to produce evidence. Look up the deadline in your own processor's terms rather than trusting a number you read in an article, because it varies by card network and by processor.

In every one of those situations, the thing that ends the conversation quickly is a dated record showing what was said, what was approved, and by whom. Without it you are arguing from memory against someone else's memory, and you will lose that even when you are right.

There is a second reason that has nothing to do with disputes. Former clients come back, and they refer people, sometimes long after you assumed the relationship was closed. When they do, the person who can say "here is what we built, here is what we recommended and you decided against, here is where the site stood when we handed it over" starts the new conversation two meetings ahead.

What a good export actually contains

• Readable transcripts of the conversation with timestamps and named senders, in a plain format like Markdown or PDF that will still open in five years.
• A structured copy such as JSON, so the record can be searched or reloaded later without a person retyping it.
• The files with a manifest that lists every filename, size, upload date, and who uploaded it. Files without a manifest become a folder of mystery faster than you expect.
• Signed documents with their certificates showing who signed, when, and from what IP or email. A signed PDF with no audit trail is much weaker evidence than one with it.
• Approvals with attribution. "Approved" is not useful. "Approved by the client contact, on a named date, at a recorded time" is.
• An index and an honest note about what is missing. If the export does not include, say, direct messages or a phone call, write that down inside the folder.

If your work lives across email, a chat tool, a drive, and a signing app, plan a day for this and accept that some of it will be incomplete, which is the real argument for getting client communication into one place long before a relationship ends. Tools built for client work should do the export in one action. Client Atrium, which is ours, does a one-click export covering transcripts, JSON, files with a manifest, and signed PDFs with certificates. It does not include direct messages today, which is exactly the kind of gap worth checking before you trust any tool to be your record.

The handover email that closes the loop

Subject: Handover for [Client] and final items

Hi [Name], as agreed, [date] is our last day on the account. Everything below is done or attached.

Completed and delivered: [list]. Not proceeding: [list], with [credit or refund, or none].

Account ownership transferred to you: [list, with the email each was transferred to]. Access I removed on [date]: [list].

Does not transfer and will need to be renewed in your own name: [font, stock, plugin licenses] at roughly [cost] on [date].

Recurring charges I stop paying after [date]: [list with amounts and renewal dates].

Attached is a full archive of our work together: every message, file, approval, and signed document. You have your own copy of the record and so do I.

Two asks. Please reply "confirmed" so we both have this on file, and let me know if I can use the work in my portfolio. If anything breaks, I am here at [rate] for emergency work, and if you decide to bring the work back out, you would not be starting over.

How to leave the door open without hovering

The most useful thing you can do after handover is one short check in at 90 days, and nothing else. Do not send a newsletter to someone who just left. Do not ping monthly. One message at 90 days that asks a genuine question, "how is the site holding up since you took it over," tends to get a real answer, because by then the client has often discovered which piece of the work was harder than it looked.

Also ask one exit question while the ending is fresh: what would have made you keep us. Ask it once, do not argue with the answer, and write it down. The dentist client who never once logged in and stayed on email is telling you something about your onboarding, not about dentists.

If you take one thing from this

Make the folder. Today, for a client who already left, create a single directory named for them with the year, drop in whatever you can still reach, and write a plain text file at the top listing what is in it, what is missing, and the date. Then set a calendar reminder for whenever your retention period ends so you are not carrying client data forever with no decision behind it.

That folder costs you one sitting and no money. The first time someone asks you what was approved on a project that closed two years ago, it pays for every minute of it.