How to Evaluate a Struggling MSP Relationship, Decide Whether It Can Be Fixed, and Change Providers Without Disrupting Your Business
A business should consider evaluating another managed IT provider when recurring technical problems, slow escalation, poor communication, unclear cybersecurity responsibilities, outdated documentation, or a lack of technology planning continue over time.
A single bad ticket is rarely enough information to make that decision. Look at what has happened over the past 3–6 months. Are employees repeatedly dealing with the same problems? Are serious issues reaching qualified engineers quickly? Does leadership know which technology investments are coming over the next 12–36 months? Can someone clearly explain what happens during a cybersecurity incident?
For a business with 25–125 employees, the MSP may manage Microsoft 365, servers, firewalls, backups, security tools, administrative access, networks, vendors, and employee support. Changing providers deserves careful planning, but staying with a provider that consistently falls short has its own cost.
A Quick Check of Your Current MSP Relationship
Your IT relationship deserves a closer review when several of these problems are happening consistently:
- Employees avoid calling the help desk because they don’t expect a useful resolution.
- The same technical problems return month after month.
- Complex problems spend too long waiting for the right engineer.
- Nobody can clearly explain who responds to cybersecurity alerts.
- Hardware replacements and IT projects regularly come as budget surprises.
- Network, asset, vendor, or recovery documentation is incomplete.
- Leadership rarely discusses technology strategy with the provider.
- Your company has grown, but the MSP’s capabilities haven’t grown with it.
None of these automatically means you need a new provider. Together, they can show that the relationship is no longer delivering what the business needs.
1. Start With What Your Employees Are Experiencing
Leadership may see monthly reports and ticket statistics, but employees experience IT support one problem at a time.
Recurring Problems Should Lead to Root-Cause Work
Let’s think about a 60-person company that generates 25 tickets over three months related to intermittent connectivity.
Employees report dropped connections, slow applications, wireless problems, and difficulty accessing shared resources. Each ticket may be resolved temporarily through a restart, reconnection, or configuration adjustment. The ticket count can show 25 completed support requests while the company still has one unresolved infrastructure problem.
A capable MSP should eventually recognize the pattern and investigate the underlying cause. That might lead to wireless testing, switch analysis, firewall review, cabling investigation, equipment replacement, or coordination with the internet provider. Support should produce information that improves the environment over time.
If the same problem continues generating tickets month after month, ask what is being done to prevent the next one.
Pay Attention to What Happens After the First Technician
Fast initial response is great, but complicated problems often need escalation.
A help desk technician may be able to handle password resets, Microsoft 365 questions, printer problems, and common workstation issues. A server outage, complex network problem, backup failure, or cybersecurity event may require a different level of expertise, but the important measure is how quickly the issue reaches that expertise.
Ask your current provider to explain the escalation path. You should know what happens when the first technician cannot resolve the problem, which technical resources are available, and who takes ownership of communication during a serious incident. Repeated delays between initial response and technical escalation are a meaningful service problem.
Employees Should Actually Want to Use the Help Desk
Ticket counts can be misleading.
An employee who has lost confidence in IT support may stop opening tickets entirely. Instead, that person asks a coworker for help, restarts the computer every morning, tolerates a recurring application problem, or finds another piece of software that gets the job done. That can create productivity problems and, in some cases, security issues.
A declining number of tickets can therefore have two very different explanations: technology is working better, or employees have stopped asking for help. Ask employees directly about their experience. Are problems getting resolved? Do they know how to contact support? Do they trust the help desk with complicated issues?
2. Look at What Leadership Is Getting From the Relationship
Managed IT should provide more than a support number. Try this framework:
SUPPORT → VISIBILITY → PLANNING
Support keeps employees and systems operating.
Visibility tells leadership what is happening across infrastructure, cybersecurity, backups, lifecycle, and technical risk.
Planning identifies what needs to change and what the company should budget for next.
A relationship that consistently stops at support is missing two important parts of managed IT.
Your Provider Should Find Problems Before Employees Do
Many important IT issues never generate help desk tickets.
A server can be approaching end-of-support while working normally. A firewall can be nearing the end of its supported lifecycle. Backup capacity can be running low. A switch can be out of warranty. Technical documentation can be years out of date. But, employees have no reason to report those conditions because nothing appears broken yet.
Someone should be looking for them. AT-NET managed IT clients receive a dedicated Technical Alignment Manager (TAM) who reviews the technical environment against established standards and identifies infrastructure, configuration, documentation, lifecycle, and other technical issues that need attention.
You should ask your current MSP:
What problems have you proactively identified in our environment during the past 12 months?
A provider responsible for proactively managing the environment should have a specific answer.
Large Technology Expenses Shouldn’t Regularly Be Surprises
Some IT expenses are unpredictable. Hardware fails unexpectedly, business priorities change, and vendors make decisions outside your control.
Many technology investments are actually predictable.
Computers age. Server warranties expire. Firewalls reach end-of-support. Software changes. Storage requirements grow. Offices expand. Cybersecurity requirements become more demanding.
If leadership repeatedly discovers an urgent $20,000–$40,000 technology requirement with little advance warning, the planning process deserves attention.
AT-NET uses dedicated vCIO resources to work with clients on technology strategy, risk, budgeting, and future projects. A 12-, 24-, and 36-month roadmap gives leadership visibility into expected hardware replacements, infrastructure upgrades, cybersecurity improvements, software changes, and larger technology projects. The roadmap does not need to predict every expense. It should make the predictable ones visible.
Cybersecurity Ownership Should Be Easy to Explain
Ask this question during your next MSP review:
If one of our security tools detects suspicious activity tonight, who is responsible for investigating it?
You should get a clear answer. The same applies to MFA, employee accounts, endpoint protection, email security, Microsoft 365, firewalls, patching, vulnerabilities, backups, and incident escalation.
Multiple vendors can make responsibility more complicated. An outside security company may monitor one system while the MSP manages another. A software provider may control a business application. That is manageable when the responsibilities are documented.
Problems occur when leadership assumes the MSP is monitoring something the MSP believes another vendor is handling. Cybersecurity responsibilities should be explicit.
Documentation Should Reflect the Environment You Have Today
Good documentation helps technicians troubleshoot faster and reduces dependence on individual people.
Depending on the environment, documentation may include network diagrams, device inventories, warranty information, vendor contacts, administrative procedures, Microsoft 365 information, server configurations, firewall details, backup systems, licensing, domain information, and recovery procedures.
That information changes constantly. So, if your network diagram shows equipment that was removed two years ago, the documentation is not doing much for the technician trying to solve today’s problem. Ask when the environment was last documented and how that information is kept current.
Your MSP Should Help With Other Technology Vendors
A business may rely on an internet provider, phone company, ERP vendor, software developers, copier company, cloud applications, security vendors, and specialized equipment providers. Technical problems often cross those boundaries.
When an ERP provider says the network is responsible and the internet carrier says the firewall is responsible, an office manager should not have to determine which company is correct.
The MSP should be capable of coordinating technical troubleshooting for the systems it manages and communicating with outside vendors when necessary.
3. Decide Whether the Relationship Can Be Fixed
Finding problems does not automatically mean the MSP needs to be replaced. A provider that understands the concerns, accepts responsibility where appropriate, and makes measurable improvements may still be the right partner. The key is moving from general dissatisfaction to specific expectations.
Instead of saying:
“Support needs to improve.”
Document the actual issue:
“Priority incidents are receiving an initial response, but technical escalation is taking too long.”
Then establish the expected change:
“We need a documented escalation process for priority incidents, including management communication and access to the appropriate engineering resources.”
Do the same for recurring problems, cybersecurity responsibilities, documentation, budgeting, and strategic planning.
Use a 60–90 Day Improvement Period
For service problems that do not require an immediate provider change, a 60–90 day review period can provide useful information. During this time, you are looking for evidence of improvement.
Are recurring problems being investigated differently? Has escalation improved? Is documentation being updated? Have security responsibilities been clarified? Has leadership received a technology roadmap?
This is much more useful than waiting another year and hoping the relationship gets better.
The Relationship May Be Worth Keeping When:
The provider acknowledges the problems, establishes clear ownership, provides a realistic corrective plan, and demonstrates measurable improvement during the review period.
It May Be Time to Evaluate Other Providers When:
The same problems continue after they have been raised, technical resources remain inadequate, cybersecurity responsibilities are still unclear, documentation does not improve, or proactive planning never materializes.
If You Decide to Switch, Here’s What Happens Next
Once leadership decides to evaluate another MSP, the process should become more structured.
The goal is to understand what you have, protect access to company systems, maintain security and support coverage, and give the incoming provider enough information to assume responsibility.
Before You Give Notice
Review the existing MSP agreement. Pay attention to termination provisions, notice requirements, renewal dates, transition obligations, outstanding projects, licensing arrangements, and any applicable fees.
Identify critical company-owned accounts and services as well. That may include Microsoft 365, domain registrations, DNS, cloud platforms, internet services, backup systems, security services, and business applications.
Leadership should understand how those systems are currently owned and administered before the transition begins.
Before the Handoff
Create an inventory of the information and access the incoming provider will need. This typically includes administrative credentials, Microsoft 365 access, domain and DNS information, firewall configurations, servers, backup systems, security platforms, software licensing, vendor contacts, internet circuits, network information, and existing technical documentation.
Credentials should be transferred through an appropriate secure process rather than ordinary email.
The incoming provider should tell you exactly what it needs.
During Onboarding
A new MSP should build its own understanding of the environment rather than assuming the existing documentation is complete.
Onboarding may include reviewing users and devices, Microsoft 365, servers, firewalls, network equipment, backups, cybersecurity tools, vendors, applications, administrative access, and documentation.
Employees also need clear instructions. They should know when the new provider becomes responsible for support, how to contact the help desk, what happens to existing tickets, and how urgent issues will be handled during the transition.
During the Technical Handoff
This part requires coordination between providers. The outgoing MSP may need to remove remote monitoring, endpoint management, security, backup, or other software. The incoming provider may be deploying replacement tools.
Those activities should be coordinated so the company does not accidentally create a gap in monitoring, endpoint protection, backup coverage, or support.
Changing administrative access also needs to be planned. Removing access too early can disrupt the transition. Leaving unnecessary privileged access in place afterward creates a security concern.
During the First 30–90 Days With the New MSP
A new provider will probably identify improvements it wants to make, but everything does not need to change immediately.
Critical security problems, unsupported systems, failed backups, and significant operational risks may deserve immediate attention. Lower-priority configuration changes and longer-term improvements can be scheduled.
The first few months should establish a baseline:
What needs immediate attention?
What should be corrected this year?
What belongs on the 12-, 24-, and 36-month roadmap?
That creates a more controlled transition than changing dozens of systems simply because the new provider prefers a different configuration.
Compare MSPs Based on the Problems You’re Trying to Solve
If slow escalation is driving the change, ask every prospective provider to explain its escalation process.
If cybersecurity is the concern, compare actual security responsibilities.
If budgeting has been poor, ask to see how the provider handles lifecycle planning and technology roadmaps.
Try this comparison sheet:
| Area | Current MSP | Prospective MSP |
|---|---|---|
| Help Desk Coverage | ||
| Technical Escalation | ||
| Cybersecurity Responsibility | ||
| Backup & Recovery | ||
| Documentation | ||
| Proactive Technical Reviews | ||
| IT Budget Planning | ||
| After-Hours Support | ||
| Onsite Capabilities | ||
| Vendor Management |
Ask providers to explain how each service works.
Two MSPs can both check the box for “proactive IT management” while providing very different services.
A Simple Test for Your Current MSP Relationship
Before making the final decision, leadership should be able to answer three questions:
1. Are our employees getting dependable support?
Problems should be resolved, recurring issues should receive deeper investigation, and complicated problems should reach the appropriate technical resources.
2. Do we understand the current condition and risks in our technology environment?
Leadership should have visibility into infrastructure, cybersecurity, backups, aging equipment, documentation, and important technical concerns.
3. Do we know what technology investments are coming over the next 12–36 months?
Predictable hardware replacements, infrastructure projects, cybersecurity improvements, and other major technology needs should be visible early enough to budget for them.
If the answer to one of these questions is consistently no, address it with the current provider, but if the answer to all three is no, the MSP relationship deserves a serious review.
Frequently Asked Questions About Switching Managed IT Providers
What are the biggest signs that it’s time to change MSPs?
Recurring unresolved problems, slow escalation, poor communication, unclear cybersecurity responsibilities, outdated documentation, surprise technology expenses, and a lack of proactive planning are common reasons to evaluate another provider. Look for patterns rather than isolated incidents.
How often should a business evaluate its managed IT provider?
A business should conduct a meaningful MSP review at least annually and whenever recurring service, cybersecurity, communication, or planning problems develop. The evaluation should cover proactive management and strategic planning in addition to help desk performance.
Should we give our current MSP a chance to improve?
When there is no urgent security or operational reason to leave immediately, establishing specific expectations and reviewing progress over 60–90 days can help determine whether the relationship can be repaired.
How difficult is it to switch managed IT providers?
The difficulty depends on the size and complexity of the environment and the quality of existing documentation. A planned transition addresses administrative access, Microsoft 365, networks, servers, backups, cybersecurity tools, vendors, licensing, documentation, and employee support before responsibility fully transfers.
Should our current MSP provide passwords and documentation?
Review the service agreement to determine contractual requirements and ownership. Company-owned accounts, administrative access, configurations, and necessary technical information should be identified and transferred using appropriate security procedures.
Can we change MSPs before our contract expires?
That depends on the agreement. Review termination terms, notice requirements, renewal dates, transition responsibilities, licensing commitments, and applicable fees before choosing a transition date.
How long does onboarding with a new MSP take?
There is no single timeframe that applies to every business. A 25-person cloud-based company has a different environment from a 125-person organization with multiple locations, servers, specialized applications, and extensive network infrastructure. The incoming MSP should provide an onboarding plan based on the actual environment.
About AT-NET
AT-NET provides managed IT, cybersecurity, infrastructure, cloud, backup and disaster recovery, and strategic technology services for businesses throughout North Carolina, South Carolina, Florida, and Eastern Tennessee.
AT-NET has served businesses since 1999. Managed IT clients receive an internally staffed 24/7/365 help desk with less than 60-second response, access to 20+ engineers, a dedicated Technical Alignment Manager, and a dedicated vCIO.
Considering a Change in IT Providers?
AT-NET can review your current support model, technology environment, cybersecurity responsibilities, infrastructure, documentation, and future technology requirements.
The assessment can help identify the specific gaps in your current IT relationship and give you a clearer basis for deciding what your business needs from its next provider.
