How to switch IT providers without losing a day
Most offices do not stay with an IT provider because the service is good. They stay because the provider holds the passwords, knows where everything is, and the thought of moving feels like changing the engine while driving. That fear is doing more work for bad providers than their service is. A handover is a known procedure with a known order, and an office that follows it switches without losing a day of work. This guide is that procedure from your side of the table: what to collect before you give notice, what a clean handover looks like, and how to tell whether the new provider is doing their half properly.
Why switching feels riskier than it is
The incumbent's real hold on you is rarely a contract. It is that they may be the only party who knows the admin passwords, which vendor bills for what, and how the pieces connect. That asymmetry is what the steps below remove, and here is the part worth hearing early: everything on the list is something the firm is entitled to, because it is yours. A provider administers your accounts. They should never own them.
What to collect before you give notice
Do this quietly, while the relationship is still routine. You are confirming that the firm holds its own keys, and every item is a normal request an owner can make on any Tuesday:
- Administrator access to Microsoft 365 or Google Workspace, registered to an account the firm owns.
- The domain registrar and DNS login, in the firm's name. This one is the most often lost and the most painful to recover.
- The firewall or router admin credentials.
- Logins and support contacts for each line-of-business application, and whose name the licenses are in.
- Backup access: where backups go, the account that controls them, and the encryption key. A backup whose key only the provider holds is their backup, not yours.
- Whatever documentation exists: an inventory, a network diagram, anything. If the answer is that no documentation exists, that is not a snag in your exit. It is the confirmation you were right to leave.
What a clean handover looks like
A proper switch runs as an overlap, not a cliff. The new provider comes under management while the old arrangement is still technically alive, and the order matters. First, everything gets documented as it actually is, because you cannot safely change what you have not mapped. Second, the new management and security tools go on and are verified working. Only then does the old provider come out: their remote-access and management agents removed from every machine, their accounts disabled, and every credential they ever held rotated, the same day the relationship ends. Old keys do not get left in old doors, however friendly the departure.
From your team's side, almost all of this is background noise. The visible moments are announced in advance: a new sign-in prompt, a new name to call when something breaks. If a step would interrupt billable work, it gets scheduled around the work, not the other way round.
How to tell the new provider is doing it right
Two habits separate a provider you will keep from a provider you will be leaving again in three years, and both show up in the first two weeks. The first: they document before they change anything. A provider who starts flipping settings on day two is improvising on your systems. The second: they verify instead of assuming. The previous provider's backups, patching, and access lists are treated as wrong until checked, because the switch is the one moment every old mistake is still someone else's fault. Ask a prospective provider how their first two weeks run. If the answer does not start with an inventory, keep looking.
This is also the window where the fastest security wins land: multi-factor sign-in enforced everywhere, former employees' accounts finally closed, and a restore actually tested rather than reported. A switch is not just a change of phone number. Done properly, it is the most security progress most offices make in any given year.
The one-page version
Confirm you own your accounts before you give notice. Insist on an overlap, never a cliff. Documentation before changes, verification before trust. Old agents off and every handed-over password rotated on the last day. And no change your team can see arrives without warning. An office that holds to those five sentences does not lose a day.
FAQ
Will anything go down during the switch?
There is no planned downtime. Swapping management agents happens in the background while everyone works, and anything a user would actually notice, like a new sign-in prompt, is announced before it happens. Nothing changes without notice.
What if our current provider will not cooperate?
It happens more often than it should, which is why you quietly confirm ownership of your own accounts before giving notice. If the domain, the Microsoft tenant, and the key vendor accounts are registered to the firm, an uncooperative provider can slow the handover but not stop it. Recovering accounts that were registered in a provider's name takes longer, so finding that out early matters most of all.
How long does a switch take?
For a small office, about two weeks from signed agreement to fully under management, and day-to-day support starts on day one of that window. The pace is set by documentation and verification, not by the software.
What does switching cost?
Plan pricing and the one-time onboarding cost are published on the pricing page, so there is no number you have to sit through a sales call to hear. Standalone help, including untangling access from a previous provider without joining a plan, is billed at $125 per hour, quoted up front for larger jobs.
Thinking about a switch and not sure what shape you are in? The free Security Check reads your firm from the outside, before any passwords change hands, and the law firm page shows how an engagement starts. Asking obligates you to nothing, and the report is yours to act on with any provider.
About the author
Mario Del Mazo is the owner of IT First Response, a managed IT and security practice in Fort Myers serving Lee County, Florida. His background is corporate IT for a healthcare organization operating under HIPAA and HITRUST standards. He publishes his prices, and every client environment is documented so nothing has to be explained twice. More about Mario.