Switching IT Provider: A Step-by-Step Guide for London Businesses

Switching IT providers is one of those tasks that gets delayed for months or years because the perceived disruption seems worse than the current frustration. But staying with an underperforming provider has real costs: slower response times, unresolved recurring issues, missed security updates, and the quiet erosion of productivity that becomes your new normal.

If you have decided it is time to change, this guide will help you execute the transition without disruption.

Signs It Is Time to Switch

Before committing to a transition, confirm that the problems you are experiencing are genuine and not simply the result of unclear expectations. These are the indicators that your relationship with your IT provider has fundamentally broken down:

Response times have deteriorated and SLAs are regularly missed without acknowledgement or improvement plans.
The same issues keep recurring without root cause analysis or permanent fixes.
Security posture is weak — no MFA enforcement, no EDR, outdated patching, no regular security reviews.
Communication is reactive only. You never hear from them unless you raise a ticket.
They cannot support your growth. As your business has evolved, their capabilities have not kept pace.
You lack visibility. No reporting, no documentation, no regular service reviews.
Key person dependency. Your entire IT knowledge sits with one engineer at the provider, and when they are unavailable, nothing gets done.

If three or more of these resonate, it is time to start planning.

Step 1: Document Your Current Environment

Before you speak to any prospective providers, document what you currently have. This inventory will form the basis of your transition plan and help new providers scope their proposal accurately.

Capture the following:

User count and locations (office, remote, hybrid split)
Devices (laptops, desktops, phones, printers, meeting room equipment)
Servers and infrastructure (on-premise, co-located, or cloud)
Software and licences (Microsoft 365 tenant, line-of-business applications, security tools)
Network infrastructure (firewalls, switches, access points, internet connections)
Domain registrations and DNS (who holds the registrar account?)
Backup systems (what is backed up, where, and how often?)
Key contracts and renewal dates (hardware warranties, software subscriptions, internet circuits)
Open issues and known problems (what is currently broken or suboptimal?)

If your current provider does not maintain this documentation — and many do not — that itself tells you something important about their operational maturity.

Step 2: Review Your Current Contract

Check your existing MSP contract for:

Notice period. Most MSP contracts require 30-90 days notice. Some have automatic renewal clauses that extend the term if notice is not given within a specific window.
Termination provisions. Look for early termination fees, minimum commitment periods, or penalty clauses.
Data and access obligations. Your contract should specify that all your data, credentials, and documentation must be handed over upon termination. If it does not, raise this with your provider in writing before giving notice.
IP and asset ownership. Confirm that any scripts, configurations, or customisations created for your environment belong to you, not the provider.

Step 3: Select Your New Provider

Run a structured evaluation rather than choosing based on a single recommendation or sales presentation. Key evaluation criteria:

Technical Capability

Can they support your specific technology stack?
Do they have experience in your industry?
What security certifications do they hold?
What tools and platforms do they use for monitoring, management, and security?

Service Model

What are their SLA commitments (response time, resolution time, availability)?
How do they handle out-of-hours and emergency support?
What does their onboarding process look like?
How do they conduct regular service reviews?

Cultural Fit

Do they communicate clearly and proactively?
Are they willing to explain things in plain language?
Do they push back when appropriate rather than simply agreeing with everything?

Commercial Terms

Is pricing transparent and predictable?
What is included in the base price versus charged additionally?
Are there any lock-in periods or exit penalties?

Request references from businesses of a similar size and industry, and actually call them.

Step 4: Plan the Transition

A well-planned transition takes 2-4 weeks from start to finish. The new provider should own the project management, but you need to be involved in key decisions.

Pre-Transition Checklist

New provider completes a technical audit of your environment
Transition plan with specific dates and responsibilities is agreed
Communication plan for your team is prepared
Fallback plan defined in case of unexpected issues
All credentials and admin access confirmed as obtainable

Credential and Access Transfer

This is the most critical and sensitive part of the transition. Your new provider needs:

Microsoft 365 global admin credentials (or a new admin account created)
Domain registrar access
Firewall and network equipment admin credentials
Server admin credentials
Backup system access
Any vendor portal logins (hardware warranties, ISP accounts, etc.)

The outgoing provider is obligated to provide these. If they resist, escalate in writing and reference the relevant contract clauses. In extreme cases, most vendors (Microsoft, domain registrars, etc.) have processes for proving ownership and recovering access.

Parallel Running Period

Best practice is to have a brief overlap period where both providers have access. This allows the new provider to familiarise themselves with your environment while the outgoing provider remains available for handover questions. One to two weeks is typically sufficient.

Step 5: Execute the Transition

During the transition itself:

Communicate with your team. Tell employees what is changing, when, and who to contact for IT support during and after the transition.
Update help desk contact details. Ensure everyone knows the new phone number, email, and ticketing system.
Verify monitoring and alerting. Confirm that the new provider’s monitoring tools are active and generating alerts before decommissioning the old ones.
Test backup and recovery. The new provider should verify that backups are running successfully and perform a test restoration.
Change all shared credentials. Any password known to the outgoing provider should be changed.
Revoke the old provider’s access. Remove their admin accounts, VPN credentials, and any remote access tools.

Step 6: Post-Transition Review

Within the first 30 days, schedule a review with your new provider to address:

Any issues identified during the transition
Gaps in documentation that need filling
Quick wins and improvements they have identified
An agreed roadmap for the first 90 days

Common Mistakes to Avoid

Giving notice before selecting a new provider. This creates a gap where you may have no support.
Not securing your credentials first. If you do not have admin access to your own systems, getting it should be your first priority.
Rushing the transition to save costs. A botched transition costs far more than a few extra weeks of overlap.
Not communicating with your team. Employees who do not know the support process has changed will continue contacting the old provider.

How Nerdster Manages Transitions

We have onboarded dozens of London businesses from other providers and have a documented transition process designed for zero disruption. Our onboarding includes a full technical audit, documented transition plan, parallel running period, and 30-day post-transition review.

If you are considering a switch and want to understand what the process looks like, start with our free IT assessment. We will evaluate your current setup, identify immediate improvements, and outline a transition plan — with no obligation to proceed.