Five signs it's time to switch
You already suspect it. Here's how to know.
- Tickets sit for days. You follow up more than they do. "We're looking into it" has become a status, not an update.
- You're on your third account manager. Every new one asks you to explain your own environment. The institutional knowledge you paid for walked out their door, not yours.
- Every fix is a project quote. The monthly fee covers keeping the lights on. Anything that would actually improve things costs extra β so nothing improves.
- Your employees stopped reporting problems. They work around them instead. That's not patience. That's your team quietly absorbing the cost of bad IT.
- You can't name one thing that got better this year. No roadmap, no security review, no recommendation you didn't ask for. You're paying for maintenance and calling it a partnership.
Two or more of these and you're not being picky. You're being billed for a service you're not getting.
Read your contract before you do anything else
Before you talk to anyone β including us β pull your agreement and find four things. This is educational, not legal advice; your contract governs the specifics, and in almost all cases these four items decide your timing and your leverage.
- The termination clause. What ends the agreement, and what does ending it early cost? Some contracts run month-to-month after an initial term. Some don't.
- The auto-renewal window. Many agreements renew automatically unless you give notice inside a specific window β sometimes 60 or 90 days before the renewal date. Miss it and you may be locked in for another year. Find that date today.
- The notice period. How much written notice do you owe, and to whom? This sets your earliest realistic exit date.
- Equipment and license ownership. Who owns the firewall? Who holds the Microsoft licenses? If the provider owns hardware or licenses, leaving means replacing them β better to know now than during cutover.
None of this stops a switch. It just sets the calendar.
The four phases of a switch
A well-run switch is boring. That's the point. Here's the sequence.
Phase 1: The switch-planning call
Twenty minutes. You describe your environment, your contract situation, and what broke your patience. We tell you what the transition would look like in your specific case β and whether your renewal window means moving now or waiting. No pitch deck. Book it here.
Phase 2: Access and documentation audit
Before anyone gives notice, you inventory what you control versus what your current provider controls: admin credentials, your Microsoft 365 tenant, your domain registrar, firewall access, backup systems, license lists. Gaps get found now, while the incumbent is still cooperative β not during cutover, when they may not be.
Phase 3: Parallel onboarding
The new provider builds alongside the old one. Monitoring, documentation, and security baselines go in while your current provider still holds the keys. Nothing gets shut off in this phase β the old setup stays live until its replacement is running next to it. Built and checked, not switched and hoped.
Phase 4: Cutover and incumbent offboarding
Access transfers to the new provider, the incumbent's access gets revoked, and you collect everything on the offboarding checklist β credentials, data, documentation, equipment. Our Switch Kit includes a 30/60/90 transition plan template; the name is a template structure, not a promise. Actual timelines depend on your environment, your contract, and how cooperative the incumbent is.
What to demand back when you leave
Everything on this list is, in almost all cases, yours. The full version is in the free MSP Switch Kit β here's the short form.
- Global admin credentials for every system they touched β Microsoft 365, servers, firewall, wireless, backup platform.
- Domain registrar and DNS access. Your domain is your business. It doesn't belong in a provider's personal account.
- Microsoft 365 / Azure tenant ownership transferred to you or your new provider.
- A license inventory β what you're paying for, who owns each license, and what transfers.
- Network documentation β diagrams, IP schemes, configurations, vendor contacts.
- Backup copies and access to any backup system they managed.
- A hardware ownership list β what's yours, what's theirs, what's leased.
If a provider hesitates on any of these, that hesitation is information.
The three fears that keep businesses stuck
Most businesses don't stay with a bad provider because they like them. They stay because of three fears. Each one has a process answer.
"They'll hold our passwords hostage."
In almost all cases, your Microsoft tenant, your domain, and your data legally belong to you β the provider just administers them. Your agreement governs the specifics, which is why the access audit happens in phase two, before notice goes out. And if an incumbent stalls anyway, ownership verification directly through the vendor β Microsoft, your domain registrar β can usually restore control without their cooperation. Hostage-taking works best on people who haven't mapped what they own. You'll have the map.
"We'll have downtime."
This fear assumes a switch means turning things off and hoping. A parallel onboarding means the opposite: the new environment gets built and tested while the old one keeps running, and nothing gets retired until its replacement is working next to it. Staged, checked, boring β by design.
"The breakup conversation will be awkward."
You're imagining a confrontation. What actually happens: you send one short written notice β there's a template in the Switch Kit β and your new provider handles most of the technical handoff directly with the incumbent. Provider transitions are routine in this industry. They've been on both sides of one. It's a business decision, not a breakup.