What can go wrong when changing IT providers, and how to avoid it

iTops consultants reviewing an IT environment

A change of IT provider does not need to be disruptive. When a handover becomes complex, it is usually because a small but important detail was left unresolved before the new provider took over.

In our experience, the problems tend to fall into a few familiar areas.

1. Important access is still tied to the old provider

A domain, cloud account or administrator login can sit in the background for years without anyone inside the business needing to touch it.

The problem appears when the provider changes and nobody is quite sure who owns the account, where the login is held or whether the business has direct access.

Domains and DNS are common examples, but the same issue can affect backups, cloud platforms, software licences and third-party services. These should be identified early so ownership and access can be sorted before the handover.

2. Nobody has the full picture of the IT setup

Business IT tends to grow over time. New equipment gets added, software changes and different people become responsible for different parts of the setup.

That can leave gaps in documentation without anyone deliberately doing anything wrong. A network device may never have been documented, a configuration may only be known by one person or an old service may still be running in the background.

The new provider may need extra time to trace those details and fill in what is missing. Finding that out early is far easier than discovering it on the day they take over.

3. The old provider finishes before the new provider is ready

Notice periods tell you when a contract ends. They do not tell you whether the handover is actually ready.

Before the existing support arrangement finishes, the incoming provider should have enough information and access to take responsibility confidently. The timing should also suit the business. A payroll run, month-end close or another high-pressure period is rarely a good moment to make the switch.

Where possible, leave enough room to deal with loose ends rather than making the date the only priority.

4. Onboarding brings existing issues to the surface

A fresh look at the IT setup can reveal work that has been waiting in the background. That could be hardware nearing replacement, software that is no longer supported, backup coverage that needs reviewing or gaps in documentation.

This can be frustrating if it feels as though the provider change has suddenly created extra cost.

A good provider should separate the handover from the issues it uncovers. They should explain what was found, why it matters and which items need attention soon versus those that can sit in a longer-term plan.

5. Staff are left guessing

From an employee’s point of view, changing IT provider should be simple. Staff mainly need the effective date and a clear route for getting support.

If that communication is missed, even a technically smooth handover can feel confusing. Give staff the new contact details or support process ahead of time and make it clear when the change takes effect.

Once the transfer is complete, close out any remaining actions and remove previous provider access that is no longer required.

The examples differ, but the pattern is the same: problems become harder to deal with when they are discovered late.

Reducing the risk of a difficult handover

The common theme is preparation. Confirm access, give the incoming provider time to understand the setup, deal with missing information before it becomes urgent and keep staff informed.

If essential access or information is not ready, move the handover rather than forcing it through.

Our guide on how to switch IT providers without disrupting your business covers the full process, from preparing for the handover through to the first days with your new provider.

There are also a few practical questions businesses often ask before they make the move.

Questions this raises

Do the outgoing and incoming IT providers need to work together?

It helps, but it is not always possible. If cooperation is limited, the incoming provider may need more time to verify access, understand the setup and rebuild information that is missing.

What should we do if important administrator access cannot be found?

Identify which account or service is affected, confirm who owns it and work through the recovery options before the handover where possible. If access to a critical system is still unresolved, it is better to address that first than to rush the switch.

What should be checked immediately after the handover?

Check that staff know how to get support, that important systems and monitoring are working as expected, that any remaining actions have clear owners and previous provider access is removed.

Related reading

An iTops team member at work

Signs your business needs a managed IT provider

IT problems do not always arrive as a priority 1 incident. More often, the signs build up slowly: the same issue keeps coming back, staff find workarounds, costs are hard to predict or nobody has a clear view of what needs attention next.

Read the post

iTops can help work through your current setup, identify what needs to move and make the change as seamless as possible.

Get in touch