Changing IT provider is one of the decisions that most companies put off even when they know they should make it. The fear is understandable: what happens to the data? Will there be days without service? Will the outgoing provider cooperate? This article explains how to manage the process in an orderly way so the change is transparent for the team and involves no risk to the company's information.
When it makes sense to change IT provider
Not every frustration with your current provider justifies the change — sometimes there are isolated problems that can be resolved with a conversation. But there are clear signs that the relationship has reached its limit:
- Response times for incidents are unacceptable — if every problem takes days to resolve and nobody takes ownership, the real cost of that provider is far greater than the monthly invoice
- There is no documentation of the infrastructure — if only the provider knows what is installed, where the passwords are and how the network is configured, the company is in a dangerously dependent situation
- The provider is not proactive — never warns about updates, risks or possible improvements. Only shows up when something has already failed
- Opaque pricing or unjustified increases — invoices with vague items, hours nobody can verify, costs that rise without notice
- The company has grown but the provider has not — what was sufficient for 5 people does not work for 25
The biggest problem: retained information
The scenario most companies fear — and which unfortunately does happen — is that the outgoing provider retains critical information: administrator passwords, system access credentials, network configurations, licences. In some cases it is deliberate, in others it is simply disorganisation, but the result is the same: the company is blocked during the transition.
Fundamental rule: before telling your current provider that you are switching, make sure you have — or can recover — all critical credentials: server administrator passwords, access to your domain registrar panel, router and firewall credentials, and access to software licence accounts.
If you do not have access to these credentials, the first step is to request them from your current provider in an unannounced way, framing it as "we need to update the company's access inventory". A good provider will hand them over without issue. One who puts up resistance is already telling you something important.
The transition process in 6 steps
Complete inventory before communicating anything
Document everything you have: servers, devices, installed software, licences, domains, email accounts, internet providers, active contracts. This inventory is the starting point for the new provider and the guarantee that nothing is lost in the handover.
Recover all credentials and access
Local and domain administrator passwords, access to your domain registrar panel, router and firewall credentials, cloud provider administration panels, Microsoft licence accounts, Google Workspace, etc. If the current provider has access to systems on your behalf, you need to recover that access before communicating the change.
Verified full backup
Before any change, ensure you have a complete, verified copy of all critical data. Do not rely on the backup managed by the outgoing provider — make your own copy and verify it can be restored.
Parallel onboarding of the new provider
Ideally, the new provider carries out their audit and familiarisation with the infrastructure while the contract with the previous one is still active. This allows an overlap period where knowledge is transferred without urgency and without days of uncovered service.
Communicate the change with sufficient notice
Review your current contract: most have a 30-day notice period. Communicate the termination in writing (email with read receipt) and specify the effective date. Be professional — even if the relationship has been bad, a formal tone protects the company.
Change passwords and revoke access upon completion
On the day the contract ends, change all passwords the previous provider had access to and revoke their remote access. This is not distrust — it is basic security hygiene that any good provider expects and understands.
Thinking about changing IT provider?
We manage the transition process from start to finish: audit of current state, access recovery, onboarding and support from day one. No interruptions for your team.
What the new provider should document from day 1
One of the signs that distinguishes a good IT provider from a mediocre one is whether they document what they do. At the start of the relationship, the new provider should deliver — or build jointly — an infrastructure document that includes:
- Network diagram with all devices and their IPs
- Server inventory with specifications, OS and services running on each
- Licence inventory with renewal dates
- Passwords stored in a secure password manager shared with the company (not just with the provider)
- Backup procedure: what is copied, how frequently, where it is stored and how it is restored
- Escalation contacts for each service provider (internet, cloud, hardware)
If your current provider does not have this document, it is a warning sign. If the new one also does not prepare it in the first few months, you are repeating the same mistake.
How long does the change take?
For a company with 10–30 employees and standard infrastructure (server, office network, Microsoft 365), the complete process — from when the decision is made to when the new provider has full knowledge of the infrastructure — typically takes between 3 and 6 weeks. The time depends mainly on how much documentation already exists and the outgoing provider's cooperation.
At EstructuraBit we have managed multiple processes of this type. If you want to know how it would work in your specific case, tell us the situation and we will explain the exact steps.
Back to blog