Almost nobody leaves their IT provider because of one disaster. They leave because of a slow build-up of small things. A ticket that took two days when it used to take two hours. The fourth account manager in eighteen months. A bill that keeps creeping up while the service quietly gets thinner.
At some point you start asking around. And that’s usually where it goes wrong, because most companies spend all their energy picking the new provider and almost none on the switch itself. The choice matters, obviously. But the handover is where people actually get hurt.
Here’s what to expect, in the order you’ll run into it.
Work out Why You’re Really Leaving
Before you speak to anyone, write down the reasons. Not a vague “they’re not great any more.” Actual examples with dates.
Do that and you’ll usually spot a pattern. Sometimes it’s response times. Sometimes it’s that you’ve grown and they haven’t, so nobody there can answer a cloud or security question properly. Sometimes it’s the opposite, and they’ve grown so much that you’ve become their smallest client. That one is common and nobody says it out loud. A provider built around 500-seat companies will always put a 40-seat company at the back of the queue, whatever the contract says.
This list becomes the thing you judge new providers against. Skip it and you’ll end up buying the same problem with a different logo on the invoice.
Find Out Who Holds Your Keys
Now the job most people don’t think of until it’s too late.
Go and check who actually owns your stuff. Your domain name, and which registrar account it sits in. Your Microsoft 365 tenant, and whether you have a global admin login that isn’t your provider’s. The firewall admin password. The backup console. Your software licences, which may well have been bought through their reseller account rather than yours.
There’s a good chance some of these are in your provider’s name. That’s usually not sinister. It was quicker to set up that way years ago and nobody was thinking about the ending. But it does mean your exit runs at whatever speed they feel like.
Ask about it now, in writing, while you’re still a happy customer and there’s no tension. The answers you get will tell you plenty. A provider who sends the list back within a week is one thing. A provider who goes quiet is another, and you’ve just learned something useful.
Judge New Providers by the Questions They Ask
Once you know what you own, you can start having conversations. Those conversations tell you more than the proposals do.
Be wary of anyone who quotes you within a day based on headcount alone. That’s a price, not a plan. A serious outsourced IT support company will want to look at your setup first. They’ll ask what breaks most often, what your growth plans are, whether you have compliance obligations, what your last security incident looked like. Some of those questions you won’t be able to answer, and that’s fine. The point is that they asked.
The other good sign is when they tell you something you didn’t want to hear. That your server is past saving. That your backup setup isn’t going to survive an audit. Anyone who agrees with everything in a sales meeting will also agree with everything after you sign, which sounds pleasant and isn’t.
Ask for references from clients your own size, in roughly your industry. Not their biggest name. If you’re a 30 or 50 person business, you want a provider whose small business IT support solutions are a real part of what they do, not a stripped-down version of an enterprise package.
The First 90 Days, Honestly
Say you’ve hired a team. Here’s the part that nobody warns you about.
The first month is mostly discovery. They’ll put monitoring agents on your machines, take over admin access, and write down what you have. During this period the service will feel worse than what you left. That’s not a bad sign. They don’t know your environment yet, and the person who did know it is no longer answering your calls. Expect the dip and plan around it.
Around week five or six they’ll come back with a list of everything they’ve found. Old servers, missing updates, accounts that should have been closed years ago, backups that don’t work. This is the moment relationships turn sour, because a chunk of that list will be chargeable project work rather than support. If nobody discussed it upfront, it feels like a bait and switch. Ask before you sign what usually turns up in the first audit and what it typically costs to fix.
By month three things settle. Tickets get answered at the speed you were promised, reports start arriving, and you can finally judge whether the decision was right.
Two practical bits. Don’t switch during your busiest trading period, and don’t do it in the same month as any migration. If you can afford a two or three week overlap with the old provider, take it. Paying twice for a few weeks is much cheaper than a bad handover.
Where the Price Surprises Hide
Which brings us to money.
The monthly rate is rarely where people get caught out. It’s everything around it. There’s often a one-off onboarding fee, which is fair enough given the work involved, but it should be on the table early. Then there’s the line between support and projects, and that definition is where most billing arguments come from. Get specific examples of what falls on each side.
Check whether you’re charged per user or per device, then count both, because the cheaper-looking model isn’t always cheaper for you. Check after-hours rates, the minimum term, and whether there’s an automatic annual price increase written in. And ask a direct question: on average, how much do their clients spend on out-of-scope work each year, on top of the fee? A confident provider will give you a number.
The parts of the contract worth reading twice
Most of the above should show up in the agreement, which usually gets less attention than it deserves.
Four things to look at. First, response times, and whether that means responding or fixing, because they’re very different promises. Also check who decides how urgent a ticket is, you or them. Second, documentation. It should be written in a form you can read and handed over whenever you ask. Third, your notice period and what leaving actually involves, including whether admin rights get transferred and how quickly. Fourth, who holds your licences and tenants when it’s over.
A provider who’s relaxed about exit terms is usually one who’s confident you won’t want to use them. A provider who gets cagey has told you something.
What Switching Won’t Fix
It’s worth being clear about the limits.
A new provider won’t rescue an application that was badly built in the first place. They won’t make a ten year old server safe. They can’t make your staff follow a process they’ve been ignoring for years. And if nobody inside your business owns IT decisions, the new lot will inherit exactly the same vacuum the last lot dealt with. Somebody at your end still has to be able to say yes, approve, spend and hold the provider to account. Without that, you’ll be having this same conversation again in two years.
Before you Start Calling Providers
Do two things this week. Find out who owns your domain and your Microsoft 365 tenant. And write down your real reasons for leaving, with examples.
Those two jobs will do more for the outcome than any amount of proposal comparison. The first decides how smoothly you can leave. The second decides whether you’re solving the actual problem or just moving it.
If you want a second opinion on where your current setup stands, have a chat with our team. We’ll go through it with you and give you a straight answer about whether switching is worth the disruption right now. Sometimes it isn’t, and we’ll say so. You can also read more about how our IT support works if you’d rather look first.
FAQs
- How long does it take to switch to a new outsourced IT support company?
Plan for eight to twelve weeks from signing to feeling settled. The technical handover, moving admin access and deploying monitoring, usually takes two to four weeks. After that comes documentation and the first round of fixes. Anyone promising a complete switch in a week is either working with a very simple setup or skipping the discovery work you’re paying for.
- Will we lose service while we switch providers?
You shouldn’t lose service, but you should expect it to feel slower for the first few weeks while the new team learns your environment. The genuine risk isn’t downtime, it’s a gap in cover if your old contract ends before the new provider has full access. Keep a short overlap between the two if your budget allows.
- How much should small business IT support solutions cost?
Most providers price per user or per device per month, with tiers depending on response times and whether security and after-hours cover are included. What moves the number is the size of your setup, how many cloud platforms you run, and any compliance requirements. Compare what sits inside the base tier rather than the headline rate, since fixes and projects are usually billed separately.
- Can we leave our current provider mid-contract?
Usually only by serving notice and paying out the remaining term, unless they’ve breached the agreement. Read the termination clause before you start the process. Even where you’re free to go, most contracts require 30 to 90 days’ notice, and that clock should start after you’ve secured your new provider, not before.
- Should a 30-person company hire in-house instead?
One internal hire gives you someone who knows your business, but no cover for holidays, nights or specialist areas like cloud and security. For most companies under about 60 staff, a provider works out better on both cost and coverage. Above that, a mixed setup often makes sense, with someone internal owning decisions while a provider handles the day-to-day.