At the end of the day, your offboarding “proof” is ticket notes and screenshots.
That's a real MSP owner describing how they'd defend a client exit a year later. If it's yours too: this is a free five-file pack — a Phase 0–7 client offboarding checklist, a credential handover register that becomes your proof-of-completion record, and a one-page signed handover certificate. Markdown, fully editable, deployed in your shop in under an hour.
You have an onboarding process. This is the other half.
Every small MSP eventually says some version of these:
“We have a well defined process to onboard new units into a client. The step we keep missing is offboarding.”— r/msp
“We still have their Ubiquiti Wi-Fi showing up in our console. No one has removed it.”— r/msp
“I'm sure there's a better way than a password protected Excel document.”— r/msp
Client exits are rare enough that nobody builds the process, and consequential enough that improvising one during a hostile termination is how you end up with orphaned agents in your RMM, your admin accounts still live in an ex-client's tenant, and nothing to show a lawyer or a cyber-insurance auditor except a ticket thread.
What's in the pack
Five files. Three you work in, two that keep you honest.
| File | What it does |
|---|---|
| Offboarding checklistoffboarding-checklist.md | The end-to-end exit process, Phases 0–7, written so a tech with ~6 months' experience can execute it under a named Offboarding Lead. Includes a hostile-exit appendix and a credential transmission standard (the anti-spreadsheet part). |
| Credential handover registercredential-handover-register.md | The fill-in ledger: every credential, its disposition, receipts, signatures. This is the proof-of-completion artifact — the thing you show the incoming MSP, a lawyer, or an insurance auditor a year later. |
| Handover certificatehandover-certificate.md | One-page signed closure both parties keep. Practice template, not legal advice. |
| README-FIRSTREADME-FIRST.md | The under-an-hour deployment walkthrough, the full find-and-replace token reference, and honest scope notes on what the pack does and doesn't cover. |
| MANIFESTMANIFEST.md | Contents, version, changelog — and the map from every artifact to the real, linked r/msp pain it answers. |
Everything is clean Markdown: paste it into Hudu, IT Glue, or Confluence as-is, or convert to Word with one pandoc command. Shop-specific values (your RMM, PSA, vault, retention window) are {{tokens}} you find-and-replace once. Vendor-specific steps were written against M365/Entra, NinjaOne, Datto RMM, ScreenConnect, SonicWall, and UniFi as of Aug 2026 — on a different stack, the step structure holds and you swap the menu paths.
It also reads from the other side: if you're the incoming MSP, the register is the checklist for what a clean handover from the incumbent should look like.
The first hour, specifically
- 0–10 minFind-and-replace your shop tokens; save as your master copy.
- 10–25 minSkim Phase 4, swap vendor paths where your stack differs.
- 25–40 minBuild the matching ticket template in your PSA.
- 40–55 minDry-run the credential sweep against one current client. Every gap it finds is a gap in your documentation today, exit or no exit.
- 55–60 minName your default Offboarding Lead. Done: the next termination notice starts at Phase 0.1 instead of a panic meeting.
Why it's free, and who's behind it
Two straight answers.
Why free: this pack is the quality bar for a paid line of MSP ops kits we're building under OpsBindery. Offboarding is the kit we give away because it's the process most shops are missing entirely — and because if this doesn't earn a place in your documentation platform, you shouldn't pay us for the next one. The free pack is the proof.
Who’s behind it: OpsBindery is a product studio from Exodus Core Solutions. The kits are built against hundreds of real, public MSP threads — the MANIFEST inside links every artifact to the specific pain it answers, so you can check our work — and everything that touches credential handling passes a technical audit and a separate review before release.
The flagship: MSP Client Onboarding Vault
Onboarding is execution, not discovery. Right now it starts with a credential dump in a text file and ends with a month of surprises coming out of the woodwork — the junk drawer for every inherited problem. The Vault is the filled-in onboarding system that flips it: intake and discovery forms that capture the environment before you touch it, network & asset documentation (M365/Entra, SonicWall, UniFi, Hyper-V, Veeam) that arrives already written, kickoff comms your client actually reads, and 30/60/90-day checklists with verification gates — so “onboarded” is a measure, not an opinion. Not a blank template shell: every document ships written, with a worked example, tokenized for one find-and-replace pass.
See a page from inside the kit
# Client Intake Form
> MSP Client Onboarding Vault · Section 1 — New-Client Intake Pack
**How to use this doc**
Fill this out in the first sales-to-delivery handoff meeting — it is the single
source of truth every later document pulls from. Anything you can't answer
becomes an agenda item for the kickoff meeting — mark it **UNKNOWN**, don't guess.
## 1. Engagement summary
| Field | Value |
|----------------------------------|-------|
| Client name | {{CLIENT_NAME}} |
| Agreement signed | {{CONTRACT_DATE}} |
| Go-live (support cutover) date | {{GO_LIVE_DATE}} |
| Master onboarding ticket | {{TICKET_ID}} in {{PSA_NAME}} |
| Prior IT provider | {{PRIOR_PROVIDER}} — cooperative / uncooperative / none |
| Prior-provider exit date | ______ (drives the offboarding-the-incumbent track) |
…
Every document reads like this: filled-in, tokenized, with the judgment calls already made.
One-time purchase, instant download. Everything is plain Markdown — it drops straight into IT Glue, Hudu, SharePoint, or a plain folder, no importer, no lock-in. Core is $69 — less than one month of an IT Glue subscription, and it comes filled in. If it saves one hour of one onboarding, it has paid for itself. The free offboarding pack is the quality bar; if it didn't earn a place in your stack, don't buy this.
What it deliberately doesn't cover
- Legal advice (the register and certificate are operational records — your MSA and attorney outrank this pack)
- Co-managed exits (needs a trimmed Phase 4)
- Employee-level offboarding (this is whole-client)
- Automation (every step is manual/console/PowerShell on purpose, so a junior can run it anywhere; script it once the manual run is boring)
Get the pack
Next client exit, run a process instead of a scramble — and finish holding a signed register instead of screenshots.