We get a lot of questions from companies who are working with MSPs that they feel are not driving value. But the question always comes up: what does a company need to do before they give notice?
Building on my post last week that, in part, covered warning signs of a bad MSP relationship, there are a few things you should consider prior to separating from your MSP:
• Ensure that you have communicated your frustrations to them. Most people have taken this step but I hope that the business owners care enough to try and pivot to take their clients’ opinions into account. But barring that…
• Make sure you have documented your issues with their performance well. This will come in handy as leverage, should you need it.
• Read through your contract to make sure you understand any potential financial penalties you may face for early termination. Often, you can leverage non-performance to avoid these.
• Ensure you understand your claim to ownership of the infrastructure you get through your MSP and whether you have admin-level access to that infrastructure. We have seen some MSPs refuse to transfer or even provide access to critical infrastructure. This must be a significant strategic consideration before making a hasty move.
• Ensure you have a list of all the apps they manage for you so you can at least take stock of where they have administrative access. Most importantly, make sure you have administrative access to those tools as well.
Once you do give your notice, try to secure their commitment for an orderly transfer. Often times, if you are unhappy, chances are they might be too. Making a clean break is in everyone’s interest. In fact, your new MSP can even help you navigate some of these waters. They have likely been through this scenario before.
