How to switch IT providers without the drama

Most organizations stay with an IT provider longer than they should because switching feels risky. What if the old provider holds the passwords? What if email goes down during the move? What if nobody knows how the firewall is set up? Those fears are reasonable. They are also manageable. A provider change done with a plan is mostly paperwork and patience.

I am usually involved in these transitions from the business side, so this is less about the technical cutover and more about the decisions, the timing and the conversations that make it go smoothly.

Before you give notice

Do not start with the termination letter. Start with your current contract and check:

• Notice period. How much notice you must give, and in what form. Thirty, sixty and ninety days are all common.
• Term and renewal. Whether you are inside a fixed term, and whether the agreement renews automatically if you miss a date.
• Exit assistance. Any clause about transition help, handover of documentation, or fees for offboarding work.
• Ownership. Who owns the accounts, licences, domain names and hardware. Anything bought through the provider may be registered in their name.
• Equipment. Leased firewalls or backup appliances may need to be returned or bought out.

Then choose your new provider and agree on a start date before you give notice. The worst position to be in is an outgoing provider who has stopped caring and an incoming one who has not started yet.

Secure what belongs to you first

In many organizations, the outgoing provider is the only party that can log into critical systems. That needs to change before anything else does. Someone inside your organization should hold, or be able to recover, administrative access to:

• Your domain registrar and DNS
• The admin centre of your email and productivity platform
• Firewalls, switches and wireless controllers
• Servers, virtualization hosts and cloud subscriptions
• Backup systems and their encryption keys
• Line-of-business applications and their vendor support portals
• Licensing and billing accounts with your software vendors

Keep these in a password vault your organization controls, not in an email thread. Once the handover is complete, change them all. A former provider should not keep working credentials, however friendly the parting.

What to ask the outgoing provider for

A professional provider expects to hand over cleanly. Put your requests in writing and be specific:

1. A complete list of credentials for every system they manage, transferred securely.
2. Network documentation: diagrams, IP ranges, firewall rules, VPN configuration, wireless settings and internet circuit details.
3. An asset inventory: devices, serial numbers, warranty dates and assigned users.
4. A software and licence inventory, including renewal dates and where each licence is purchased.
5. Backup details: what is backed up, where, how often, how long it is kept, and how to restore it.
6. Vendor contacts for your internet provider, phone system, printers and line-of-business software, with account numbers.
7. Open tickets and known issues, including anything they meant to fix and never did.
8. Scheduled tasks and scripts running in your environment, so nothing quietly stops working.

If the documentation turns out to be thin, that is useful information too. It tells you how much discovery the new provider will need to do. Get what you can and plan for the rest.

Keep the tone professional. You may need the outgoing team's help for a few weeks, and a cooperative handover is worth far more than winning an argument about a final invoice.

A 30/60/90-day transition plan

Every environment is different, but a sensible transition tends to follow the same shape.

Days 1 to 30: take control and stabilize

• Confirm and test administrative access to every critical system.
• Deploy the new provider's monitoring and support tools, and remove the old provider's agents in a planned order so no device is left unmonitored.
• Verify backups with a real test restore, not just a green status light.
• Review who has admin rights, and disable accounts that should no longer exist.
• Introduce the new helpdesk to staff: how to ask for help and what to expect.

Days 31 to 60: document and fix the obvious

• Finish discovery and rebuild documentation where it was missing.
• Apply the new provider's security baseline: multi-factor authentication, patching, endpoint protection and email security.
• Deal with anything risky found in discovery, such as unsupported devices or services exposed to the internet.
• Clean up licences that are unassigned or duplicated.

Days 61 to 90: plan forward

• Review the first monthly reports together.
• Agree on a roadmap for larger issues: device refresh, infrastructure changes and security gaps.
• Hold a first business review to check whether the transition met its goals and what still needs attention.

Tell your staff what they need to know

Staff do not need the details of a vendor change, but they do need three things: who to contact for help, when the change happens, and whether anything they do day to day will be different. A short note from leadership a week before, and a reminder on the day, prevents most of the confusion. Expect a few extra tickets in the first weeks while the new team learns your environment. That is normal, and it settles.

Common mistakes to avoid

• Giving notice before the new provider is ready to start.
• Letting the old agreement end with no overlap.
• Accepting a verbal handover instead of written documentation.
• Forgetting the domain name, which is often registered in someone else's name.
• Leaving the old provider's credentials and remote access tools in place after they have gone.

Frequently asked questions

How long does it take to switch IT providers?

For most organizations, the hands-on cutover takes a few weeks, and the full transition, including documentation and security improvements, takes around three months. Your notice period often sets the pace more than the technical work does.

What if the outgoing provider will not hand over passwords?

Start by checking your contract and asking in writing. For most cloud services, the account owner can recover administrative access directly with the vendor by proving ownership. For on-premises equipment, a new provider can often reset access, sometimes with a short planned outage. It is rarely as stuck as it feels.

Will we have downtime during the switch?

A well-planned transition should not cause noticeable downtime for staff. Most of the work happens in the background. Where a change does need a short outage, such as replacing a firewall, it can be scheduled outside working hours.

Should we tell the outgoing provider why we are leaving?

Briefly and professionally, yes. It keeps the handover cooperative, and the feedback may be useful to them. You are not obliged to negotiate.

Switching to Ceifa

When an organization moves to Ceifa, I stay close to the transition from the business side while our team handles the technical onboarding. We start by securing access and verifying backups, then apply the same security baseline we use for every managed client, and the monthly reporting gives you a clear view of progress. If you have an internal IT person, the work can be shared through our co-managed IT model instead of a full handover.

If you are thinking about a change, talk to us before you give notice. We will help you plan the timing so there is no gap in support.