Your business should not have to choose between tolerating poor support and accepting an uncontrolled handover. Ask the incoming provider for readiness milestones, not simply a start date. The process below is our recommended planning approach, not a universal transition timetable.
1. Separate the provider change from other projects
Switching support providers is not automatically a reason to replace every device, migrate email, or move to a different Microsoft 365 tenant. Ask them to distinguish the essential handover from remediation, upgrades, and application migrations. Identify separate approvals, costs, dependencies, and change windows.
Review notice periods, renewals, licensing commitments, and transition assistance with the appropriate advisers. Budget for agreed overlap where needed; do not cancel protection or licensing before its replacement is ready.
2. Confirm business ownership and usable access
Build a handover inventory covering company-controlled accounts, domain and DNS, cloud subscriptions, network equipment, backups, critical applications, documentation, vendor contacts, and open work. Verify authorized recovery access rather than accepting a list of usernames as proof.
Transfer secrets through an approved secure process, not an ordinary email attachment. Give the new provider only the access required for the agreed work. Microsoft's GDAP model illustrates granular, time-limited delegated access; the correct arrangement depends on the services involved. [1, 2]
If the outgoing provider will not cooperate, involve business leadership and counsel, establish legitimate ownership, and use the relevant vendor's authorized recovery process. Do not attempt to bypass access controls or assume every dependency can be recovered immediately.
3. Establish protection before removing the old tools
Agree who handles alerts and incidents during the overlap. Check the new provider's access, endpoint enrollment, failed deployments, backup authorization, and available recovery points before retiring superseded services.
Overlapping security agents can require a specific compatibility and removal plan. Ask for that plan instead of leaving both providers to assume the other is responsible. A successful installation message is not acceptance of the whole environment.
4. Plan around the work employees actually do
Filing deadlines, court dates, payroll, production schedules, and customer commitments matter more than a generic recommendation about the best month to switch. Confirm vendor availability for the chosen window and give employees a clear support route.
Tell staff whether they must enroll authentication, restart a device, test an application, or attend orientation. Separate scheduled disruption from possible unplanned interruption. No one should discover a required change only when they cannot work.
5. Agree on the go/no-go and rollback decisions
Before a change, record the expected result, test owner, time window, failure criteria, recovery option, and person authorized to stop. Do not promise that every change can simply be reversed. Identify irreversible steps and protective measures before authorizing them.
| Readiness checkpoint | Evidence to request |
|---|---|
| New support can operate | A tested contact route, approved access, named owner, and escalation path. |
| Protection has continuity | Reconciled device coverage, alert ownership, and usable backup/recovery evidence. |
| Critical work still works | A user completes a representative workflow, including printing, integrations, or remote access where relevant. |
| A failed change has a plan | Known stop criteria, authorized decision-maker, and an achievable fallback. |
6. Close the handover without leaving old access behind
Reconcile open tickets, documentation gaps, licensing, and outstanding charges. Confirm replacement coverage and then remove superseded remote-management access, delegated permissions, service accounts, and tools in the agreed sequence. Government MSP guidance specifically addresses disabling provider accounts when the relationship ends. [1]
Schedule a post-transition review. Record unresolved remediation separately so "onboarding completed" does not imply every inherited risk has been fixed.
Ask Blue Tree Technology® for milestones, dependencies, employee impacts, and acceptance checks for your environment. The objective is a controlled handover with clear ownership, not an assurance no provider can substantiate.
Sources and further reading
[1] Joint government advisory: Protecting MSPs and their customers
