Switching IT support providers: the first 30 days
Changing your IT company does not have to mean chaos. Check which access to take over before you give notice, and what the first month with us looks like.
Switching IT support providers starts before you give notice to your current one. First, make sure that all administrator accounts, the domain and licences are registered to your company, and that you hold all the passwords. In the first week, the new provider then secures access and checks the backups. Over the next two weeks it carries out an inventory, and in the fourth week it presents a plan of clean-up work and priorities.
Most problems when you change IT company come from services registered to the previous provider and systems whose workings nobody has written down. The 30-day plan below shows how a handover typically runs with us. The actual length depends on the size of your infrastructure.
Before you give notice to your current IT company
The notice period is the best time to transfer knowledge: your current company is still working for you and is obliged to cooperate. Before you send the notice:
- read the contract: the notice period, the obligation to hand over documentation and passwords, and who owns the hardware (a firewall or backup server may be leased, for example)
- check who services are registered to: the domain, the Microsoft 365 account, antivirus and backup software licences, hardware warranties
- set a handover date that gives the new provider a few days of working alongside the previous one
These steps are not about distrusting your current provider. The Microsoft 365 administrator account may be held only by them, and the antivirus licences may be assigned to their management panel. Moving them after the contract ends then takes time, even with goodwill on both sides.
Which access do you need to take over?
Take over access to everything the previous company administers, and check who each service is registered to:
| Area | What to take over | Who it should be registered to |
|---|---|---|
| Domain and DNS | access to the registrar’s panel, the domain holder’s details | your company, with your email address |
| Microsoft 365 or Google Workspace | the global administrator account, information on which partner has administrative rights | an emergency account for your company plus named administrator accounts |
| Firewall and network | administrator passwords, configuration, security licences and subscriptions | licences in your company’s name |
| Servers and virtualisation | administrator accounts, passwords to management consoles, licence keys | your company |
| Backups | access to the console, backup encryption keys, list of jobs | keys also kept by you |
| Computer protection | access to the console, licences | your company |
| Line-of-business software | vendor contact, licence number, support contract | your company |
| Hardware | list of devices, serial numbers, warranties, accounts in manufacturer portals | your company |
Pay particular attention to Microsoft 365. The partner that sold you the licences may have administrative rights in your environment. According to Microsoft’s documentation, you can check this in the Microsoft 365 admin centre, in settings, on the Partner relationships page. That is also where you remove the partner’s roles.
Removing the roles does not end the commercial relationship itself. If the licences were bought through the previous company, transferring them has to be agreed separately.
Week 1: access and security
In the first week we do not change the architecture. We want nothing to stop working once the previous company leaves, and nobody unauthorised to have access.
- We take over the administrator accounts and change the passwords to privileged accounts.
- We remove the previous company’s access that is no longer needed: accounts, remote access tools, VPN connections to the company network.
- We check whether multi-factor authentication (MFA) is enabled for administrator accounts. If it is not, we turn it on first. We describe how we roll out MFA on our Microsoft 365 security page.
- We check the backups: whether they run, what they cover and whether data can be restored from them. We run a restore test straight away, before the first failure happens.
- We agree with you how your staff will report problems from now on: through the helpdesk in the client zone or by phone.
Weeks 2–3: inventory and documentation
Once access is secure, we document what the company actually has. The scope is similar to an IT infrastructure audit: servers, workstations, the network, licences, cloud services, line-of-business software and its vendors. We describe the scope of such a review on our IT infrastructure audit page.
This is when things nobody remembered usually come to light. It might be an old server in a cabinet that supposedly cannot be switched off, a former employee’s account with access to email, or a licence that expires next month. We record them, but we do not fix everything at once. First we need to know what depends on what.
During this time your staff report problems as usual, and we solve them. The first requests are also a good way to learn how the company works.
Week 4: plan and priorities
At the end of the first month we present:
- documentation: a list of devices, services, access rights and supplier contacts
- a list of risks, ranked from the most urgent (for example no off-site backup, or a system without vendor support)
- a clean-up plan: what we will do as part of ongoing support, and what needs a separate decision and budget
This is also the moment to match the contract to reality. After a month, it is clear how many requests the company raises and how much work the infrastructure needs. We describe the billing models on our managed IT services page.
What if the previous company does not cooperate?
Access can still be recovered, but it takes longer. The order of steps is the same. We use the vendors’ procedures (for example administrator account recovery in cloud services), reset network devices and rebuild their configuration from scratch. This may mean short service interruptions.
This happens when the cooperation ends in a dispute or the previous provider stops responding. That is why the handover of access belongs in the notice period.
What you can do on your side
- Appoint one contact person who knows the office and can make small decisions.
- Tell your staff about the change and the new way of reporting problems.
- Collect your contracts with suppliers: internet, phones, line-of-business software, hardware leasing.
If you are planning to change your IT company, write to us. We will help you prepare a list of things to take over before you send your notice.