Most of the risk in changing IT support is not technical. It is finding out, too late, that the old provider held the only key to something you need. Here is the order that avoids that.
Facts checked
Get control of your own accounts before you give notice: the domain, DNS, the Microsoft 365 or Google Workspace admin account, who bills your licences, and where your backups live. Then bring in the new provider, let the two overlap briefly, and close off the old provider's access as the last step, in writing.
The order matters more than the speed. A switch that starts with the business holding its own keys is mostly paperwork. A switch that starts with notice, while the old provider holds the only admin account, can leave you locked out of your own email at exactly the wrong moment.
Check each of these quietly, before anyone is told anything. For each one, the question is the same: can someone inside the business sign in today, with an account in the business's name?
Anything you cannot get into is the real start of the project. That list, not the size of the business, is what decides how much work the switch is.
Work through the list above and write down what you hold, what you do not, and what nobody can explain.
Where you can already sign in, add an administrator account for the business with two-step sign-in and recovery details the business controls. Where you cannot, that recovery comes first.
A short overlap lets the new provider see the setup while the old one can still answer questions about it.
Ask for admin credentials, documentation, licence billing, backup access and anything they hold for you, by a date.
Remove their administrator accounts, their delegated partner access in Microsoft 365, and their remote support software on your computers. Change the passwords they knew.
Check that email, sign in, backups and billing all work under the new arrangement. Only then end the old contract.
Paying two providers for a short time is an expense. Not paying for it means the new provider learns your setup with nobody to ask. For a simple setup a short overlap is usually enough; for an inherited or undocumented one, it is the cheapest insurance you can buy.
Asking the current provider to help with the handover keeps the relationship friendly and usually works. Securing your own admin access first is not hostile; it is simply what every business should already have. Doing both, in that order, avoids having to choose.
Sometimes the real complaint is not the provider but a setup nobody can explain. Switching providers will not fix that by itself. A new provider who starts by documenting and tidying what exists gives you a cleaner base, but it is extra work at the start, and it should be scoped and priced as such.
Read the notice period and any minimum term in your current agreement before you set dates. Switching at the end of a term avoids paying twice; switching sooner can still make sense when access or security is the problem.
Sometimes the only admin account belongs to the provider, and they have stopped replying or will not hand it over. For Microsoft 365 there are recognised routes back: a handover by whoever holds the account, Microsoft's own admin takeover where the tenant is unmanaged, or Microsoft support where it is managed. Which applies depends on how the account was set up.
That recovery is its own piece of work, written up on getting your Microsoft 365 admin access back. If the person who left was an employee rather than a provider, see former employee access.
Changing provider is a natural place to start: we take stock of what exists, get the admin access into the business's name, then look after it month to month.
Usually not before you hold your own admin access. Most providers hand over cleanly, and nothing here assumes bad faith. But notice changes the relationship, and the safest moment to ask for a password or an admin account is while everyone is still cooperating as a matter of routine.
So the usual order is: confirm what you can already get into, line up the new provider, then give notice in writing with a list of what you need handed over. Check your agreement first for a notice period, so the dates line up and you are not paying two providers longer than you meant to.
The account and the data inside it are normally yours, but the billing may not be. Many providers buy Microsoft or Google licences on your behalf and add them to their own invoice. If that relationship ends abruptly, the subscriptions can lapse along with it, and with them the mailboxes.
Ask early who pays Microsoft or Google for your licences, and plan the move of that billing as its own step, before the old contract ends. It is routine work, but only if it is done on purpose rather than discovered when mail stops.
A change of support provider does not, by itself, touch your email. The mailboxes stay where they are; what changes is who is allowed to manage them. Email only breaks during a switch when someone changes DNS records, cancels licences, or removes an account without knowing what depended on it.
If you are also moving email to a new system at the same time, that is a migration with its own order of steps, written up in how long email migration takes. Doing the provider switch first and the migration second is usually the calmer path.
The ones the old provider knew, yes, and the admin ones first. That means administrator accounts for Microsoft 365 or Google Workspace, the domain registrar, DNS, the website host, and any shared logins the provider kept on your behalf.
Changing passwords is only half of it. Old providers often also hold access that a password change does not remove: their own admin accounts in your tenant, delegated partner access, and remote support software installed on your computers. Those have to be removed one by one, which is why the last step of a switch is a written list of what was closed.
We will not put a number of days on a switch we have not looked at, because the time goes almost entirely on access, not on technical work. A business that already holds its own admin logins and registrar account can change providers quickly. One where the only admin account belongs to the old provider, or to someone who has left, has to recover that first.
The useful planning step is the inventory below. Once you know which keys you hold and which you do not, the length of the switch stops being a mystery.
For businesses that have lost Microsoft 365 admin access: finding the route back, then cleaning up and documenting what is in it.
Untangle the accounts, domains and logins nobody has a full list of.
What to check when somebody has left and you are not certain their access is closed.
How support is priced, and which model actually suits your size.
Per user, per hour, blocks, flat fee or per project, and how each one behaves.
The safe order for the move, and the traps that cost businesses their email.
Tell us roughly how many people you have, whether you are on Microsoft 365 or Google Workspace, and what you already have access to. We will tell you what the switch involves before anything changes, and you approve the scope and price before work begins.