What Happens to Your IT When You Switch Providers

Why it becomes uncomfortable

A long-term IT provider knows things about your environment that aren't written down anywhere. Which server has the quirky configuration. Which licence renewal always requires a manual step. Which customer portal uses a password that was set in 2019 and never documented. This tacit knowledge is the invisible dependency that makes switching hard.

Combined with access credentials held by the outgoing provider — admin accounts, domain registrar logins, server access, licence portals — a switch can become a months-long process of recovering what should have always been yours.

What actually needs to be handed over

Credentials list: Every login, for every system, with the associated account owner name and email. Domain registrar. Hosting control panel. Microsoft 365 / Google Workspace admin. Firewall. VPN. Backup system. Website CMS. Third-party services.

Contracts and licences: What software licences are active, under whose name, with which renewal dates. Bulk licences held by the provider are particularly risky — they may not be transferable, and you may not have your own contract with the software vendor.

Documentation and tacit knowledge: Network diagram, device inventory, configuration notes, known issues, unusual dependencies. This is the hardest to transfer because it only exists in someone's head.

Where it gets stuck

Bulk contract: If your Microsoft 365 licences were purchased under the provider's reseller agreement, you may not have a direct relationship with Microsoft. Switching means either transferring the licences (requires cooperation) or buying new ones and migrating data.

Microsoft 365 admin access: If the provider holds the Global Administrator account and doesn't cooperate, recovery requires a Microsoft support process. This can take days to weeks. The fix: always maintain your own Global Admin account that is not dependent on the provider.

Domain ownership: If the domain is registered in the provider's name, you need their cooperation to transfer it. Check WHOIS now, before you start a transition. If it's not in your name, start the transfer process while the relationship is still good.

The sequence that works

Six steps in order: (1) Audit what exists — build the asset list if it doesn't exist. (2) Identify what's in your name vs the provider's name. (3) Transfer domain and hosting accounts to your own registrar/account before the relationship ends. (4) Establish your own admin accounts for all platforms. (5) Document the current environment with the outgoing provider while they're still cooperative. (6) Plan migration service by service, with parallel running for email and critical systems.

How to make it easier — before you need it

The most useful preparation happens during the existing relationship, not when you've already decided to leave. Six things that reduce switch risk:

• Maintain a current asset list (systems, accounts, licences, renewal dates)
• Register all contracts — domains, hosting, software — in the company's name
• Ensure you have your own Global Admin account in Microsoft 365
• Store all passwords in a company-owned password manager, not only with the provider
• Request documentation of your environment annually
• Include an exit clause in IT service contracts that obligates documentation delivery