Updated November 2026
The short answer: Before you give notice, confirm your company owns its core accounts and holds its own admin access, then sign with the new provider. Request a complete handover package in writing, run a short overlap while the new provider verifies the documentation, then remove the old provider’s access, rotate passwords and test a restore. Most transitions take four to eight weeks.
An MSP transition can be a frustrating process if managed incorrectly. The following guide lays out the process and helps catch gaps before they become a real issue. An MSP transition is when one provider hands over your IT management to another company. The support, admin access, and documentation all have to change hands. If you’re moving from in-house IT to a third party, or moving into a co-managed IT service option, these steps can also provide structure and guidance. This effort also takes time. 4-8 weeks for cutover is a reasonable timeframe, but multiple sites or compliance requirements can add to that timeline. In most cases, the technical cutover is not the difficult part. Timing and security of access can be the leading causes of delays and hangups. Preparation before giving notice provides a better opportunity for a smooth transition.
These are the 15 steps we’d follow, in order.
Before You Give Notice
1. Put the Reason for Leaving in Writing
Ensure the requirements you wish to have your new MSP deliver are clearly stated, specifically making sure any complaints with your current service are used to determine requirements or requests that your new service can be measured against. And for yourself and your team, list out the items which will make you happy to have transferred to the new service in 6 months’ time. Document any risks to ensure they are included (e.g. a compliance date, busy season, system only currently operated by single person).
2. Read the Contract You Signed
- Notice period: What is the required amount of time prior to when your agreement will terminate (i.e. 30 days or 90 days)? Will it be via email to a specific individual or via certified letter to a specific individual?
- Auto-renewal: Will you be stuck in another full term of agreement should you miss a window and find that certain agreements automatically renew?
- Documentation transfer: Identify what documents you are entitled to receive and how long the outgoing service provider has to deliver them.
- Transition fees: Some providers may bill hourly to offboard their services or remove their software agents from your devices. It is better to learn about this issue now instead of on the last invoice.
Most service providers are willing to assist with a smooth transition if asked in sufficient detail. So a request to help with the transition will likely be ignored, whereas a request such as “Export the firewall config for me by the 15th” will get done as requested. Make sure these requests are made in writing.
Put the date of the notice in your calendar. Everything else in the plan works backward from that date.
3. Confirm Who Owns Your Core Accounts
Review your system accounts, domains, backup platforms, software licenses and other products you’re currently paying for. Paying for that account is not the same thing as being the named owner. Confirm ownership of all the below:
- Microsoft 365 or Google Workspace tenant
- Domain registrar and DNS
- Backup platform
- Software licenses and subscriptions
- Firewall and network management portals
Identify who owns the core accounts for your systems and see if they are registered with your provider. You don’t want to find out after the relationship has ended that your domain or a software package was registered to your provider, and not to you. This needs to be addressed while the relationship is still in place.
4. Hold Your Own Admin Access
For each critical system, confirm that there is at least one account with admin access held by your staff and stored in your password manager (not the service provider’s vault).
An additional option is to keep one emergency (break-glass) Global Admin account for Microsoft 365 that isn’t used day to day.
Key staff can also depart, making internal continuity just as important. We explore this risk in our IT Continuity Planning When Your MSP or Key Staff Leaves article.
5. Sign with the New Provider First
When you give notice to your outgoing provider, it starts a clock. Therefore, you want to have the new MSP in place, ready to take over management. As documentation, access controls, and licensing management starts changing hands, having already signed with your new provider is probably the most important step in this entire process.
While you’re signing up, check the terms in the new contract. What are the standard response times? What will not be covered? And if you ever have to change providers again, what is their transition plan? This last one is often not ever stated or discussed except in the contract, as no one wants to advertise that it’s easy to leave. At Virtuas, documentation, licensing and domains stay in your name and under your control. More on that below.
Planning the Handover
6. Get Names and Dates from the New Provider
Find out who will conduct the discovery, and when they will set up the monitoring. This will help determine how long both providers will overlap. Also plan the date of the cutover, and when the first review meeting should occur.
Hold the old contract up against the new one. The new one may not cover after-hours calls or the support of an internal app. These exclusions or potential extra costs should be defined in your new contract.
7. Assign an Internal Owner
Assign an internal owner to track this. While it is good for an internal technical person to be tracking this, it does not have to be. What is most important is that this person can make decisions and be able to follow up with both providers to verify that dates have not changed. In addition, the internal owner should have a short list of escalation points for each provider (i.e. who to call in case of a problem with a system that both providers will be supporting for a short amount of time) and the SLA from each provider for response to requests.
8. Give Written Notice
Send the notice exactly as required by the contract (e.g. via email to a specific contact). Include the date of your planned last day of service and a list of the items to be transferred in the handover (listed in Step 9 below).
9. Request the Handover Package
At minimum, ask for:
| Category | What to request |
|---|---|
| Access | Admin credentials for all systems, as well as all accounts the service provider currently accesses. |
| Documentation | Network diagrams, configurations, firewall rules, procedures |
| Inventory | Every device and software title, with license keys and renewal dates |
| Vendors | Account numbers and contacts for your ISP, phone provider, and software vendors, along with the contracts. |
| Compliance | Security policies, past audit reports, and any compliance work the provider handled for you, such as HIPAA or PCI. |
| History/open issues | Open tickets, recurring issues, or exceptions that were implemented on purpose. |
The last item above is often missed, but it can be the determining factor in understanding why a specific firewall rule was put in place or a static route was implemented.
10. Let Everyone Know Who to Call
Let your staff know the new support number to call, the new portal link to use, and what date the new provider starts. Tell the vendors who call your IT department (e.g. copier company, your ISP, software vendors) who your new IT provider contact will be.
Confirm staff know how to get assistance from the new provider and follow up with them in a couple of weeks.
Executing the Transition
11. Verify the Documentation against the Live Environment
Documentation received and documentation that is accurate are two different things. Review with your new provider the documentation that was handed over to you and verify that it accurately represents your current inventory of hardware and software. Gaps and overlaps can both be discovered, such as:
- Firewall rules no longer needed
- Admin accounts belonging to former employees or former vendors
- Backups that report success but have never been restored
- Licenses purchased under the old provider’s reseller account
12. Run a Short Overlap
Execute the transition using an ‘overlap’ period. It is recommended for about two weeks, as shown in the table below, in which both the outgoing and new service providers can be connected to all systems. Once the new provider has become familiar with the systems and is able to report that monitoring and management are in place, then the old provider tools should be disconnected from the environment.
Before you disconnect the old provider, confirm:
- Your staff can sign in to every critical system with their own admin accounts
- The new provider’s monitoring, patching and backups are reporting
- Staff have used the new help desk number or portal successfully
- Open tickets from the old provider have a named owner
- You know who to call at the old provider if something breaks during cutover
If any answer is no, extend the overlap rather than cutting over.
13. Cut Over Cleanly
Before a final cutover, ensure a full backup has been performed. Once the new provider has taken over, complete the following actions:
- Remove the outgoing provider’s accounts and remote access tools, including any admin accounts they created in your Microsoft 365 tenant
- Cancel their GDAP relationship in Microsoft 365, along with any older delegated admin (DAP) access, and put the new provider’s GDAP relationship in place
- Rotate passwords, including service accounts
- Update the new help desk number on any printed or electronically published materials
14. Test a Restore
As part of the previous step, it is important to not just complete a backup, but to test the restore of data. Backup systems are very good at showing success, but without verification, your disaster recovery process is at risk.
15. Hold a 30-Day Review and Close Out the Old Provider
Meet with the new provider approximately 30 days after their takeover. Review with them any issues found, any outstanding matters and verify progress against the scorecard listed in Step 1 above.
Close out the old contract after the new provider has confirmed management of your environment. Once closed, all old tickets should be resolved, any hardware that belonged to the old provider should be returned or wiped, and the last invoice paid.
Typical MSP Transition Timeline
| Phase | Timing | What happens |
|---|---|---|
| Plan | Weeks 1–2 | Contract review, account ownership check, provider selection |
| Notice and handover | Weeks 2–3 | Written notice, handover package requested |
| Discovery | Weeks 3–5 | Documentation verified, baseline captured |
| Overlap and cutover | Weeks 5–7 | System-by-system takeover, removing access for previous provider |
| Stabilize | Weeks 7–8+ | Close old contract, confirm test restore functionality, 30-day review |
Add time for multiple locations, regulatory requirements or heavily customized applications.
How Virtuas Handles Both Sides of a Transition
Most of this guide is about getting your environment back from a provider, sometimes in a less-than-ideal situation. With that in mind, what happens when a client joins Virtuas, and what happens if one leaves?
When a Client Joins
We onboard one client at a time. The first 30 days are for setup, knowledge transfer and getting stable. Your team shares access, documentation and installation media, and we set up monitoring, backups and support for the environment. Response-time commitments start once that transition period ends.
If your IT staff want to stay hands-on, Paired Services lets them work alongside our consultants at no additional cost. The knowledge of how your systems run shouldn’t live only with us.
While We Manage Your Environment
Licensing is purchased in your name from the start, and anything we buy for you during the contract is in your name too. Under our Open Documentation policy, you can see the documentation for your systems at any time, not only when the relationship ends.
If a Client Leaves
We hand over the documentation for every system we managed on your behalf. At Virtuas, we retain our own credentials while we are supporting your environment. Once that relationship ends, your new provider or responsible party should remove our credentials.
Virtuas is employee owned and we are not building toward a private equity exit. We are also willing to protect clients contractually if ownership changes materially. We discuss the risk of PE acquisition, and why it is an important consideration in The Quiet Risk in Managed IT.
We want clients to stay because of the quality of work. Even at the end of a contract, therefore, our deliverables will still meet that same quality.
Frequently Asked Questions
How long does an MSP transition take?
Add time for multiple sites, for various compliance issues and for software running on top of the basic services. Four to eight weeks are still a reasonable time frame after signing with your new MSP.
Is an MSP transition the same as an MSP migration?
The two terms are often used interchangeably. A transition usually refers to handing over the responsibility for your IT services to a new MSP. A migration usually refers to moving systems or data, which may be one part of a transition.
Should I tell my current MSP before I sign with a new one?
Typically, no – confirm you have admin access, choose your new provider, and plan your onboarding. Then give notice to the outgoing MSP as your contract requires.
Who owns my Microsoft 365 tenant?
Your organization should own the tenant. At least one Global Admin account should be held by your staff, and the billing should be in your name. Your MSP should only have delegated access to manage it for you.
What does GDAP have to do with switching MSPs?
GDAP is the Microsoft term for Granular Delegated Admin Privileges, the way a provider can have limited and time-bound access to a Microsoft 365 tenant to manage it for you. When you switch providers, end the old provider’s GDAP relationship and set up the new MSP within the same system.
Do companies ever return to their previous MSP?
It does happen. While transitioning to a new IT provider can take time, it is easier to make decisions and move providers when your accounts, documentation, and credentials are in your control.
How do we move to managed services for the first time?
The process to move to managed services is similar to what you would expect for any handover of responsibility. Document what your staff knows, decide what the MSP will be responsible for and what you will keep in-house and negotiate these points prior to the transfer.