Skip to main content

Insights

Switching IT providers: an access and handover checklist

A change of IT provider goes smoothly when the business knows, before giving notice, what it owns, where it sits and who holds the keys. This checklist covers access, licences, domain names, backups and the order in which to take them back.

Published on By Smart ITReading 7 minutes

Organisational byline. Prepared with AI tools; every cited fact is automatically checked against its source.

A person at their workstation in front of two screens, in an office lit by a window.

The main risk when switching IT providers is not technical. It is finding out, after the contract has ended, that a critical login was only known to the outgoing provider: a Microsoft 365 admin account in one of their technicians' names, or a domain name where they are the administrative contact. The method has three stages: take stock before giving notice, transfer and check during the handover, and close the old access once the switch is done.

Choosing the new provider is covered in how to choose an IT provider. The clauses that govern the exit (notice, reversibility, return of data) are covered in managed IT contract clauses.

Before giving notice: establish what you own

Start by rereading the current contract: notice period, end-of-contract services, and any reversibility clause (the provider's commitment to hand back what you need to run the service yourself or with someone else). Then work through the inventory below without waiting for termination.

  • Check that at least one person in the business can sign in, without the provider's help, to the critical tools: Microsoft 365, domain names, backups, firewall.
  • Identify what is in the provider's name rather than yours: licences, subscriptions, domains, telecoms contracts, vendor accounts.
  • List named technician accounts that hold admin rights, and shared technical accounts.
  • Note the key dates: contract end, licence and domain renewals, hardware warranties.

The handover checklist

This table can serve as a working document between the business and both providers. Fill in the "Who holds it" column with what you have actually confirmed, not what you assume.

Handover checklist between two IT providers
ItemWhat to obtainWho holds itWhen to check
Microsoft 365 tenantList of admins and their roles; a Global Administrator account owned by the businessThe business, with some roles often assigned to the providerBefore notice, then after the switch
Microsoft partner relationshipsList of partners with delegated access, and of the partner billing your licencesMicrosoft 365 admin center and the outgoing providerDuring the handover
Passwords and vaultVault export or transfer of entries; list of service accountsOften the outgoing provider's vaultDuring the handover
Domain namesRegistrar, registrant (owner), administrative contact, expiry dateRegistrar; confirm with a WHOIS lookup (the public domain registration directory)Before notice
DNS zoneFull export of all records (website, email, third-party services)DNS host, which may differ from the registrarBefore any change
Licences and vendor contractsList of licences, contract holder, renewal dates, access to vendor portalsThe business, a reseller or the provider, depending on the caseBefore notice
BackupsConsole access, scope covered, encryption keys, test historyOutgoing provider or backup vendorRestore tested during the handover
Network documentationDiagram, IP addressing, exported firewall, Wi-Fi and switch configurationsOutgoing providerDuring the handover
Hardware and warrantiesAsset inventory, serial numbers, warranty and maintenance contractsThe business, supplier or providerBefore notice
Remote accessList of VPNs, remote support tools and agents installed on devicesOutgoing providerAfter the switch, when closing access
Telecoms contractsHolder of internet and phone lines, customer portal loginsCarrier; sometimes contracted by the providerBefore notice
Data held by the providerReturn or deletion of personal data, as you chooseOutgoing providerAt contract end

Microsoft 365: take back control of the tenant

The tenant is your organisation's own space in Microsoft 365: accounts, mailboxes, files and settings. Admin roles decide who can change what. Microsoft points out that Global Administrators have almost unlimited access to the organisation's settings and most of its data, and that only Global Administrators can view and manage subscriptions purchased through a partner.

Before announcing anything, make sure a Global Administrator account belongs to the business itself, is protected by multi-factor authentication, and has recovery options that do not depend on the provider.

A provider can also work through delegated access. With granular delegated admin privileges (GDAP), the partner's access is granular and time-bound, and customers must grant it explicitly. Two relationships then need to be kept apart: admin access and licence resale. According to Microsoft, removing GDAP relationships does not end the partner's reseller relationship. Removing the old provider's access therefore does not change who bills your licences: that is a separate step, to plan with both providers.

Domain names and DNS

The domain name carries your website and your email. For a .lu domain, the DNS-LU registry distinguishes the owner, who legally owns and operates the domain and is liable for its use, from the administrative contact, designated by the owner to manage it. Check that the owner is the business, not the provider.

The administrative contact matters just as much. According to the switching registrars procedure published by DNS-LU, no transfer of a .lu domain to another registrar can take place without the approval of the current administrative contact, and the old registrar plays no role in the process. The registry sends that contact an approval link valid for 15 days, so the email address must be correct and read by someone in the business. For other extensions, the procedure depends on the registry: check with the registrar.

DNS (the service that points the domain name to the servers for your website, email and other services) is sometimes hosted somewhere other than the registrar. Export the full zone before changing anything: one forgotten mail or verification record is enough to stop incoming email or break an online service.

Backups: get access, then restore

Access to the backup console does not prove the data can be recovered. Ask for the scope covered, where the copies are stored, any encryption keys and the test history, then have the new provider run a restore while the old one can still answer questions. The method is set out in business data backup: making sure your data can actually be restored.

Passwords, remote access and licences

Passwords are often stored in the outgoing provider's vault. Ask for the entries to be transferred to a vault owned by the business, then change the ones the old provider knew, starting with admin and service accounts. List every remote access path: VPNs, remote support tools, monitoring agents on workstations and servers. Each one remains an open door until it is removed.

For licences, hardware and telecoms contracts, ask: whose name are they in, and who can access the management portal? Anything held in the provider's name needs its own transfer, planned before the renewal date.

Data held by the outgoing provider

A provider that processes personal data on your behalf is a processor under the GDPR. The European Data Protection Board notes that the processor, at the choice of the controller, deletes or returns all personal data after the end of the provision of services. Make that choice in writing and ask for confirmation once it is done.

The order of operations

  1. 1.Before giving notice

    Reread the contract, secure an internal Global Administrator account, check the owner and administrative contact of each domain, list licences, hardware and telecoms contracts.

  2. 2.When you give notice

    Inform the outgoing provider, share the checklist and agree a handover schedule with them and with the new provider.

  3. 3.During the handover

    Collect documentation, the password vault and configuration exports; give the new provider access; test a restore; transfer domains and licences where needed.

  4. 4.At the switch

    Confirm the new provider is handling support and tell staff who their new point of contact is.

  5. 5.After the switch

    Remove the old provider's roles and delegated access, uninstall their remote tools, change the passwords they knew, and obtain the return or deletion of data.

Closing the old access last leaves a way back if something is missing; set the closing date in the handover schedule all the same.

Common pitfalls

  • A domain or licence in the provider's name, discovered at renewal.
  • A single Global Administrator, which is a provider account.
  • A backup that can be accessed but has never been restored, or is encrypted with a key nobody handed over.
  • A remote support tool still installed on devices after the contract has ended.

Frequently asked questions

In short

Most of the work in switching IT providers happens before notice is given: knowing who owns the accounts, domains and licences, and being able to sign in to them unaided. After that: transfer, check with a restore, then close the old access. In Smart IT's managed IT support, the transition starts with an inventory and the recovery of access and documentation, followed by a start-up schedule agreed with you.

Preparing a change of IT provider

The free audit, a 45-minute remote conversation followed by a written summary, lets you talk through your current situation before starting the transition.

Request a free audit