Clients leave — budgets change, businesses close, a nephew “does IT now”. How you handle the exit decides whether they ever return and what they say about you in the market. Clean offboarding means their data handed over, your agents off their machines, and no silent remote access left behind. Ever.
Offboarding is the mirror of onboarding, with one extra duty: proof. The client should receive their final reports and inventory, your agent should be removed from every one of their computers, the distribution server at their site should be retired, and only then should the customer record disappear from your console. This page gives the order — and the reason data export comes before agent removal, not after.
Before touching a single agent, generate and save the client's final pack: last patch status, full inventory, software list and any open issues you know about. Send a copy to the client and archive your own copy with the contract end date. This pack is your closing statement — it proves the state you handed the network back in, and it is genuinely useful to whoever manages them next. Delete the customer first and this evidence deletes itself.
Uninstall the distribution server component from the client's machine once its agents are gone, and remove any client-specific items you placed there. Back in your console, delete or disable the client's configurations, automated patch tasks, software deployments and scheduled reports so nothing fires into a vacuum next month — a “monthly report” email arriving after the contract ends is a small embarrassment that says a lot.
Remove the customer from every technician's scope. Revoke or rotate any credentials connected with the engagement — shared mailbox passwords you were given, the local admin password you set, VPN accounts in your name. If your team created accounts inside the client's systems, hand them over in the closing pack or delete them, in writing either way. The rule is simple: after the end date, nobody at your company should be able to reach into that network, and the client should be able to verify it.
Only when reports are archived, agents are off and scopes are cleaned should the customer and its remote offices be deleted from the console. Keep your offline archive — contract, baseline, monthly reports, closing pack — for the period your agreement and local rules require. Clean exits are a sales asset: the market for IT services is small, owners talk, and “they handed everything over neatly when we left” is the review that wins your next client.
See Endpoint Central MSP running live — customers, offices and agents on one screen, step by step.
▶️ Watch Full VideoExport the final reports and inventory first, then uninstall agents, retire the distribution server and client-specific tasks, clean technician scopes and credentials, and delete the customer record last. Deleting the record first destroys the history you need for the handover.
Agree it in writing with the client: a guided manual uninstall, removal at their next office visit, or a fixed date by which the machines will be brought in. Keep the list of outstanding machines in the closing pack so both sides know exactly what remains.
Keep the business archive — contract, reports, baseline and closing pack — for the period your agreement requires, stored outside the console. Do not keep live access, agents or credentials. The archive protects both sides; live access after the end date protects nobody.