Switch IT providers without losing control of your systems

Third Level IT · IT field notes

1. Establish who owns each account

List your domain registrar, DNS hosting, Microsoft 365 tenant, internet circuits, firewall, backup platform and business applications. Record the business owner and the administrative contact for each. A provider may administer an account without owning it; make that distinction explicit before a transition.

Do not collect passwords in a spreadsheet or email thread. Agree on a secure handoff method and verify access with the people authorized to use it.

2. Define the contract and transition dates

Bring the renewal date and notice requirement to the planning conversation. Establish the last day of responsibility for the outgoing provider and the first day for the incoming one. Identify work that requires cooperation during the overlap. Ask the appropriate adviser to resolve contractual disputes rather than treating them as technical access problems.

3. Check backups before replacing agents

Document what is backed up, where it is stored, retention, encryption-key custody and who receives failure notifications. Determine whether backups remain accessible after the old provider’s account is removed. A successful job notification is not a restore test; request the scope and date of the most recent recovery check.

4. Transfer useful documentation

Start with network diagrams, device inventory, application dependencies, recurring maintenance, vendor contacts and known unresolved issues. The documentation does not need to be beautiful. It needs to let the next engineer understand which systems depend on each other and how to recover them.

5. Verify the new support path

Agree on how employees request help, which requests are covered, response expectations and escalation. Verify monitoring on the intended devices, backup notifications and authorized administrative access. Do not assume that an installed agent means the new provider has accepted responsibility for everything.

6. Close the old access deliberately

After the agreed handoff, review the outgoing provider’s accounts, delegated relationships, remote tools and shared secrets. Remove access according to the transition plan and test that required vendor connections still work. Record unresolved exceptions with an owner and a due date.

What to bring to a first conversation

Your approximate user count, locations, main applications, current provider arrangements and the reason you want to change are enough to start. TLI can scope a transition or a specific unresolved issue while the wider handoff is planned.