Switching IT provider sounds disruptive, but done properly your team should barely notice it happened: the work is an organised handover of credentials, documentation, licences and monitoring, most of which happens behind the scenes over two to four weeks. The businesses that get burned are the ones that treat it as a leap between providers rather than a managed project. This guide gives you the timeline, the checklist and the traps.
It's written for Norfolk businesses but the process is universal. (Declared interest: this is Snap IT's website, and onboarding businesses from other providers is literally our job. The advice below is the same advice we give when we're the one being left.)
Why do businesses put off switching IT provider?
Fear of downtime, fear of the unknown, and a vague sense that the current provider "has everything". All three are fixable, and the third one is the most important to fix whether you switch or not.
If your provider holds admin credentials you've never seen, owns licences you pay for, or keeps documentation that doesn't exist outside their systems, you don't have a provider problem, you have an ownership problem, and it gets worse the longer you leave it. The signs that it's time to look around (service drifting after an acquisition, response times stretching, every fix becoming a quote) tend to be cumulative; we've written about the tell-tale signs your IT provider has been acquired, which is a common trigger.
What should you check before giving notice?
Four things, quietly, before anyone knows you're moving: your contract terms, your credential access, your licence ownership, and your backups.
- Contract. Find the notice period, the renewal date and any auto-renewal clause. Diarise the renewal window; missing it by a week can cost you a year.
- Credentials. Can someone in your business, today, log into your Microsoft 365 admin, your domain registrar, your firewall, your backup console? If not, request admin access now, as routine housekeeping. It's your infrastructure; this is a normal request.
- Licences and domains. Confirm whose name is on the Microsoft agreement, the domain registration, the antivirus licences. Anything registered to the provider needs transferring or replacing.
- Backups. Confirm where they live and that they'd survive the relationship ending. A backup you can't access without the outgoing provider's goodwill is not your backup.
What does a clean switching timeline look like?
For a typical 10 to 150 person business, plan on two to four weeks of overlap between signing with the new provider and the old contract ending.
| Phase | When | What happens |
|---|---|---|
| 1. Discovery | Before notice | New provider audits your environment, confirms what exists, flags ownership gaps |
| 2. Notice | Day 0 | Written notice per the contract; request the exit handover list in the same letter |
| 3. Parallel access | Weeks 1 to 2 | New provider gets admin access alongside the old one; monitoring and security tooling deployed; nothing switched off yet |
| 4. Transfer | Weeks 2 to 3 | Licences, domains and vendor relationships moved into your name; documentation rebuilt; helpdesk number rolled out to staff |
| 5. Cutover | Week 3 to 4 | Old provider's access revoked, credentials rotated, their software removed, final invoice settled |
The single most important line in that table is "nothing switched off yet". Overlap costs a few weeks of double-running; a gap costs you the one week where nobody was watching the backups.
What exactly should the old provider hand over?
Everything on this list, in writing. A professional outgoing provider will have it ready; a difficult one is revealing why you're leaving.
- All administrative credentials: Microsoft 365 / Google Workspace, servers, firewalls, switches, Wi-Fi controllers, backup systems
- Domain registrar and DNS access (check the registrant is your company, not theirs)
- Licence inventory: what's licensed, in whose name, renewing when
- Network documentation: IP schemes, VLANs, VPNs, how the Dereham site connects to the Norwich one
- Asset register: every device they manage, with age and warranty status
- Open and recent tickets, and any known unresolved issues
- Details of third-party contracts held on your behalf (broadband, VoIP, printing)
- Confirmation in writing, post-cutover, that their access has been removed and any copies of your data deleted
Will there be downtime during the switch?
There shouldn't be any. Nothing about changing provider requires turning anything off; it's a change of who manages, not what runs.
Your email, files and applications carry on exactly as before. The visible changes for staff are small and announced: a new helpdesk number, perhaps a new support agent icon in the system tray. Where downtime does sneak in is through neglected dependencies: a domain that lapses mid-transfer because renewal notices went to the old provider, or a firewall nobody had credentials for failing the week after cutover. Both trace back to the pre-notice checklist above, which is why it comes first.
What does switching reveal about choosing?
Every pain in this process is the shadow of a question that wasn't asked at signing time. Exit terms, credential ownership, documentation standards: they're all cheap to fix in negotiation and expensive to fix in divorce.
So when you interview replacement providers, interview them about the end as well as the start: ask how they'd hand over if you left them, and compare answers against our checklist of questions to ask an IT provider before you sign. A provider with a confident exit answer is a provider who plans to keep you by being good. (It's also why we offer our guarantee: not happy in the first 2 months and we refund your fees, help you move on, and buy your team doughnuts. An exit promise is only scary to providers who expect you to want one.) For the wider selection process, start at our guide to how to choose an IT support company in Norwich and Norfolk.
Frequently asked questions
How long does switching IT provider take?
Two to four weeks of managed overlap for most SMEs, sitting inside whatever notice period your contract requires. Complex environments (multiple sites, on-premise servers, regulated data) sit at the longer end.
Can my old IT provider hold my data or passwords hostage?
They can be obstructive, but the law and your contract are on your side: the data, domains and systems are yours. Put handover requests in writing, escalate to directors, and take professional advice if genuinely stuck. Most "hostage" situations are actually disorganisation rather than malice, which overlap time absorbs.
Should I tell my current provider I'm looking around?
Not before you've confirmed your credential and licence position, and usually not before you've chosen a replacement. Secure your access first, as routine housekeeping, then give notice properly and professionally.
Who owns our Microsoft 365 licences when we switch?
The tenancy and your data are yours regardless. Licences bought through the provider's agreement typically transfer or get repurchased through the new provider at the same or similar cost; what matters is that the tenancy's global admin ends up in your control.
What does it cost to switch IT providers?
Often nothing beyond the overlap period: most incoming providers absorb onboarding as part of winning your business. Ask directly whether onboarding, documentation rebuild and tooling deployment carry charges.
What if the old provider also supplies our broadband or phones?
List those contracts in discovery and migrate or novate them deliberately. They often outlive the support contract, which is fine; what you're avoiding is discovering a dependency the day it breaks.
