How To Document Your Business Technology Before Changing IT Providers

Before changing IT providers, document the systems that keep the business running: administrator access, Microsoft 365, devices, network equipment, backups, domains, hosting, security tools, vendors, and open issues. The goal is not to produce a perfect technical encyclopedia. It is to make sure the business owns its access and the incoming provider can support the environment without guessing.

Start with ownership and access

The most important question is simple: can the business access its own technology if the current provider is unavailable or uncooperative? List every critical portal and record who controls it. This usually includes Microsoft 365, domain registration, DNS, website hosting, firewall management, backup consoles, endpoint protection, password management, accounting software, phone systems, and internet service accounts.

Do not wait until the last day to ask for access. If the current provider created accounts under its own email address, the business may need ownership transferred. If administrator accounts are shared, the transition should create named admin accounts and remove unnecessary access after the handoff.

Document Microsoft 365 and identity

Microsoft 365 is often the centre of a small business environment. Record the tenant name, administrator accounts, licensing, groups, shared mailboxes, distribution lists, Teams, SharePoint sites, OneDrive usage, and any conditional access or multi-factor authentication settings. Also note who handles user onboarding and offboarding today.

The incoming provider does not need every historical detail on day one, but they do need enough context to avoid breaking email, file access, and authentication. If former employees still have accounts, if shared mailboxes are undocumented, or if Teams and SharePoint have grown organically, flag those items as transition risks.

Map devices, network, and backup responsibilities

Create a device list with user names, device names, operating systems, approximate age, and whether each device is company-owned or personally owned. For the network, identify the internet provider, modem, firewall, switches, Wi-Fi equipment, VPN use, static IP needs, and any vendor-managed equipment.

Backups deserve separate attention. Document what is backed up, where backups are stored, how often they run, who monitors failures, and whether restores have been tested. If the current answer is unclear, say that directly. Unclear backup ownership is one of the highest-risk items in a provider transition.

Business scenario: the missing domain login

A professional services firm decides to change IT providers after repeated delays. During preparation, the office manager discovers that the domain registrar account is tied to an old contractor email address, DNS is managed through the outgoing provider, and nobody knows who controls the website hosting. Email is in Microsoft 365, but several admin roles belong to generic accounts.

Instead of switching immediately, the firm spends two weeks recovering registrar access, adding a business-owned administrator account, exporting a device list, and confirming backup status. The transition still requires coordination, but the incoming provider can now plan the cutover instead of starting with an access emergency.

Transition checklist

• List all administrator portals and confirm business-owned login access.
• Export or record Microsoft 365 users, groups, shared mailboxes, Teams, SharePoint sites, and licences.
• Document computers, servers if any, printers, firewall, switches, Wi-Fi, VPN, and remote access tools.
• Confirm domain registrar, DNS, website hosting, SSL, and email routing ownership.
• Record backup scope, backup location, monitoring responsibility, and last known restore test.
• Collect vendor contacts for internet, phones, software, accounting, line-of-business applications, and website support.
• List unresolved issues and recurring complaints so the new provider knows what needs attention first.

What not to over-document

A provider transition can get bogged down if the business tries to capture every minor setting before moving. Focus first on access, continuity, and risk. Screenshots of every configuration page are less useful than confirmed ownership of the key systems. Old ticket history may help, but a clear list of current issues is more valuable than years of unfiltered exports.

Do not share passwords through email or spreadsheets. Use a secure password manager or provider-approved transfer process. The handoff should improve access control, not create another loose copy of sensitive credentials.

It also helps to classify each system by transition sensitivity. Email, identity, backups, internet, phones, and line-of-business applications usually need the most care because they affect almost everyone. Website hosting, DNS, and domain registration may not change often, but losing control of them can create a serious problem later. Printers, scanners, and local applications are easy to overlook until staff cannot complete a normal task after the new provider starts.

Make a separate note for anything that is known but not healthy. Maybe backups exist but restore testing has never been discussed. Maybe the firewall works but only the outgoing provider knows the configuration. Maybe the business has administrator access, but it is protected by a shared mobile number. These notes help the incoming provider decide what to stabilize first instead of assuming the environment is cleaner than it is.

Next step: build a handoff folder

Create one secure handoff folder or vault with the inventory, portal list, vendor contacts, and current issues. Then use it to brief the incoming provider before notice is given. OnlineV’s Managed IT Services can help structure the ongoing support model after the transition. For related planning, see IT Consulting, Cloud Management, and Managed IT insights.