Changing your IT provider is one of the more stressful moments in a company. You are afraid something will stop working, that you will lose access, or that the previous company will leave a mess. Those fears are justified, but a well-planned takeover proceeds calmly and without downtime. Below I show how to do it step by step.

Start with an inventory, before you change anything

You cannot safely take over an environment you do not know. The first step is to write down everything that makes up your IT. Without that map, the new provider works blind.

What should be on the list:

  • Physical and virtual servers, together with their functions and location.
  • Accounts and licences: Microsoft 365, Google Workspace, line-of-business systems, tools.
  • Hardware: computers, laptops, network devices, printers.
  • External services: domains, hosting, email, certificates, VPN.
  • Contracts and their notice periods.

A good partner starts exactly there. If you hear an immediate promise to fix everything in a week without getting to know the environment, that is a warning sign.

Regain control over access

This is the most important and most often neglected element. Your company must be the owner of all key accounts, not the previous provider. It happens that the domain or the Microsoft 365 administrator account is registered to the IT company rather than to the client. That is a serious problem on parting.

Make sure that:

  • Administrative accounts and domains are registered to your company.
  • All administrative passwords are changed after the handover.
  • The previous provider’s access is revoked in a controlled way and on an agreed date.
  • A secure password register is created in a manager, not in a file on the desktop.

The most common trap I see when changing provider is a domain and administrator account registered to the old IT company. Check this at the very start, because regaining access after the fact can take weeks.

Do a starting audit

Before the new provider takes responsibility for the environment, they should know what state it is in. A starting audit protects both sides: you know what you are taking over, and the provider is not responsible for neglect they had no chance to fix.

A thorough IT audit shows, among other things, the state of backups, how up to date the systems are, the security configuration and areas of heightened risk. Its result should reach you in writing and become a list of priorities for the first weeks.

Agree a transition plan and schedule

A takeover does not happen in one day. Agree a realistic schedule that minimises the risk of downtime.

A sensible order looks like this:

  • Week 1: inventory, starting audit, taking over access, securing backups.
  • Week 2: tidying up accounts and passwords, documenting the environment, setting priorities.
  • Week 3 and beyond: fixing the most urgent matters and moving to a steady support mode.

It is important that throughout this time someone is responsible for current requests. Agree exactly when the new provider takes over support, so no gap arises in which nobody is responsible.

Take care of communication with the team

People in the company have to know where to report problems from day one. Inform the team about the change, give them the new contact channel and agree who the coordinating person is on your side.

A short email with the helpdesk address, a phone number and the name of the contact person solves most of the confusion. Without it, employees call the old company or random people.

Do not burn bridges with the old provider

Even if the parting is not pleasant, an orderly handover is in your interest. Ask the predecessor for documentation, passwords and information about the environment in writing. Agree a date by which they provide support in transferring knowledge.

It is worth checking the notice period and end-of-cooperation obligations in the contract with the previous provider. Sometimes you have to align these two processes, the notice and the takeover, in time.

Secure backups from day one

Before you start changing anything in the environment, make sure you have a working backup of the data. It is your safety net in case something goes wrong during the takeover of access or the change of passwords.

In practice this means:

  • Checking where and how backups are made and who has access to them.
  • Making a fresh copy right before work begins.
  • A test restore of at least part of the data, to confirm the backup works.

Only with the certainty that the data is safe is it worth starting to tidy things up. Without that, every change carries a risk that is easy to avoid.

A short checklist

Before you consider the takeover complete, check whether:

  • You have a full inventory of the environment in writing.
  • All domains and administrative accounts are with your company.
  • Administrative passwords have been changed and old access revoked.
  • Backups work and have been tested.
  • The team knows where to report matters.
  • You have a list of priorities for the coming weeks.

A well-executed IT takeover is the foundation of calm cooperation for years. That is exactly how we set up the start in our IT outsourcing in Warsaw: first we understand and secure the environment, then we tidy it up. If you are planning to change provider and want to do it without chaos, get in touch and we will go through every stage with you.