MSP Contract Buyer’s Checklist: What to Ask Before Switching Providers

Switching managed IT providers is one of those decisions that feels riskier than it actually is — mostly because businesses don’t know what questions to ask until something’s already gone wrong. Maybe your current provider is slow to respond, keeps quoting extra for things you thought were included, or simply hasn’t kept pace with your business as it’s grown. Whatever the reason, if you’re evaluating a new MSP, the contract and onboarding process will tell you far more about how they’ll actually treat you than any sales pitch.

This checklist walks through exactly what to ask, and what to check in writing, before you sign anything or give notice to your existing provider. Use it as a script for your next round of MSP meetings.

Contract length and exit terms

Before you even discuss services, understand how long you’re locking yourself in for and how hard it is to get out if things don’t work.

Contract term. Ask whether the agreement is month-to-month, 12 months, or a longer multi-year term, and what the pricing difference is between them. Longer terms often come with a discount, but they also reduce your flexibility if the relationship sours.

Termination clause. Find out exactly how much notice you need to give to end the contract, and whether there are exit fees or early termination penalties. A reasonable MSP should be comfortable with 30–60 days’ notice rather than trying to lock you in for years with no way out.

Auto-renewal terms. Check whether the contract automatically renews and, if so, how far in advance you need to cancel to avoid being rolled into another term. Some contracts auto-renew for the full original length, which can catch businesses out.

Service reduction flexibility. Ask if you can scale services up or down during the contract term as your headcount or needs change, without renegotiating the whole agreement.

Data and account ownership

This is one of the most overlooked areas — and one of the most important, because it determines how easily you can leave in future.

Who owns your Microsoft 365 tenant. Confirm your business owns its own Microsoft 365, Azure, and domain accounts outright, rather than the accounts being owned or administered under the MSP’s own reseller tenant. If the MSP owns the tenant, moving away later can mean migrating all your data and rebuilding your environment from scratch.

Admin access and credentials. Ask for full global admin access to your own environment, and confirm you’ll retain that access even during a dispute or after you leave. You should never be locked out of your own systems.

Data export rights. Get written confirmation of what data you’re entitled to export (emails, files, documentation, configurations) and in what format, both during the contract and if you leave.

Documentation ownership. Ask whether network diagrams, password vaults, and asset registers belong to your business or stay with the MSP. This documentation is essential for any future provider to pick up support smoothly.

Service level agreements and response times

An SLA is only useful if it’s specific enough to hold someone to, so push past vague promises like “fast response times.”

Response time by priority. Ask for documented response times broken down by issue severity — critical outages versus minor requests — rather than a single blanket figure.

Resolution time versus response time. Clarify the difference between how quickly they’ll acknowledge a ticket and how quickly they’ll actually fix the problem, since these are often confused in sales conversations.

Coverage hours. Confirm what hours support is available, whether after-hours and weekend cover is included or charged separately, and how emergencies are handled outside business hours.

Escalation path. Ask what happens if a ticket isn’t resolved within the SLA — is there an automatic escalation to a senior engineer or account manager, and is there any credit or remedy if SLAs are consistently missed?

Pricing transparency and hidden fees

Vague or bundled pricing is one of the most common sources of frustration with MSPs, so get specifics before you commit.

What’s included versus billed separately. Ask for a detailed breakdown of what’s covered under the monthly fee — help desk, patching, monitoring, backups, security tools — and what triggers an additional charge, such as after-hours work, new site setups, or project work.

Per-user or per-device pricing model. Understand exactly how pricing scales as you add or remove staff and devices, and how quickly changes take effect on your invoice.

Price increase clauses. Check whether the contract allows for annual price rises, and if so, whether they’re capped or tied to a specific index rather than left open-ended.

Onboarding and setup costs. Ask for a clear, itemised quote for any onboarding or migration fees upfront, rather than discovering them once the engagement has already started.

Onboarding process and timeline

A new MSP’s onboarding process is a strong preview of how organised they’ll be as your ongoing partner.

Discovery and documentation phase. Ask how they’ll audit your existing environment — devices, licensing, network infrastructure, and security posture — before support officially begins, and how long this typically takes.

Realistic timeline. Get a written onboarding timeline with milestones, rather than a vague “a few weeks.” Rushed onboarding is one of the biggest causes of early support gaps.

Point of contact during transition. Confirm who manages the onboarding project and who you can escalate to if something is missed or delayed during the switch.

Parallel run period. Ask whether there’s a period where both the old and new provider might need to be engaged, particularly for critical systems, to avoid a coverage gap.

Existing hardware, licensing, and vendor relationships

Switching providers doesn’t mean starting from zero, but it does require a clear plan for what you already own and license.

Hardware inventory and warranty. Ask the new MSP to review your existing hardware, confirm what’s still under warranty or vendor support, and flag anything nearing end-of-life that will need replacing soon.

Existing licensing transfer. Clarify how your existing Microsoft 365, security, and line-of-business software licenses will be transferred or re-homed under the new arrangement, and whether there’s any disruption to users during the switch.

Vendor and ISP relationships. Ask whether the new MSP will manage relationships with your internet provider, phone system vendor, and any line-of-business software vendors on your behalf, or whether that remains your responsibility.

Existing tooling reuse. Confirm whether your current backup, security, and monitoring tools can be retained, or whether the new MSP requires a shift to their preferred stack — and what that means for cost and disruption.

Security and compliance credentials

Given how central cyber security has become to IT support, don’t take a provider’s competence on trust — ask for evidence.

Security certifications and frameworks. Ask what security frameworks they align to (such as the Essential Eight) and how they help clients improve their maturity against it over time.

Incident response process. Ask what happens if your business experiences a security incident or breach — who’s notified, how quickly, and what the containment and recovery process looks like.

Staff vetting and access controls. Confirm how the MSP manages access to client systems internally, including whether staff undergo background checks and how privileged access is logged and reviewed.

Cyber insurance. Ask whether the MSP carries its own cyber liability insurance, and whether their services help support your business’s own insurance requirements and questionnaires.

References, case studies, and proven experience

Anyone can make promises in a sales meeting — a track record with businesses like yours is much harder to fake.

Industry-relevant references. Ask for references from businesses of a similar size and industry, and actually call them. Ask those references specifically about response times and how issues were handled, not just general satisfaction.

Client tenure. Ask how long their average client stays with them and why clients have left in the past. A provider that’s upfront about this is usually more trustworthy than one that dodges the question.

Case studies and outcomes. Request examples of similar migrations or transitions they’ve managed, including how they handled challenges that came up along the way.

Smooth handover from your current provider

Finally, plan the offboarding from your existing MSP just as carefully as the onboarding with your new one — this is where relationships often turn sour if it isn’t managed properly.

Notice and transition period. Confirm the exact notice period required under your current contract and build your new provider’s onboarding timeline around it, so there’s no gap in coverage.

Handover documentation request. Ask your outgoing provider in writing for full documentation, admin credentials, and asset registers, ideally before you give formal notice so there’s less risk of a delayed or incomplete handover.

Final invoice and offboarding fees. Clarify whether your outgoing provider charges any offboarding or data export fees, and get this in writing to avoid a dispute at the end of the relationship.

Communication to staff. Plan how and when you’ll communicate the change internally, so staff know who to contact for support during the transition period and aren’t caught between two providers.

Switching MSPs is a decision worth taking seriously, but it shouldn’t be a daunting one if you go in with the right questions. At SSDL, we manage this transition regularly for Australian businesses and handle the discovery, documentation, and handover coordination as a standard part of onboarding — so you’re never left without support during the switch. If you’re weighing up a change and want a second opinion on your current contract or a straightforward, no-pressure look at what a switch would involve, book a free consultation and we’ll walk you through it.