Your old IT provider finishes on Friday and the new one starts Monday. Ending the contract does not remove the old provider’s accounts, credentials, or remote connections. Include access removal and verification in the handover so that administrative responsibility and technical access change together.
A handover assessment documents the systems and access in place at a specific date. Both providers can use that record to resolve gaps and agree what the new team inherits. Check the items below before marking the transition complete.
Why there's no clean handoff by default
An MSP relationship can accumulate access over years: firewalls, servers, identity consoles, registrars, DNS, backups, VPNs, endpoint agents, cloud accounts, and vendor portals. The accounts were added through separate projects and tickets, so the handover inventory needs to reconcile more than the original contract.
Treat access removal as a project with an owner, an inventory, and completion tests. Ask both providers to account for the systems they manage, then compare their records with what is installed and reachable.
Vendor-owned accounts: the administrator who never technically leaves
Look for administrator accounts tied to the provider’s domain, recovery contacts using a technician’s address, and service identities created during setup. These can remain active after the contract ends. Determine which must be transferred, replaced, or disabled.
Inventory owner and administrator accounts across identity, domain, DNS, cloud, backup, and security platforms. Verify that your business controls its ownership and recovery contacts. For accounts tied to the outgoing provider, record the agreed removal or transfer and test the result.
Retiring remote access
RMM software gives support operators elevated access for patching, monitoring, and troubleshooting. A 2023 advisory from CISA, the NSA, and MS-ISAC warned that attackers can misuse those capabilities for persistence and movement across a network. It also described the risk of reaching multiple customers through a compromised MSP relationship.
That risk isn't theoretical. In July 2021, attackers exploited a vulnerability in Kaseya's VSA remote management platform, a tool used by MSPs specifically to administer client systems, and used it to push ransomware downstream through fewer than 60 directly compromised MSP accounts into an estimated 1,500 businesses that had never been targeted individually. Sweden's Coop grocery chain shut down roughly 800 stores because their point-of-sale systems ran through an affected MSP. Over a hundred New Zealand kindergartens lost access to their systems the same weekend. None of those businesses were the target. Their provider's remote access tooling was.
Find every remote access agent and VPN profile associated with the former provider. Remove access that is no longer required or transfer it under the approved support arrangement. Test connections after the change and after a restart. Keeping an old agent for possible future use needs an explicit owner and authorization.
Forgotten infrastructure: the systems nobody remembers exist
Look beyond the central asset list. Old staging servers, test subdomains, backup destinations, trial SaaS tools, and migration buckets can remain in use long after their projects finish. Ask the outgoing provider about them and compare the answers with discovery results.
The incoming provider can manage only what it knows about. Independently map the business’s public domains and services, then reconcile that list with the handover inventory. Assign owners and retirement decisions to unexplained assets.
Transferred credentials: the vault that gets handed over but not rotated
Identify passwords, API keys, SSH keys, shared logins, and vault entries the outgoing provider could use. Transferring a vault gives the new provider a copy; it does not invalidate the copies already held elsewhere. Schedule replacement around the jobs and services that depend on each credential.
Rotate or revoke credentials that should no longer grant the outgoing provider access. Confirm that approved services work with the replacements and that the old credentials fail. Keep those results with the handover record.
Who's responsible for issues that existed before the handover?
Record pre-existing issues before the new provider begins making changes. Without a dated baseline, a later finding can be difficult to trace to a deployment or earlier configuration. Both providers should receive the relevant findings and agreed ownership.
Use the assessment date and evidence to establish what was observed at handover. That record helps resolve later questions about when an issue was present; responsibility still depends on the agreements and work involved.
A transition security checklist worth working through line by line
Before closing the transition, check administrator ownership and recovery contacts. Remove or transfer remote agents and VPN profiles, rotate shared credentials, and revoke badges or alarm codes where relevant. Reconcile public assets with both providers’ inventories. Review firewall entries for the old provider’s addresses and tools. Keep a dated assessment record and a named owner for each unresolved item.
Example language for the transition agreement
The transition agreement can specify who supplies the access inventory, who removes or transfers access, and when verification occurs. For discussion with your advisers, the following wording is one starting point:
"Outgoing Provider shall, within five (5) business days of contract termination, disable or transfer all administrative accounts, remote access tools, and credentials associated with its personnel and infrastructure, and shall deliver to Client a complete written inventory of all systems, accounts, and access points established or maintained during the engagement. Client reserves the right to commission an independent security assessment following termination to verify the completeness of this transition, at Client's discretion and expense."
This is a starting point for a conversation with an attorney, not a drop-in legal document. Contract language needs to fit your specific vendor relationship, industry, and risk tolerance, and should be reviewed by legal counsel before it goes into any binding agreement.
A handover testing procedure
Request the outgoing provider’s system and access inventory, then compare it with independent discovery and endpoint records. Investigate discrepancies before rotating credentials and removing obsolete accounts. Retest remote connections using the retired access paths. Record the verified state, unresolved issues, and owners as the baseline for the incoming provider.
Why this belongs at the handover, not after
Scope testing alongside the handover schedule. Larger environments may need authenticated tests of identity, remote access, and administrative roles as well as public-asset checks. Agree follow-up testing after the incoming provider changes tools or configuration.
The Kaseya incident showed how provider tooling can reach many customer businesses at once. During your own transition, make that access visible and verify which operators still control it.