The old provider always answered fast. That was the problem.
You asked whether the new case software would run on the server. “Yeah, that should be fine.” Three seconds, no questions, on to the next ticket. You asked whether the office move would interrupt email. “Shouldn’t be an issue.” You asked one night, after reading something that scared you, whether the backups were actually being tested. “Yep, all green.”
It was not fine. It was an issue. And the afternoon the server stalled with the new software half installed, you finally said out loud what part of you had known for a while: the answers had been arriving before the questions were understood.
Firms sit with that knowledge for years because of a story everyone has heard secondhand: the switch that took six months. Locked-out accounts, email down for days, two vendors pointing at each other. Staying can feel safer than becoming that story, so the fast wrong answers keep coming.
Look closely at any six-bad-months story and the missing thing is never talent on the incoming side. The firm left without its property.
What the six bad months are made of
An administrator password nobody at the firm holds. A domain renewal billed to a credit card that was cancelled two office managers ago. Backups that quietly stopped the day the old provider’s software came off. A copier that scans to a mailbox no one can open. A software vendor who will only speak to “the account holder,” who no longer answers you.
Each is a property problem: access, ownership, custody. A smarter incoming provider prevents none of them; nobody can hand you what the outgoing one holds. The fix is a folder. Call it the transfer file: six items, all already yours, most one email away. By the end of this page, the email is written.
The transfer file
For each item: what it is, why it’s yours, and the line that requests it. The lines assemble into one letter at the end. Sign with the incoming provider first, read your current agreement’s termination section (notice period, early-exit fee, any transition-assistance clause), then send the letter in writing.
1. The administrator credentials
Every system has a most-powerful account: Microsoft 365, the firewall, the wireless, the server itself, the backup console, the security tools, the phones. The test is physical: someone at your firm can sign in to each one today, from an account the firm owns, without calling anyone. “They have access” fails. “It’s all in their system” fails.
Ask for the inventory of administrator accounts and treat the passwords as its attachment. The list is the prize: every admin that exists, including ones created for technicians who left the provider years ago. During the transition, the incoming provider rotates all of them: announced, courteous, not optional.
The line: “Please provide a complete inventory of administrative accounts and credentials (Microsoft 365, firewall, wireless, server, backup, security tools, phones), delivered securely, including accounts your team created for internal use.”
2. The domain
The sleeper. Your domain, the yourfirm.com in every email address, lives in a registrar account at GoDaddy or Cloudflare or wherever it was bought in 2009. Whoever signs in there controls the records that route your email and point your website. Check three things: whose name is on the account, whose card pays the renewal, whose email recovers the password. It is common, and rarely sinister, for all three to be the old provider. Sometimes a technician who no longer works there.
Move this artifact first, because it fails ugliest. A lapsed renewal or a locked registrar account takes email down for every address at once, and no amount of urgency hurries a registrar. The account belongs in the firm’s name, on the firm’s card, recoverable by a mailbox more than one person can open.
The line: “Please confirm where our domains are registered and transfer the account, or the domains themselves, to firm ownership, with billing and recovery contacts updated to [firm email].”
3. The backups
Three custody questions. Where do the copies physically live? Inside whose account? What happens to the copies the provider holds after you part: retained how long, destroyed when, confirmed how? Get the answers in writing even if you like them.
Then the proof. You’ve already heard “all green.” While both providers are still engaged, ask for the one thing a dashboard can’t supply: a file restored this week, with a timestamp. One mechanism to respect before anything gets uninstalled: if backups run through the old provider’s tools, they can stop the day that agent comes off. The replacement backup goes in, runs, and is verified first.
The line: “Please provide the storage location and account details for our backups, your written retention and destruction policy after termination, and a scheduled test restore during the transition.”
4. The licenses
An afternoon of sorting, cheap at the price. Two piles. The provider’s licenses: monitoring tools, antivirus seats, usually whatever is priced per device on the invoice. Those end with the relationship and get replaced; nothing to collect. Then the ones that are yours but billed through them, and Microsoft 365 is the big one. The tenant holding your mailboxes and files belongs to the firm, attached to your domain. The provider’s part is a billing and access layer on top, and that layer can pass to a new partner with nothing migrating.
While you’re in there, open the Microsoft 365 admin center: Settings, then Partner relationships. That screen lists who holds standing access to your tenant; the roles are yours to remove.
The line: “Please provide a list of software licenses and subscriptions purchased on our behalf, noting which are held in the firm’s name and which in yours, with renewal dates.”
5. The documentation
You’re owed the facts of your own network: the device inventory, what connects to what, internet account numbers, the vendor list (copier, phones, practice software), the firewall configuration exported, the quirks list if one exists. Not owed: their internal scripts, their ticketing system, the tooling that makes their shop run.
Thin documentation is information too, not a fight worth having. Ask instead for an hour: their outgoing technician on a call with your incoming one. A walkthrough moves more truth than a binder, and technicians tend to be generous with each other even when the companies aren’t.
The line: “Please share the documentation you hold on our environment (inventory, network details, vendor accounts, configuration exports), or an hour of your technician’s time to walk it through with our incoming provider.”
6. The overlap month
The sixth item is time, and you buy it: one month with both providers paid and the old one reachable. Nobody enjoys writing two checks. Write them anyway; it is the cheapest month in this whole story, converting every surprise above from an outage into an agenda item.
The overlap has a shape. The old provider makes no changes and answers questions. The incoming one verifies the file live: signs in to every admin account, watches a backup complete and restores from it, confirms the registrar transfer landed. Only then does the old access end; the cutover date comes from the checklist, not the calendar.
Most professionals hand over cleanly, even the hurt ones. The rare one who stonewalls a transfer file is answering the only question you had left.
The letter, assembled
Every line above, in one email. Adjust the bracketed parts (dates follow your agreement’s notice terms) and copy yourself at a personal address so the thread survives any mailbox turbulence.
Subject: Transition notice and transfer request
Hi [name],
After [six] years, we’ve decided to move our IT support to another provider. This is our written notice under our agreement, with [date] as the target cutover. Thank you for the work across those years; we’d like an orderly handoff on both sides. Between now and then:
- A complete inventory of administrative accounts and credentials (Microsoft 365, firewall, wireless, server, backup, security tools, phones), delivered securely, including accounts your team created for internal use.
- Confirmation of where our domains are registered, and transfer of the account, or the domains themselves, to firm ownership, with billing and recovery contacts updated to [firm email].
- The storage location and account details for our backups, your written retention and destruction policy after termination, and a scheduled test restore during the transition.
- A list of software licenses and subscriptions purchased on our behalf, noting which are held in the firm’s name and which in yours, with renewal dates.
- The documentation you hold on our environment (inventory, network details, vendor accounts, configuration exports), or an hour of your technician’s time to walk it through with our incoming provider.
- A one-month overlap beginning [date], billed at your usual rate, during which your team remains reachable and makes no changes while [incoming provider] verifies each item above.
[Incoming provider] will coordinate the technical steps with your team. If anything above needs a different arrangement, tell us and we’ll work it out.
With thanks, [Name]
That’s the whole method, and it works with any incoming provider; a good one has run it from the other side and will pick up the checklist unprompted. Hand them this page if it helps.
A note on fit, since you read the exit instructions before moving: that’s the kind of firm we get along with, and we wrote down who we sign and why a while ago. If you’d like one of the replacement interviews to be with us, book a call. You already know the test: watch whether the questions arrive before the answers.