Nobody wakes up wanting to switch IT providers. The businesses that call us about it have usually been unhappy for a year or more before the first conversation, because switching feels risky, the current arrangement is at least familiar, and everybody has something better to do. So it is worth being precise about what actually pushes a business over the line, because the patterns are remarkably consistent, and because some of them are worth acting on earlier than people do.
The provider was acquired
This is the story we hear most, and the industry keeps producing a steady supply of it. IT providers are being bought and consolidated at a remarkable pace, and from the client's side the acquisition follows a script: the announcement says nothing will change, the people you knew start leaving within a year, and the service quietly becomes something different from what you originally bought. Nobody at the new company did anything wrong, exactly. The company you chose just no longer exists, and you never chose the one that replaced it.
If your provider has been acquired, the practical advice is not to panic and not to wait passively either. Watch whether the people who know your environment are still the ones serving it. When that stops being true, the value of the relationship has changed, whatever the contract says.
The business outgrew a small shop
The mirror image, and nobody is the villain here either. A one-person or three-person shop that was perfect for you at eight employees can be genuinely overwhelmed by you at forty. The signs are gradual: projects that never start, maintenance that slips, the sense that you are now the biggest thing your provider handles and that this is not a compliment.
Small shops often know this themselves. Some of the most graceful transitions we have been part of started with the outgoing provider making the introduction.
Every call starts from scratch
Somewhere above a certain size, some providers route support through whoever is free. Each ticket gets a stranger, each stranger starts from the beginning, and nothing accumulates. The individual people are usually competent. The model prevents any of them from knowing you.
The cost of this is not the minutes spent re-explaining your setup. It is that recurring problems never get recognized as recurring. When a different person sees each occurrence, every incident looks new, and a problem can be patched monthly for a year without anyone being positioned to say the approach is wrong. We once solved a problem in the first meeting that had been open for a year, and there was nothing clever about it: we were simply the first people to look at the whole picture instead of the ticket in front of us. Read that case study.
Nobody owns the whole picture
Some businesses do not leave one provider. They leave five: an IT company, a phone vendor, a security vendor, a backup vendor, a licensing reseller, each doing a defensible job in a narrow lane, with every real problem starting as an argument about whose lane it is in. The hidden cost of that arrangement rarely shows up on any single invoice, which is what lets it survive for years.
The reasons that are not good reasons
Honesty requires the other list too, because some businesses switch when they should not.
Price alone is usually a mistake. If service is good, the people know your systems, and problems get solved, the cost of switching and re-teaching a new provider your environment routinely exceeds a modest saving. And some dissatisfaction is a communication problem wearing a service problem's clothes: a provider doing solid invisible work, and a client who has no idea, because nobody reports on it. That is fixable with a conversation, and we have told prospective clients exactly that. If the honest read on your environment is that your current provider is doing a good job, the useful thing is to tell you so, and we do.
What staying costs
The arithmetic people do in their heads is wrong in one specific way. Switching has a price you can see, so it feels expensive. Staying with a provider you no longer trust has a price you cannot see, so it feels free. It is not free, and unlike the cost of switching, it grows every month you postpone the decision.
It starts with the things your own staff stop doing. Once people believe a ticket is not worth filing, they quit filing them, and the problems that used to be small stay hidden until they are large. Someone in the office becomes the unofficial IT person because it is faster than waiting, and whatever that person was actually hired to do gets done with whatever hours are left. Projects that would genuinely help the business sit unstarted for a year, not because the money is not there, but because nobody wants to hand a significant piece of work to a company they are already unhappy with. That last one is the expensive item, and it never appears on an invoice.
Then there is the part that is a risk rather than a frustration. A provider you do not trust is also a provider you stop checking on, and the work that quietly stops happening is the work nobody watches: backups that have not been tested against an actual restore, accounts belonging to people who left months ago, patching that fell behind, an answer on your cyber insurance application that was true when you signed it and is not true now. None of that announces itself. It waits for the bad day, which is also the day it stops being cheap to fix.
Meanwhile the switch you keep deferring costs about what it would have cost last year. An assessment, a documented handover, a couple of disrupted days. That number sits still while you wait. The other one does not.
Trust is the honest test, and it is a fair one to apply to us as well as to anyone else. If you believe your provider is telling you the truth about your environment, staying and fixing the relationship is usually the better move. If you have reached the point of double checking what you are told, or of deciding it is not worth asking, the relationship has already ended in every way except the billing, and the only open question is how long you keep paying for both the service and the workarounds.
What switching actually involves
The fear of switching is mostly fear of the unknown, so here is the known version. A competent transition starts before you give anyone notice: a quiet assessment of your environment, in writing, so you are deciding on facts. Then documentation, then credentials, then the handover, sequenced so your staff keep working through all of it. The incoming provider should deal with the outgoing one directly, because refereeing that exchange is not your job. Done this way, the disruptive part of a switch is usually a day or two, not the month people imagine.
The part that goes badly is always the same part: nothing was documented, so the handover becomes archaeology. Which is itself worth knowing while you are still choosing providers, because a provider who documents your environment properly is also, on the day you eventually part ways with them, the easiest kind to leave. We consider that a feature. An arrangement that is painful to exit is not a relationship, it is a hostage situation, and we would rather be chosen every year than merely retained.
If your arrangement has stopped fitting, how we handle switching, starting with an assessment that changes nothing and obligates you to nothing. And if the assessment says you already have a good provider, you will hear that from us, in writing, for free.