The 15-20% Switching Tax
Switching costs for IT managed services equal 15-20% of annual contract value. Bain & Company research quantifies what departing clients discover: leaving costs almost as much as staying for another few months. Organizations that have navigated MSP exits confirm these figures from painful experience.
The switching tax isn’t accident. It’s architecture. Lock-in mechanisms accumulate during the relationship, often invisibly, until exit reveals their full weight.
The Lock-In Taxonomy
Lock-in operates through multiple mechanisms, often simultaneously:
| Lock-In Type | Mechanism | Exit Cost | Mitigation Difficulty |
|---|---|---|---|
| Contractual | Termination clauses, penalties | Direct financial | Negotiable at signing |
| Technical | Proprietary tools, formats | Migration effort | Architecture dependent |
| Operational | Process dependency, tribal knowledge | Transition duration | Gradual |
| Relationship | Personal connections, trust | Search cost | Natural |
Each type reinforces others. Technical lock-in extends contract lock-in because migration takes time. Operational lock-in makes technical migration harder because procedures are intertwined.
Proprietary Tooling: The Invisible Prison
MSPs deploy their preferred tools: RMM agents, PSA systems, documentation platforms. Each tool creates dependency.
RMM (Remote Monitoring and Management). The agent on every endpoint reports to MSP infrastructure. Removing it requires touching every device.
PSA (Professional Services Automation). Ticket history, configuration data, and operational records live in MSP systems. Export may be partial or impossible.
Documentation platforms. Runbooks and procedures in MSP-controlled systems. Departure means recreating or losing operational knowledge.
Custom scripts. Automation developed during engagement may be claimed as MSP intellectual property. You can’t take it. You must rebuild it.
Unwinding proprietary tooling creates technical debt that takes 3-6 months to resolve. During that window, both old and new tools must function. Neither works optimally.
The Missing Exit Clause: 85% Unprepared
Exit readiness clauses are absent in 85% of standard MSP contracts. The clauses that protect your exit interests simply don’t exist in template agreements.
Missing provisions typically include:
Data export format specifications. What format will you receive data in? Is it machine-readable? Standard?
Transition assistance obligations. Is the outgoing MSP required to cooperate with the incoming MSP?
Knowledge transfer timelines. How long will outgoing MSP staff be available for questions?
Tool removal procedures. How will proprietary agents be removed? By whom?
Final audit rights. Can you verify that all data was transferred and no copies retained?
Negotiating these provisions before signing costs nothing. Negotiating after announcing departure costs leverage.
The Technical Debt Accumulation Pattern
Lock-in deepens over time. Year one looks manageable. Year three feels permanent.
| Engagement Year | Typical Lock-In Depth | Exit Complexity |
|---|---|---|
| Year 1 | Tools deployed, basic integration | Moderate |
| Year 2 | Custom configurations, workflow embedding | High |
| Year 3+ | Deep integration, institutional dependence | Very High |
Pattern explains why three-year contracts favor MSPs. By year three, exit seems impossible. Renewal happens by default.
Organizations that maintain exit readiness throughout the relationship preserve options. Those that defer exit planning discover costs compounded.
The Parallel Operation Cost
Leaving an MSP typically requires parallel operation. Old MSP continues support while new MSP onboards. You pay twice.
The parallel period exists because:
Knowledge transfer takes time. New MSP must learn your environment.
Tool migration isn’t instant. Removing old tools while deploying new ones requires coordination.
Risk mitigation demands overlap. Running without support during transition is unacceptable.
Parallel period typically runs 30-90 days. Budget accordingly. The cost belongs in exit planning, not as a surprise.
Contract Structures That Enable Lock-In
Certain contract structures systematically favor MSP retention:
Auto-renewal with short notice windows. Miss the 60-day notice window, you’re locked in another year.
Volume discounts with clawback. Leave before term completion, discount reverses as penalty.
Bundled services. Can’t exit one service without exiting all. Partial transition becomes impossible.
Escalating termination fees. Early termination costs more than later termination, but the contract renews before “later” arrives.
Intellectual property claims. Any customization becomes MSP property. Leaving means losing it.
Read contracts assuming you will eventually leave. Because you will.
Building Exit Readiness
Organizations that preserve exit options share practices:
Independent documentation. Maintain your own copies of network diagrams, configurations, and procedures. Don’t rely solely on MSP documentation.
Regular data exports. Periodically export data from MSP systems in standard formats. Verify usability.
Staff cross-training. Internal IT should understand enough to evaluate new MSPs and participate in transition.
Contract review before renewal. Each renewal is opportunity to improve exit provisions.
Relationship diversification. Avoid single-vendor for all IT services. Partial dependencies are easier to exit than total dependencies.
The Leverage Window
Leverage for negotiating exit terms exists at two moments:
Before initial signing. MSP wants your business. Terms are negotiable.
Before renewal signing. MSP wants to retain your business. Terms are renegotiable.
Between these moments, leverage is minimal. The MSP has you under contract. Exit terms are fixed. Improvement requires waiting for renewal window.
Use renewal windows strategically. Three months before renewal, assess exit readiness. Identify gaps. Negotiate improvements. If negotiation fails, that’s the time to evaluate alternatives, not after signing.
The Hidden Switching Costs
Beyond direct fees, switching costs include:
Productivity loss. Staff learning new systems, new procedures, new relationships.
Elevated incident rates. New MSP learning curve creates temporary degradation.
Delayed projects. IT focus on transition prevents other initiatives.
Vendor coordination. Other vendors must coordinate with new MSP. Relationship rebuilding required.
Customer impact. Subtle degradation during transition affects customer experience.
The 15-20% figure captures direct costs. Total switching cost, including hidden impacts, may double that estimate.
Measuring Lock-In Exposure
Periodic assessment reveals lock-in depth:
Data export test. Can you export all critical data in standard formats today?
Tool removal test. Do you know what removing MSP tools would require?
Knowledge test. Could internal staff explain your environment to a new MSP?
Contract test. What would termination cost right now?
Timeline test. How long would transition to a new MSP take?
If any answer is “I don’t know,” you have lock-in exposure you haven’t quantified. Quantify before you need to act.
Sources
- Switching cost percentage: Bain & Company
- Exit clause absence rate: MSP contract analysis
- Technical debt timelines: Managed services transition research