Switching Managed IT Providers: What to Ask and How It Works

Most businesses change managed IT providers because the relationship stopped delivering, not because of one dramatic incident. Response times slip. Strategic conversations stop happening. The same problems recur. Bills creep up while the service quietly thins out.

The decision to switch is rarely the hard part. The hard part is doing it without disruption, without losing data, and without ending up with the same problems wearing a different logo. This is what a deliberate switch looks like, from your side.

Before you go shopping

Spend an hour getting your own house in order before you start meeting providers. Walking into a discovery conversation with a clear picture of your current arrangement saves time and gives you something to compare.

• What you currently pay, end to end. Helpdesk, software licensing, hardware leasing, telephony, internet, security tooling, all of it
• What contracts are in place and when they expire. Some MSP agreements have notice periods of 30 to 90 days
• Where the administrator accounts sit. Microsoft 365 tenant, domain registrar, backup tooling, email security, password manager. You should hold the master credentials, not your provider
• What documentation exists. Network diagrams, asset register, vendor contacts. If none exists, that is itself a finding
• What is actually working in the current arrangement, not just what is broken. You want to keep the good parts

If your current provider holds the credentials, the documentation, or both, you are in a weaker negotiating position than you should be. That is worth knowing before you start.

The questions to ask a prospective MSP

Most MSPs will run discovery their way. That is fine, but you should also have your own list of questions you want answered, regardless of how they structure the conversation.

How the engagement works

• Who, specifically, will my business work with? Named account manager or technical lead, or a rotating queue?
• What is your response model, business hours and after-hours? What is the SLA you commit to in writing?
• How often do we meet to talk about the business, not just open tickets?
• What is included in the monthly fee, and what is billed separately?
• What does a typical onboarding look like, and how long does it take?

How they think about security

• What security framework do you align to, ASD Essential Eight, SMB1001, or something else?
• What is included in the standard service, and what is an add-on?
• Who reviews and approves changes to firewall and identity policies?
• What is your incident response process? Who calls who, when something happens?
• How do you handle backups, and how recently was a restore tested?

How they handle the relationship

• How long do your average clients stay with you?
• Can I speak to two or three current clients of a similar size and industry?
• How do you handle disagreement, or a service issue, when it happens?
• What happens if we decide it is not working? What is the offboarding process?

The last one matters. An MSP that has a clean, documented offboarding process is one that treats the relationship as a partnership, not a lock-in.

What a clean handover actually looks like

A managed IT transition done properly takes four to eight weeks for a typical Australian SMB. Compressed timelines are possible but invite mistakes. The shape of a clean transition:

Week 1, discovery and documentation

The new provider runs full discovery on the environment. Network, identity, devices, applications, security posture, backups. Everything documented in a way the new provider can support on day one and that you can read.

Week 2, planning and risk review

A transition plan with named owners, timing, and rollback steps. Risks identified up front, not after the cutover. Communication plan for your team so they know who to call from when.

Weeks 3 to 5, parallel running

The new provider takes over administration of selected systems while the existing provider keeps the lights on. Monitoring, ticketing, change control all move across in stages, not in a single weekend.

Week 6, cutover and final handover

Existing provider hands over remaining credentials, removes its administrative access, and exits cleanly. The new provider holds the keys end to end. A final handover report goes to you.

Weeks 7 to 8, stabilisation

The new provider works through the early-issue list that surfaces in the first month, things only visible once they are running the environment. Onboarding is not over the day the previous provider walks out.

Red flags during the switch

Some signs to watch for that the transition is not being handled well:

• The new provider is reluctant to share its transition plan in writing
• The existing provider is uncooperative or slow to share credentials and documentation
• No nominated technical lead on either side
• No agreed cutover date with rollback steps
• Pressure to sign a long-term contract before transition is complete

A switch done well leaves you better informed about your own environment than you were before. The documentation alone is often more valuable than people expect.

What you should expect to feel during the process

Switching providers is uncomfortable. You will know more than you did about how the previous arrangement was operating, and some of that knowledge will be unwelcome. You will see configuration choices you did not know had been made on your behalf. You will see gaps that have been there for years.

That is normal. The point of changing providers is not to find a perfect replacement. It is to get to a clearer, more deliberate arrangement where you understand what you are paying for, what you are getting, and who is responsible for what.