Switching your managed IT provider feels daunting. Your current provider controls your passwords, your infrastructure documentation, your backups. The fear of disruption keeps many businesses stuck with an MSP they've outgrown, paying for mediocre service because the transition seems riskier than the status quo.
It doesn't have to be that way. With the right process, you can transition to a new provider cleanly, without downtime, data loss, or gaps in coverage. This checklist walks you through a realistic 30-day handover.
Before You Start: Know What You Own
The single most common complication in MSP transitions is missing documentation. Many businesses discover, mid-transition, that their current provider has been the sole keeper of critical information: admin credentials, firewall configs, vendor contacts, licence keys.
Start by requesting the following from your current provider, in writing, before giving notice if possible:
- Full asset inventory (all managed devices, serial numbers, specs)
- Network documentation (IP schema, VLAN layout, firewall rules, switch configs)
- All admin credentials (domain admin, Microsoft 365 tenant admin, firewall, backup platform)
- Licence keys and vendor account logins
- Current backup configuration and most recent restore test results
- Open ticket log and any known ongoing issues
Reputable MSPs keep this documentation current and will provide it promptly. If your current provider stalls, pushes back, or claims they "don't have that documented," treat that as confirmation that you're making the right decision.
The 30-Day Transition Checklist
Week 1, Inventory and Discovery
- [ ] New MSP completes full environment discovery (devices, users, network, cloud accounts)
- [ ] All admin credentials transferred and verified
- [ ] MFA reset and reassigned to your own admin accounts (not the MSP's)
- [ ] Network documentation captured or verified
- [ ] Backup targets reviewed, confirm all critical data is being backed up
- [ ] Helpdesk communication sent to staff: who to call, how to submit tickets
Week 2, Security Baseline
- [ ] New RMM (remote monitoring and management) agent deployed to all devices
- [ ] Old MSP's RMM agent removed from all devices
- [ ] EDR deployed to all endpoints
- [ ] Patch status reviewed; outstanding critical patches queued
- [ ] MFA confirmed active on all email, VPN, and remote access accounts
- [ ] Dark web monitoring scan completed
Week 3, Cloud and Vendor Accounts
- [ ] Microsoft 365 / Google Workspace admin access transferred (remove old MSP as admin)
- [ ] Azure / AWS access reviewed and access granted to new MSP
- [ ] Internet/ISP vendor contact transferred
- [ ] Hardware vendor and warranty contacts documented
- [ ] SaaS application inventory complete
- [ ] Backup recovery test performed for at least one critical system
Week 4, Handover and Go-Live
- [ ] Old MSP formally offboarded (access revoked, contracts closed)
- [ ] All remaining open tickets reviewed and resolved or transferred
- [ ] New MSP helpdesk fully operational, test tickets submitted and resolved
- [ ] First account review meeting scheduled
- [ ] Staff communication: transition complete, here's your new IT contact
Common Pitfalls to Avoid
Giving notice too early Give notice to your current provider only after you've secured your key credentials and documentation. Some providers become uncooperative once they know they're being replaced.
Overlapping contracts Pay attention to your contract end date and notice period. Aim to start the new engagement so the first full month of new service aligns with the end of the old contract.
Forgetting cloud admin accounts It's easy to focus on servers and laptops and overlook that your current MSP may be listed as a global admin on your Microsoft 365 tenant or Azure subscription. Remove their access and verify.
Skipping the restore test Many businesses discover their backups haven't been working properly only when they try to restore. Before going live with your new provider, test at least one restore.
Why Businesses Switch MSPs
The most common reasons businesses come to North Star IT after leaving another provider:
- Slow or inconsistent response times
- Lack of proactive communication, finding out about problems after they've caused damage
- No clear security posture or tooling
- Feeling like a low-priority account
- Poor documentation of their own environment
If any of these sound familiar, you're not alone, and the transition is more manageable than it looks.
What to Expect From Your New Provider in the First 90 Days
A smooth handover is only the beginning. In the first 90 days, your new MSP should be doing more than keeping the lights on. They should be learning your environment deeply and taking action on what they find.
Expect to see:
- A security baseline report, a documented assessment of your current security posture, including any vulnerabilities or gaps identified during onboarding.
- A patching report, confirmation that all managed devices are current on OS and application patches.
- A backup verification, documented proof that your most recent backups are intact and recoverable.
- An asset inventory, a complete, up-to-date list of all managed devices, software licences, and cloud accounts.
- A roadmap conversation, early discussion of any technology risks, upcoming hardware end-of-life, or strategic improvements worth planning for.
If your new provider isn't producing these outputs in the first 90 days, ask for them. They should be standard deliverables, not extras.
What buyers ask before they sign
Ready to make the move?
Book a free transition assessment with North Star IT Services. We'll review your current environment, identify what needs to be captured, and build a transition plan with you. Call 672-983-1174 or book online.
Get a clear picture of your IT, no pressure
Book a free assessment with North Star IT. We will review your current environment, flag the real risks, and give you an honest proposal.