Most organisations wait too long. Switching IT providers feels risky and disruptive, so the decision gets deferred past the point where the relationship is clearly not working. The irony is that the longer you wait, the harder the transition gets, because documentation decays and institutional knowledge concentrates in a provider you are trying to leave.
This page covers three things: how to tell whether the problem is fixable, what to secure before you give notice, and what a properly run transition looks like.
Signs it is time to switch IT providers
Frustration is not a reason on its own. Every provider has bad weeks. The signals worth acting on are structural, because they do not resolve themselves.
- The same incidents keep recurring. Tickets get closed, problems do not. Nobody is doing root-cause analysis.
- Nobody has documented your environment. Ask for a current network diagram and asset inventory. If it does not exist, you are dependent on one person's memory.
- There is no strategic conversation. You have never been shown a roadmap, a lifecycle plan or a budget forecast. The relationship is entirely reactive.
- Response times have quietly slipped. Often a sign the provider has grown faster than its engineering bench.
- You are being sold, not advised. Every conversation ends in a product recommendation that happens to match their margin.
- They resist sharing administrative credentials. The most serious signal on this list, and the one that should end the discussion.
Before you give notice: secure these first
This is the part organisations skip, and it is the part that turns an orderly transition into a difficult one. Establish that you actually hold or can obtain the following before you announce anything.
- Domain registrar access. Who owns the domain, and can you log in? This is the single most damaging thing to lose control of.
- DNS management. Where records are hosted and who can change them.
- Microsoft 365 or Google Workspace global admin. Confirm your organisation holds at least one global administrator account that is not the provider's.
- Firewall and network configurations. Current configs, exported, plus administrative credentials.
- Backup access and restore keys. Including whether backups live in the provider's tenant, which is common and problematic.
- Licence ownership. Whether software and cloud licences are held in your name or resold through the provider.
- Documentation. Asset inventory, network diagram, procedures, vendor contacts.
If you cannot verify these, an independent IT assessment before you switch will tell you exactly what you hold and what you do not.
What if your provider will not hand over credentials?
It happens, and it is worth stating plainly: your organisation should own the administrative credentials to its own systems. A provider that will not release them is holding your infrastructure, not managing it.
The practical sequence is to check your contract for ownership and transition clauses, escalate in writing rather than by phone so there is a record, and involve counsel if the refusal persists. Domain registrar control and tenant global admin are the two to recover first, because everything else can be rebuilt and those cannot.
How a transition actually runs
A well-run switch is a project with phases, not a switchover date.
| Phase | What happens | Typical duration |
|---|---|---|
| Discovery | Incoming provider documents the environment independently | 1–2 weeks |
| Parallel running | Both providers have access; new tooling deployed alongside old | 2–4 weeks |
| Credential transfer | Administrative access moves; old access revoked in a controlled order | Within the parallel window |
| Cutover | Support routes to the new provider; old contract ends | 1 day |
| Stabilisation | Backlog of deferred issues worked through | 2–6 weeks |
The stabilisation phase is the one nobody warns you about. Almost every transition surfaces a queue of problems the previous provider had been living with rather than fixing. That is not a sign the switch went badly. It is usually a sign it was overdue.
- Judge the relationship on structural signals, not on one bad month.
- Secure domain, DNS, tenant admin and backup access before you give notice, not after.
- A proper transition runs four to eight weeks with a parallel period, not a single cutover date.
- Expect a stabilisation backlog. It reflects the old relationship, not the new one.
Frequently asked questions
What are the signs it is time to switch IT providers?
The reliable signals are structural: recurring incidents with no root-cause analysis, no documentation of your own environment, no strategic planning conversation, slipping response times, resistance to sharing administrative credentials, and being sold products rather than advised on outcomes.
What should I secure before giving notice to my IT provider?
Administrative credentials for every system, domain and DNS control, Microsoft 365 or Google tenant global admin, firewall and network configurations, backup access and restore keys, licence ownership records, and current network documentation. Confirm you hold these before notice, not after.
How long does switching IT providers take?
A well-run transition typically runs four to eight weeks from signed agreement to full handover, depending on environment size, documentation quality and your contract notice period. Discovery and credential transfer take longest when the outgoing provider is uncooperative.
What if my IT provider will not hand over our passwords?
Your organisation should own the administrative credentials to its own systems. If a provider refuses to release them, check your contract for ownership and transition clauses, escalate in writing, and involve counsel if necessary. Domain registrar and tenant global admin access are the two most urgent to recover.
Keep exploring
Ready for a clear path forward?
Start with a Navigate Clarity Conversation. A free 30 minute review of where you stand and what to do first.
Start with a Clarity Conversation