Fed up with your IT provider?

Short answer: most businesses stay with an IT provider they’ve stopped trusting far longer than they should — usually because switching feels risky. In practice a competent handover happens quietly in the background over a week or two, with no downtime for your staff. The genuine risks aren’t technical: they’re auto-renewing contracts and not owning your own documentation and accounts. Sort those two out and switching is straightforward.

The signs it’s actually time

One bad week isn’t a reason to move. A pattern is. If several of these sound familiar, it’s worth a conversation:

• You’ve started working around problems instead of reporting them. This is the clearest signal of all — when your team decides it’s faster to live with something broken than to raise a ticket, you’ve already lost the value you’re paying for.
• Response times keep sliding. What used to be an hour is now “sometime today,” and nobody explains why.
• The same problems keep returning. Recurring issues mean symptoms are being treated, not causes.
• You only hear from them when something breaks. No planning, no reviews, no advice about what’s coming.
• Invoices surprise you. Work you thought was included keeps appearing as extra.
• Nobody can tell you when backups were last restore-tested. Or the answer is a vague “they run nightly.”
• You’ve outgrown them. The person who was perfect at five staff may not be right at twenty-five, and that’s nobody’s fault.
• You don’t have your own admin credentials. Deal with this one regardless of whether you move.

What switching actually involves

The fear is a weekend of chaos and a Monday of angry staff. That’s not how a planned migration works.

1. Discovery — roughly a week

The new provider documents what you actually have: servers, workstations, network gear, software, licenses, accounts, who has access to what. Plenty of businesses learn things about their own setup at this stage.

2. Preparation — runs alongside

Monitoring, security tooling and backups are brought online next to your existing setup, not instead of it. Nothing is switched off. If something needs fixing urgently, it gets fixed now.

3. Handover — a defined moment

Credentials transfer, support routes to the new team, and your old provider is formally offboarded. For your staff the practical change is a different number to call.

4. Stabilising — the first month

The new provider works through whatever the documentation turned up — the unpatched machine, the backup that was never actually running, the account belonging to someone who left in 2023.

The two things that genuinely trip people up

Auto-renewal clauses

Read your agreement today, before you do anything else. Find the renewal date and the notice period — often 30, 60 or 90 days. Miss that window and you can be locked in for another full term. Put the notice deadline in your calendar even if you’re not certain yet; you can always choose not to act on it.

Ownership of your own systems

Your domain, your Microsoft 365 or Google Workspace tenant, your website, your hosting, your backups — these should be registered to your business, not to your provider. If they’re not, that’s worth correcting immediately, whether you switch or stay. A provider who resists handing over your own accounts is telling you something important.

What if they won’t cooperate?

Most handovers are professional. Occasionally one isn’t. It’s an obstacle rather than a wall: domains can be recovered through the registrar, Microsoft 365 tenants through ownership verification, and hardware through purchase records — because those accounts belong to your business. Keep requests in writing, check your contract for an offboarding clause, and let the incoming provider handle the technical side. It happens often enough that a good provider has a process for it.

Questions to ask before you sign with anyone

Including us. If the answers are vague now, they’ll be vague when something goes wrong:

• What’s your guaranteed response time, and what happens outside business hours?
• Is support unlimited, or capped at a number of hours or tickets?
• Are on-site visits included or billed separately?
• How often are backups restore-tested, and will I see the results?
• Who specifically will I be dealing with day to day?
• Do we keep ownership of our documentation, domain and accounts — and what happens if we leave?
• What’s the contract term, the notice period, and does it auto-renew?

A fair word about your current provider

Sometimes the honest answer is that they’re fine and the relationship just needs a direct conversation. Response times slip because a provider has grown too fast. Costs creep because your business changed and nobody re-scoped. Plenty of these situations are fixable by saying plainly what isn’t working and giving them a chance to respond. If you’d rather try that first, that’s a reasonable thing to do — and if it doesn’t improve, you’ll switch with a clear conscience.

How we handle a switch

We do this regularly, and we handle the awkward parts — documenting your environment, recovering access to accounts that should have been yours all along, and coordinating the handover so you’re not stuck in the middle of two providers. Your team keeps working throughout.

Before any of that, we’ll give you an honest assessment. If your current setup is in decent shape and your provider is doing a reasonable job, we’ll say so — we’d rather tell you that than win a client who didn’t need to move. Tell us what’s frustrating you and we’ll be straight with you.

Related reading: four questions that reveal whether your provider is really handling security, and what managed IT should cost.