How to Switch MSPs: The Australian Business Handover Checklist
Switching managed IT providers doesn't have to be stressful — but it does require preparation. This guide gives you a printable handover checklist, a phased transition plan, and the right questions to ask before you sign with anyone new.
In brief: Before you switch MSPs, complete an ownership audit of every account, domain, licence, and system your current provider touches. Run both providers in parallel during the handover, and change all administrator passwords on cutover day. A well-planned transition takes 4–6 weeks with zero downtime.
Common Reasons Businesses Switch MSPs
There's no single trigger — it's usually a combination of issues that builds over time. Here are the most common reasons Australian businesses decide it's time to move on.
Slow or inconsistent response times
Support tickets sit open for hours (or days), critical issues don't get prioritised, and you're left chasing updates instead of receiving them.
Reactive instead of proactive support
Your MSP only shows up after something breaks. There's no regular patching schedule, no security reviews, and no forward-looking IT roadmap.
Unexpected invoices and unclear billing
Line items you didn't approve, scope creep charges, or a monthly fee that keeps climbing without a clear explanation of what changed.
Loss of key staff or institutional knowledge
The technician who understood your environment has left, and nobody at the MSP seems to know your setup anymore. You're re-explaining issues from scratch.
Security concerns or a breach
A ransomware incident, a failed backup recovery, or the discovery that basic security controls like MFA were never properly enforced.
Lack of transparency or communication
No regular reporting, no account management meetings, and no visibility into what your MSP is actually doing each month.
Business outgrew the provider
Your MSP was fine when you had 10 staff, but at 50+ users with multiple locations, they can't scale with you. Response quality has dropped as you've grown.
The 4-Phase MSP Transition Process
A structured approach prevents gaps in support coverage and ensures nothing falls through the cracks during the handover.
Phase 1: Preparation & Ownership Audit
Timeline: Weeks 1–2
- Work through the Ownership and Access Audit checklist below — this is the most critical step
- Review your current MSP contract for notice period, auto-renewal dates, and exit clauses
- Send formal written notice to your current MSP per the contract terms
- Begin evaluating new MSP candidates using the questions checklist in this guide
- Identify any upcoming renewals, migrations, or projects that affect transition timing
⚠️ Do not skip the ownership audit. Businesses regularly discover their MSP registered domains, Microsoft tenants, or vendor accounts in the MSP's name — reclaiming these after the relationship ends is far harder.
Phase 2: New MSP Onboarding
Timeline: Weeks 2–4
- New MSP conducts an independent discovery audit of your environment
- Monitoring agent (RMM) deployed alongside the existing MSP's agent during overlap period
- Backup solutions verified, tested, and transitioned to infrastructure you control
- New MSP rebuilds documentation from their own audit — never rely solely on inherited docs
- Staff provided with new helpdesk contact details, portal access, and escalation paths
⚠️ Run both MSPs in parallel for a defined overlap period. This prevents monitoring gaps and gives the new MSP time to understand your environment before they're solely responsible.
Phase 3: Cutover
Timeline: Week 4 (a scheduled date)
- Remove the old MSP's monitoring agents and remote access tools from all devices
- Rotate every administrator password across all systems — servers, firewalls, switches, cloud portals
- Revoke the old MSP's access to Microsoft 365, vendor portals, and any shared accounts
- Verify DNS, email, and hosting account access is fully under your control
- Redirect all billing relationships to the new MSP or directly to your business
⚠️ Change all admin passwords on cutover day. Do not assume your previous MSP has removed their own access — verify independently.
Phase 4: Stabilisation & Optimisation
Timeline: Weeks 4–8
- New MSP addresses inherited technical debt, deferred patching, and known issues
- Security baseline assessment completed (Essential Eight alignment for Australian businesses)
- First monthly report and account management review meeting held
- SLA performance tracking begins against agreed benchmarks
- A 12-month IT roadmap is developed collaboratively with your team
⚠️ Set clear expectations for the first 90 days. A structured new MSP should present measurable improvements in security posture, response times, and documentation quality within this window.
The Ownership & Access Audit Checklist
This is the most important part of any MSP transition. Work through each category and confirm that your business — not your MSP — owns and controls every account, credential, and asset listed below. Print this section and tick items off as you go.
Domain registrar
- Log in to your domain registrar (e.g. VentraIP, Crazy Domains, GoDaddy) and confirm you are listed as the registered owner — not your MSP
- Verify your business ABN or company name appears as the registrant contact
- Confirm your own email address is on the account for renewal notices, not a generic address at the MSP's domain
- Enable registrar lock and check the domain isn't about to expire during your transition window
Microsoft 365 tenant
- Confirm you hold a Global Administrator account on the tenant — not just a user mailbox
- Verify the tenant was created under your organisation's name, not under a CSP (Cloud Solution Provider) partner tenant owned by the MSP
- Check whether your Microsoft 365 licences are purchased directly or through the MSP's partner agreement — this affects what happens if the MSP relationship ends
- Document all custom domains attached to the tenant and verify each one
DNS records
- Identify who hosts your DNS zone (this may be different from the domain registrar)
- Obtain login credentials for the DNS management panel
- Export a full copy of your current DNS records (MX, A, CNAME, TXT, SPF, DKIM, DMARC) before any changes
- Confirm you can independently create and modify DNS records without MSP involvement
Backups
- Identify where all business data backups are stored — local NAS, cloud, or the MSP's own infrastructure
- Request a test restore of a recent backup to confirm data integrity and completeness
- If backups are stored on MSP-owned infrastructure, plan data migration before the cutover date
- Verify backup retention policies and confirm no data will be deleted when the MSP relationship ends
Documentation
- Request the complete network documentation package: topology diagrams, IP address schemes, VLAN configurations
- Obtain a full hardware and software asset register, including serial numbers and warranty dates
- Request an export from any password vault or IT documentation platform (e.g. IT Glue, Hudu) covering your environment
- Get copies of any runbooks, disaster recovery plans, or standard operating procedures created for your systems
Administrator accounts
- Compile a list of every system where the MSP holds administrator or root access — servers, firewalls, switches, Wi-Fi controllers, printers
- Identify any shared accounts or service accounts the MSP created under generic names
- Document remote access tools installed by the MSP (e.g. ConnectWise, TeamViewer, Datto RMM agents)
- Plan to change every admin password and remove MSP remote access tools on cutover day
Supplier and vendor accounts
- ISP account: confirm the internet service is in your business name and you can manage it directly
- Firewall and security vendor portals (e.g. Fortinet, SonicWall, Sophos): check who is the registered owner of device licences
- Cloud subscriptions (AWS, Azure, Google Workspace): verify billing and admin access is under your organisation
- Any line-of-business SaaS tools the MSP manages on your behalf — CRM, accounting integrations, VoIP
Licensing
- Identify which software licences are purchased in your business name vs. bundled through the MSP's reseller agreements
- For reseller-managed licences (common with Microsoft, antivirus, and backup products), plan to purchase replacements or transfer before cutover
- Check licence transfer policies — some vendors allow a partner change without repurchasing
- Keep records of all licence keys and activation details
⚠️ Why this checklist matters
It's not uncommon for businesses to discover — after giving notice — that their domain, Microsoft 365 tenant, or firewall licences are registered in the MSP's name rather than their own. Sorting this out during a transition is stressful and sometimes requires legal involvement. Completing this audit before you give notice puts you in a much stronger position.
8 Questions to Ask Your Next MSP
Before signing with a new provider, ask these questions. Pay attention to how specific and transparent the answers are — vague responses are a red flag.
- 1 What is your average response time for critical issues, and is it written into the SLA?
- 2 Will we have a dedicated account manager, or will we speak to a different person each time?
- 3 Where is your helpdesk based? Are all support staff in Australia?
- 4 How do you handle the transition from our current MSP — do you have a documented onboarding process?
- 5 What does your first 30, 60, and 90 days look like after onboarding?
- 6 How do you approach cybersecurity — is it included in your base agreement or a paid add-on?
- 7 What happens if we want to leave you in the future — what's your exit process and what do we keep?
- 8 Can you provide references from businesses of a similar size and industry?
Need Help Finding a New MSP?
Use our free comparison directory to shortlist managed IT providers in your city. Filter by location, business size, industry, and the services you need.
Frequently Asked Questions
How much notice do I need to give my current MSP?
Most Australian MSP contracts require 30–90 days written notice. Review your contract carefully for notice period, auto-renewal clauses, and any exit fees. If you're within an initial contract term, there may be an early termination fee — factor this into your switching timeline.
Will switching MSPs cause downtime for my business?
A well-planned MSP transition should cause zero business downtime. The key is running both providers in parallel during the handover period, scheduling the cutover during low-activity hours, and completing all access transfers systematically before removing the outgoing MSP's tools.
What if my current MSP won't cooperate with the transition?
Unfortunately, this does happen. You are legally entitled to access your own systems, domain registrations, and business data. This is why the ownership audit is so important — completing it early gives you leverage. If an MSP refuses to hand over assets registered in your name, seek legal advice promptly.
How long does an MSP transition take?
A typical MSP transition takes 4–6 weeks: 1–2 weeks for the ownership audit and preparation, 2–3 weeks for onboarding the new MSP alongside the old one, then a scheduled cutover. Urgent transitions — for example, after a security incident — can be compressed to 1–2 weeks if necessary.
What should I look for in an MSP that handles transitions well?
Look for an MSP with a documented onboarding process that includes an independent discovery audit of your environment, a defined parallel-running period with your outgoing provider, and a clear cutover checklist. Ask to see their onboarding timeline, and request references specifically from clients who switched to them from another provider.