The IT Handover: What to Actually Ask When You Switch Providers

Plenty of businesses stay with an IT provider they have quietly outgrown, or even come to resent, for one reason: the switch feels frightening. What if email goes down? What if we lose access to something important? What if it turns into a mess? So they stay put, unhappy, because nobody has told them what a proper handover actually looks like. The truth is that a good transition is a routine, well-worn process, and knowing what to ask for takes most of the fear out of it.

Why Do So Many Businesses Stay With a Provider They've Outgrown?

Because the unknown feels riskier than the known, even when the known is poor. People imagine a switch as a single, terrifying cutover where everything could break at once. In reality, a professional handover is a controlled sequence of ownership checks and staged steps, run so that nothing goes dark. Here is the single most useful idea to hold on to, and it doubles as a test of any provider: the easiest way to judge an IT company is to ask how they help you leave. A good one can describe a clean, documented handover without flinching. A poor one goes vague or defensive, which tells you everything.

What Makes a Handover Go Wrong?

Almost always the same three things: admin credentials, documentation, and ownership of your core systems. The most dangerous part of switching is not setting up the new provider, which both you and they want to go smoothly. It is getting free of the old one, because that is where motivation drops and where the gaps hide. Most transition delays trace back to missing credentials or a hidden dependency, some critical account or system that turns out to be controlled by the outgoing provider rather than by you. Sort those out and the rest is manageable.

Who Actually Owns Your IT?

This is the question to answer before any other, and the answers sometimes come as a shock. You need to confirm that your business, not your provider, owns and controls your core assets: your Microsoft 365 or Google Workspace tenant, your domain name and its DNS settings, your cloud subscriptions, your backup consoles, your security tools and your password vault. The common trap is that a provider has registered your Microsoft tenant or your domain under their own partner account, with their staff holding the top-level admin rights, so that on paper you do not fully control your own environment.

Fixing this is the foundation of a safe switch. Make sure at least two administrator accounts are under your control, protected with multi-factor authentication and recorded in your own password manager, before you do anything else. Everything that follows depends on being able to act without asking permission from the company you are leaving. Confirm, too, that your domain registrar login is in your name and that you can reach your backups without the old provider's help.

What Documentation Should You Be Given?

A proper handover includes a full written record of your setup, sometimes called a technical asset register. Vague requests produce vague results, so ask for a specific, itemised list while your contract is still live. It should include:

• A network diagram showing how your systems fit together, including servers, connections and IP ranges.

• A full asset inventory of hardware and software, so you know exactly what you have.

• Software licence details, including quantities, renewal dates and who they are billed to.

• Third-party vendor contracts and contacts, such as your internet provider, phone system and any specialist software.

• Runbooks and escalation contacts, the notes on how key things are configured and who to call.

• An export of your ticket history, so the record of past issues comes with you.

Send this as a numbered request with a deadline. A numbered list tends to produce a numbered response, whereas asking loosely for "the handover pack" tends to produce very little.

What Access Needs to Transfer?

Beyond the admin accounts above, make sure control of every system that runs your business moves to you or your incoming provider: firewall, router and VPN credentials, the domain registrar, the backup portal, and your security and device-management tools. One practical detail matters here: confirm the credentials actually work before the transition begins, because a password that turns out to be wrong at the crucial moment is a classic cause of delay.

How Do Licences Move?

Carefully, and this is worth checking early. Confirm that you own your Microsoft 365, backup and security licences, and that they can transfer to a new arrangement without being wiped or cancelled in a way that deletes data. Ask directly about any offboarding or data-extraction fees, because some providers charge to hand over your own information, and you want that surprise identified now rather than on the final invoice.

What Does a Proper 30-Day Parallel Period Look Like?

The safest transitions are not a single flip of a switch but a staged handover with an overlap. During this window, typically around thirty days, both the outgoing and incoming providers have access at the same time, so email, security and support never go dark while responsibility shifts across. A sensible sequence looks like this: sign with your new provider before you serve notice on the old one, take your own independent copies of critical data and test that they actually restore, then let the new provider validate the environment, backups, security alerts and user access, before you formally close out the old relationship. Only once the new setup is proven do you remove the former provider's accounts and remote access, keeping a record of what was changed. A professional transition of this kind usually runs around four to eight weeks from agreement to full cutover, so it is a project to plan, not an afternoon's work.

What Are the Red Flags Your Provider Is Making the Exit Painful on Purpose?

Some obstruction is accidental disorganisation. Some is deliberate, designed to make leaving so daunting that you give up. Watch for these signs:

• They dodge or deflect questions about exit and handover support.

• They claim your documentation is "proprietary" and cannot be shared. It is a record of your own systems, and it is yours.

• They cannot produce an inventory of who has access to what, quickly. If they do not know, that is its own problem.

• Surprise fees appear for handing over your data or assisting the move.

• They hold the only top-level admin account for your Microsoft tenant, or your domain is registered in their name.

Any of these is a reason to be firmer, more organised, and more determined, not to abandon the move. A provider behaving this way on the way out is quietly confirming you were right to leave. It is also worth asking, in passing, whether they have been through any ownership change, merger or private-equity investment in the last couple of years, since that often sits behind a decline in the service you once valued.

The Bottom Line

Switching IT provider is far less frightening than staying somewhere that no longer serves you, once you know what to ask for. Confirm you own your tenant, domain, backups and licences. Get a proper documentation pack and working admin access. Run a staged parallel period rather than a risky single cutover, and validate everything before you close the old door. And treat any obstruction as useful information about the provider you are leaving. A good provider welcomes these questions and makes both leaving and joining painless, which is exactly how we approach onboarding new clients at SystemsCloud through our managed IT and security service. If you have been unhappy for a while but nervous to move, the process is more orderly than you fear, and the questions above are most of what you need to move with confidence.