How to Know When It Is Time to Leave Your MSP

There is usually no single moment when a business decides its managed service provider is no longer working. More often, the relationship wears down gradually. A ticket needs chasing, then another one does. A project keeps being pushed back. Someone internally becomes the person everyone goes to, because getting help through the proper channel feels harder than solving the problem themselves.

Meanwhile, the monthly MSP invoice keeps arriving.

Eventually, someone asks the question: is it time to leave our MSP?

A discussion on a subreddit r/ITManagers started with almost exactly that problem. The original poster said their MSP had become less responsive while costs were increasing, and asked whether bringing IT in-house was the answer. The most popular reply was blunt: “When you ask that question, the time has come.”

There is some truth in that, but the rest of the discussion showed something more useful. A poor MSP relationship does not automatically mean the managed IT model is the problem. Before deciding what to do next, you need to understand exactly what has stopped working.

Start with the simplest question: is your MSP doing what you pay them to do?

Before replacing your MSP, it helps to move beyond the general feeling that support has become “slow”. Those frustrations are valid, but the decision gets clearer when you can connect them to actual performance.

Your MSP should have agreed service levels covering response times, priority levels and escalation. Compare those commitments with what is really happening. Are urgent requests treated as urgent? Are everyday issues sitting untouched? Are tickets acknowledged quickly but taking days to resolve?

Several people in the thread recommended having this conversation before making a move. Sometimes there is a genuine mismatch between what the business considers urgent and what the provider has agreed to deliver, and that can often be fixed by reviewing service levels and expectations.

But if expectations are already clear, performance is measurable, the issue has been raised and nothing changes, the situation is different. The problem is no longer a misunderstanding. Your provider knows what you need and is still not delivering it.

6 signs your MSP relationship may no longer be working

No provider will perform perfectly every day. What matters is whether problems have become a pattern.

1. Your own staff are doing the MSP’s job, or supervising it

This was the clearest theme in the discussion. If employees are regularly fixing problems themselves, chasing unresolved tickets, coordinating vendors or checking that agreed work actually happened, the business is paying an MSP while also using its own people to cover the gaps. One commenter put it simply: if your internal team is quietly covering the MSP’s slack, you are paying twice.

The cost is easy to underestimate. An employee who spends several hours a week following up IT issues is spending that time away from the job they were hired to do. Some oversight is normal, particularly around projects, budgets and strategy. But a managed service should reduce your operational burden, and if someone in your business has to watch every ticket from start to finish, the model has started working backwards.

2. Response times look good, but problems still take too long to resolve

A fast first response is useful, but it is not the same as fast support. A provider can meet its response target by acknowledging a ticket within minutes while leaving the issue unresolved for days.

Resolution time, escalations, repeat issues and reopened tickets usually say more about the quality of service than the headline figure. If users regularly hear “we are looking into it” and still have to follow up several times, the SLA number may not reflect their real experience.

3. Projects keep stalling

An MSP can be perfectly capable of handling password resets and still struggle with anything more complicated. Cloud migrations, Microsoft 365 projects, security improvements, network upgrades and office moves all need more experienced engineers. One contributor pointed out that providers can become bottlenecked when they have plenty of Tier 1 technicians but too little Tier 2 and Tier 3 capability. Those tiers are simply the levels of technical depth, from front-line support through to senior engineering.

An MSP should not only keep today’s environment running. It should also have the depth to help you improve it. If every significant project ends up waiting for “the right engineer”, the issue may be the provider’s overall capacity rather than any individual technician.

4. Costs keep rising, but you cannot see what has improved

Higher IT costs are not automatically a reason to leave. Licensing changes, cybersecurity requirements, labour costs and hardware prices all affect what managed IT costs over time, and one commenter made exactly that point.

The better question is whether the value of the service is rising with the price. Are you getting stronger security, wider coverage, faster service, better reporting or more senior guidance? If the price climbs while the service stays flat or gets worse, the problem is value, not cost.

5. You cannot easily see how your MSP is performing

You should not have to rely on instinct to know whether your provider is doing a good job. There should be enough visibility to understand response times, recurring issues, outages, outstanding work and service levels.

One commenter reduced the question to this: is the MSP doing what you are paying them to do and meeting its SLAs? You need data to answer that properly. If the provider cannot show you that information, or the reporting is limited to surface-level figures that do not match your experience, the lack of visibility is worth questioning on its own.

6. Important responsibilities are starting to fall through the cracks

Slow support is frustrating. Missed security, backup or compliance responsibilities are far more serious.

One person in the thread said the final trigger for leaving their MSP was discovering that required backup retention had not been maintained. At that point, the issue was no longer customer service. It was trust. If you find yourself wondering whether backups are really running or whether security alerts are actually being reviewed, the relationship has moved into much more serious territory.

Sometimes fewer support tickets are a bad sign

A drop in ticket volume looks positive on a service report. In some cases, it genuinely means the environment is running better.

In other cases, people have simply stopped bothering. Employees start messaging the colleague who is “good with computers”, find their own workarounds or live with an issue because raising another ticket feels like more trouble than it is worth. Over time, that behaviour can make the MSP’s reporting look healthier while the employee experience gets worse.

This is why ticket volume should never be read in isolation. If requests are falling but frustration is not, users may have lost confidence in the support process.

Should you switch MSPs or bring IT in-house?

One of the most useful themes in the thread was that the choice is not simply between your current MSP and a fully internal IT department. If your current arrangement is failing, there are four realistic paths.

Option 1: Fix the current relationship

If the problem is mainly a mismatch in expectations, start by reviewing the agreement. Service levels, priorities, escalation, project workflows, reporting and responsibilities should all be clearly understood on both sides. If the provider takes that conversation seriously and service improves, replacing them may not be necessary. The important test is whether the MSP is willing and able to correct the problem once it has been clearly identified.

Option 2: Switch MSPs

If outsourcing still makes sense for your business but your provider consistently fails to deliver, the answer may be a better provider. One ineffective MSP does not mean managed IT does not work.

Switching only helps if you use the experience to choose more carefully next time. If projects keep stalling, ask prospective providers how senior engineering time is allocated. If tickets disappear into the queue, ask how escalations are handled. If your staff constantly coordinate third-party vendors, ask whether the MSP will take ownership of those relationships. If reporting is poor, ask exactly what you will be able to see.

Option 3: Move to co-managed IT

For some organisations, the issue is not outsourcing itself. They want stronger internal ownership and faster day-to-day responsiveness. Co-managed IT suits that well. You keep an internal IT person or team who understands your business and your people, and the MSP provides what is hard to maintain internally: after-hours support, cybersecurity, escalations, specialist engineering and larger projects.

Option 4: Bring IT fully in-house

For the right organisation, fully internal IT makes sense. But the comparison needs to go beyond putting the annual MSP fee next to one salary. An internal function also needs remote management tools, patching, endpoint security, vulnerability management, backups, documentation, security expertise, senior engineering capability and after-hours incident response. There is also the plain question of what happens when your only IT employee is on leave, sick or dealing with three urgent issues at once.

One commenter described a single internal hire as being able to handle the easier 80 per cent of everyday work. The remaining 20 per cent covers complex projects, security incidents, specialist problems and coverage gaps that a very small team struggles to fill. That does not make insourcing the wrong choice. It means the comparison should reflect the full operating model, not just headcount.

Before switching MSPs, get your evidence together

If you believe the relationship has reached its end, preparation makes both the decision and the transition easier.

Start by reviewing several months of performance data: response and resolution times, outages, missed deadlines, recurring issues and escalations. Then list everything your current MSP is responsible for, such as support, licensing, security, backups, infrastructure, vendor management and projects. Note what your own employees are doing as well, because internal time spent chasing or troubleshooting work that should sit with the MSP is part of the true cost of the current arrangement.

Before giving notice, review the contract for exit terms and notice periods. Confirm you hold administrative credentials, documentation, domains, licences, backups and anything else that will matter during the handover. Finally, write down exactly why you are leaving. That list should become the brief for your next provider.

If you are changing MSPs, choose one that fixes the reason you left

Switching providers only makes sense if the next relationship works differently.

At Affinity MSP, we think good managed IT should feel less like managing another supplier and more like having an IT team that takes responsibility for the outcome. That starts with ownership. If an issue involves another technology vendor, your employees should not become the messenger between two support desks. If a problem needs escalating, your team should not have to work out who needs to see it. If a project needs senior expertise, that expertise needs to be available.

We support Australian organisations across managed IT, co-managed IT, cybersecurity and IT projects, so clients have access to a broader team rather than one person covering every requirement. For businesses that need extended coverage, ProCare+ includes 24/7 helpdesk support, on-call assistance and access to our wider technical team. Security services can also include SentinelOne endpoint protection backed by a 24/7 Security Operations Centre.

If support has become something your team has to manage, chase or work around, it may be time to see what a different relationship could look like. We can review what is not working today, what your current provider is responsible for and what you need from the next one. That might mean fully managed IT, a co-managed arrangement alongside your internal team, or simply a clearer view of what needs to change. The aim is not just to move you from one MSP to another, but to make sure the problems that made you leave do not follow you.

Talk to Affinity MSP about switching MSPs →

FAQ

How do I know when it is time to leave my MSP?

Look for patterns rather than isolated problems. Repeatedly missed SLAs, unresolved tickets, stalled projects, rising costs without added value, poor reporting and internal employees regularly doing work the MSP should handle are all strong warning signs.

Should I switch MSPs or bring IT in-house?

It depends on why the current arrangement is failing. If one provider is the problem, switching may be the simplest fix. Co-managed IT works well when you want internal ownership plus external specialist support. Fully in-house IT generally makes more sense when the business can fund the staff, tools, expertise and coverage required.

What should I ask a new MSP before switching?

Ask how tickets are escalated, what happens when senior expertise is needed, how service levels are measured, how projects are resourced, how third-party vendors are managed, what support is available after hours and what reporting you will receive. Most importantly, explain why you are leaving your current provider and ask how their service model prevents the same problems.

Is switching MSPs difficult?

It needs careful planning, but a good incoming provider should guide the transition. Before moving, confirm contract notice periods, administrative credentials, documentation, licensing, backups, security systems and the services your current provider manages.

How does Affinity MSP help with leaving your MSP?

We take ownership of tickets and the relationship around them, including working directly with your software vendors so your staff are not stuck in the middle. We can take on fully managed IT, or run co-managed IT alongside your internal person if you want to keep one. We will also review what your current provider is responsible for and give you a straight view on whether switching, co-managing or renegotiating is the right move.