The Four Lock-In Mechanisms
MSPs don't want you to leave. They want you to stay — paying monthly fees forever. To achieve this, they use four lock-in mechanisms:
- Proprietary tools that only they support
- Knowledge hoarding that makes you dependent on their staff
- Long-term contracts with exit penalties
- Migration complexity that makes switching painful
Lock-In #1: Proprietary Tools
Many MSPs use proprietary tools for: - Remote monitoring and management (RMM) - Documentation - Password management - Backup and recovery - Ticketing
These tools are designed to lock you in. If you leave the MSP, you can't take the tools with you. You lose all the data, configurations, and documentation stored in them.
How to Protect Yourself
Before signing: - Insist on standard tools (ConnectWise, Datto, IT Glue) that you can take with you or that another MSP can support - Ask: "If we leave, can we export all our data?" - Include data portability clauses in the contract
During the relationship: - Maintain your own documentation outside the MSP's tools - Keep copies of all configurations, passwords, and network diagrams - Don't rely solely on the MSP's proprietary systems
Lock-In #2: Knowledge Hoarding
MSPs hoard knowledge in two ways:
1. Tribal knowledge. Only certain staff know how your environment works. When they leave (or are made redundant), that knowledge walks out the door.
2. Documentation hoarding. The MSP has all the documentation. You don't. If you try to leave, you discover that you don't know your own environment.
How to Protect Yourself
Before signing: - Require comprehensive documentation as a deliverable - Include documentation standards in the contract - Require knowledge transfer sessions
During the relationship: - Maintain your own documentation (don't rely on the MSP) - Attend knowledge transfer sessions - Build internal expertise (don't let the MSP be the only ones who know your environment)
Lock-In #3: Long-Term Contracts
MSP contracts typically run 1-5 years. The longer the contract, the harder it is to leave.
Common Contract Traps
1. Auto-renewal clauses. The contract automatically renews unless you give notice 60-90 days before the end date. If you miss the notice window, you're locked in for another year.
2. Exit penalties. Some contracts charge penalties for early termination. These can be 2-3 months of fees.
3. Minimum commitment. Some contracts require minimum monthly spend. If you reduce services, you still pay the minimum.
4. Technology lock-in. The contract specifies proprietary technology that only the MSP supports. Leaving means replacing the technology.
How to Protect Yourself
Before signing: - Negotiate shorter contracts (12 months maximum) - Remove or reduce exit penalties - Include step-down clauses (reduce services without penalty) - Require 30-day termination notice (not 90)
During the relationship: - Calendar the auto-renewal notice date - Negotiate extensions well in advance - Start evaluating alternatives 6 months before contract end
Lock-In #4: Migration Complexity
Switching MSPs is painful. The process typically involves:
- Data migration (moving documentation, configurations, passwords)
- Tool migration (replacing RMM, PSA, backup tools)
- Knowledge transfer (learning the environment from scratch)
- Service disruption (there will be gaps during the transition)
- Risk (things can break during migration)
MSPs know this. They make migration deliberately complex to discourage you from leaving.
How to Protect Yourself
Before signing: - Include migration support in the contract (the MSP must assist with transition) - Require documentation in standard formats (not proprietary) - Include a transition period (the old MSP must support the new MSP during migration)
During the relationship: - Maintain internal documentation - Build internal expertise - Test migration procedures periodically
The Client Lock-In Scorecard
| Lock-In Mechanism | How to Detect | How to Protect |
|---|---|---|
| Proprietary tools | Ask: "What tools do you use?" | Insist on standard tools |
| Knowledge hoarding | Ask: "Can we see the documentation?" | Require documentation as deliverable |
| Long-term contracts | Read the fine print | Negotiate shorter terms |
| Migration complexity | Ask: "What happens if we leave?" | Include migration support in contract |
The Exit Strategy
If you're locked into an MSP and want to leave, here's the playbook:
1. Review Your Contract
- What's the notice period?
- Are there exit penalties?
- Who owns the data?
- What documentation is available?
2. Start Building Internal Knowledge
- Document everything the MSP knows about your environment
- Attend knowledge transfer sessions
- Build relationships with the MSP's technical staff (they may leave too)
3. Evaluate Alternatives
- Get quotes from 3-4 other MSPs
- Ask about migration support
- Check references from similar clients
4. Negotiate Your Exit
- Give proper notice (don't burn bridges)
- Negotiate migration support
- Ensure all data and documentation is transferred
- Get written confirmation that all access has been revoked
5. Plan for Disruption
- Expect 2-4 weeks of reduced service during migration
- Have internal resources available to support the transition
- Communicate with stakeholders about the change
The Bottom Line
MSP lock-in is real. Proprietary tools, knowledge hoarding, long-term contracts, and migration complexity all make it hard to leave.
The best defence is prevention. Negotiate contract terms before you sign. Maintain your own documentation. Build internal expertise. And always have an exit strategy.
If you're already locked in, start planning your exit now. The longer you wait, the harder it gets.
Based on analysis of MSP contracts, client case studies, and industry reporting.
Was this helpful?