Most businesses put up with a poor IT provider for a year longer than they should, and the reason is always the same: the switch feels dangerous. Your current provider holds every password, every licence and every undocumented quirk of your systems, and the fear is that leaving them means chaos, or worse, spite. It is the better-the-devil-you-know calculation, and IT providers know their customers are making it.
Here is the reassuring truth: a competently run switch takes one to two weeks, involves no downtime for your staff, and the awkward parts are handled provider-to-provider without you in the middle. The less reassuring truth: the handover goes exactly as well as your preparation, because a small number of items, sorted in the right order, decide everything. This is that list.
Before you serve notice: four things to check quietly
1. Read your contract’s exit terms. Find the notice period (30 to 90 days is typical), the renewal date, and any auto-renewal clause; missing a notice window by a week can cost a year. Look for offboarding fees and what the contract obliges them to hand over. Do this before anyone knows you are thinking of leaving.
2. Establish what you actually own. Licences, your domain name, your Microsoft 365 tenancy, admin accounts: registered to your business, or to the provider? This is the single biggest factor in how hard the switch will be. If things are in the provider’s name, your new provider will plan transfers as part of onboarding, but they need to know now, not mid-cutover.
3. Get a copy of your own documentation. You are entitled to know your own systems. Asking for an updated network and asset summary during normal service is unremarkable; asking for it the day after you serve notice looks like what it is.
4. Choose the new provider first. The overlap matters: the incoming provider audits and prepares while the notice period runs, so the baton passes hand to hand rather than being set down. Our guide on choosing an IT support company covers the selection; make sure exit terms (theirs, this time) are part of what you compare.
The handover, week by week
A typical SME handover, run properly:
Week 1, before notice or as it is served: audit and access. The incoming provider inventories your estate: devices, servers, cloud services, licences, backup state, and identifies what must transfer versus what they will rebuild. Admin credentials are transferred or freshly issued, with your business as the owner and both providers holding delegated access during the overlap.
Week 1 to 2: parallel running. Monitoring and management agents roll out to your machines remotely, alongside the outgoing provider’s, with no user impact. Backups are verified independently: the one thing you should never assume from the old regime is that the backups restore. Documentation is rebuilt from observation, not inherited on trust.
Cutover day: quiet, deliberately. Staff get the new support contact details, the old agents are removed, and transfers (licence billing, domain management, tenancy control) complete. Done right, the most dramatic thing anyone notices is a new number on the “IT problems?” poster.
Week 2 to 4: bedding in. The urgent items from the audit get fixed (there are always some: missing MFA, stale accounts, a backup that had not run since March), and a 30-day review closes the loop.
When the old provider plays rough
Most outgoing providers behave professionally; a minority do not, and it is worth knowing what that looks like. Documented cases run from slow-walked password handovers to outright hostility: businesses promised “the most difficult migration you have ever seen” out of pure spite, tenancy access withheld, offboarding invoiced creatively.
Three protections cover nearly all of it. First, the contract: the exit clause you checked in step one is your lever, and most obstruction collapses when quoted back calmly in writing. Second, ownership: everything registered in your name limits what can be withheld to inconvenience rather than hostage-taking. Third, the professional buffer: an experienced incoming provider has run dozens of these handovers, knows exactly what to request and in what order, and conducts the awkward correspondence so you do not have to. In genuinely obstructive cases, data-protection obligations sit on your side: your business data is your business’s data, and providers know how that argument ends.
If your relationship with the incumbent is already hostile, tell the incoming provider before notice is served; the sequencing changes (more rebuilding, less transferring), and it is a known playbook, not a crisis.
The handover checklist
What must be in your hands (or your named control) by cutover:
- All administrator credentials: servers, firewall, network kit, cloud services
- Microsoft 365 / Google Workspace tenancy ownership and billing
- Domain registrar and DNS control
- Licence inventory, with each licence’s owner and renewal date
- Backup access, plus confirmation of where historic backups live and for how long
- Network documentation: IP schemes, VLANs, WiFi keys, ISP account details
- Any code, configs or integrations built for you during the engagement
- Third-party contacts held on your behalf (ISP, printers, software vendors)
- Final invoice position and confirmed end date in writing
Anything on this list still in the old provider’s sole control after cutover is a loose end that will surface at the worst moment; chase it to zero.
Frequently asked questions
How long does switching IT providers take?
One to two weeks from signed agreement to cutover for a typical SME, running inside the old contract’s notice period. Complex estates or hostile incumbents stretch it; staff disruption should be near nil either way.
Will we have downtime during the switch?
A properly sequenced handover has no planned downtime: agents install silently, transfers happen in the background, and the cutover is administrative. The riskiest moment is actually an unmanaged gap between providers, which the overlap exists to prevent.
Can our old provider hold our data or passwords hostage?
They can try friction; they cannot lawfully keep your data or refuse credential handover indefinitely, and contract terms plus data-protection obligations sit on your side. Ownership checked in advance and a firm paper trail reduce the leverage to nearly nothing.
When is the best time to switch?
Into a quiet period for your business, never inside your busiest weeks, and timed so notice lands comfortably before any auto-renewal. For seasonal businesses we plan the cutover date first and work backwards.
Should we tell our current provider we’re unhappy first?
If the relationship is salvageable, a direct conversation is fair and occasionally works. But run the exit-terms check first regardless; the difference between negotiating and being stuck is whether you could actually leave.
What does the new provider need from us to start?
Your contract’s exit terms, the ownership picture from the checks above, and an honest description of what is and is not working. The rest (audit, sequencing, the correspondence) is their job. Switching to us starts with the free IT health check, which doubles as the incoming audit.
Make the devil-you-know calculation honestly
Price the year of slow responses, invoice surprises and unpatched risk you are tolerating, then compare it with two weeks of managed handover. If you want the real number for your situation, our free IT health check will audit what you currently have and map the exact switch plan, ownership snags included, before you commit to anything. Get in touch; the conversation is confidential, and the plan is yours either way.
