The 90-Day Cliff Nobody Survives Unscathed
A quarter of MSP client relationships end within 90 days. Not because the technology failed. Because the handoff failed. Cloudtango’s research confirms what industry veterans already knew: onboarding is where managed services engagements live or die.
The failure mode follows a pattern. Scoping documents describe an environment. Reality contains surprises. Discovery reveals systems nobody mentioned. Timelines compress. Shortcuts emerge. Three months later, both parties question whether the relationship can recover.
The businesses that avoid this cliff share a common trait: they treat onboarding as an internal project, not something the MSP manages alone.
Shadow IT: The 30% Surprise
During onboarding discovery, MSPs typically find 30-40% more applications than clients disclosed. The gap isn’t dishonesty. It’s invisibility. Departmental software purchases, free-tier SaaS tools, browser extensions with data access: none of these appear in IT inventories because IT never knew they existed.
Each undisclosed application creates risk during transition. The marketing team’s scheduling tool might integrate with the CRM. Nobody mentioned it. The MSP migrates the CRM. The scheduling tool breaks. Marketing calls leadership. Leadership calls the MSP. The relationship absorbs damage that proper discovery would have prevented.
| Discovery Phase | Client Responsibility | MSP Responsibility |
|---|---|---|
| Network scanning | Provide access and credentials | Execute scan and document |
| Application inventory | Identify department stakeholders | Interview and catalog |
| Shadow IT discovery | Enforce honest disclosure | Provide structured questionnaires |
| Data flow mapping | Explain business processes | Document technical dependencies |
| Exception documentation | Disclose known workarounds | Capture tribal knowledge |
Access Gaps That Outlast the Transition
Onboarding requires credentials. Domain admin. Cloud console access. Firewall management. Vendor portals. The list extends further than anyone anticipates.
The common failure: incomplete handoff. The departing IT person held credentials in a personal password manager. The vendor portal login uses a former employee’s email. The firewall appliance still authenticates against the previous MSP’s systems.
Access gaps discovered during onboarding delay stabilization. Access gaps discovered during incidents cause outages. The difference between discovering a missing credential at 10 AM on a Tuesday versus 2 AM during a security incident spans orders of magnitude in impact.
Successful onboarding includes credential audits. Every system gets tested. Every login gets verified. Every vendor relationship gets confirmed. The investment in thoroughness prevents the crisis that discovers gaps through failure.
The Documentation Decay Curve
Average time to documentation stability after MSP engagement: three to six months. During this window, critical knowledge exists in three states simultaneously: old documentation (often wrong), new documentation (incomplete), and staff memory (unreliable).
Risk isn’t abstract. A runbook written for the previous environment doesn’t work in the new one. The MSP technician follows documented steps. The steps fail. Escalation begins. Resolution requires finding someone who remembers what the documentation forgot to capture.
Documentation debt compounds. The shortcuts taken during transition become permanent holes. Six months in, everyone assumes documentation exists because someone should have created it. Nobody verifies. Two years later, the tribal knowledge holder leaves. The organization discovers what was never written down.
Timing Risks That Compound Failures
Onboarding timing interacts with business cycles. Starting a managed services transition in Q4 when retail clients face peak demand creates predictable stress. Launching during fiscal year-end when finance locks down systems introduces unnecessary constraints.
Worse: executive attention during onboarding determines success. When leadership treats MSP transition as an IT project requiring no executive involvement, IT gets blamed for failures that originated in business decisions. When leadership engages, cross-departmental cooperation improves.
The 90-day window should avoid:
Major product launches or campaigns. Business focus will be elsewhere.
Fiscal year transitions. Access and budget disruptions complicate handoffs.
Key personnel departures. Tribal knowledge exits with people.
Major system implementations. Too many moving parts creates diagnostic confusion.
The Parallel Operation Trap
Some organizations run parallel operations during transition. The old environment stays live while the new one stabilizes. The approach sounds cautious. It’s often catastrophic.
Parallel operations double administrative burden. Every change must propagate to two environments. Every incident requires determining which environment caused it. Staff confusion about which systems to use creates data inconsistency.
Cut-over transitions feel riskier but execute cleaner. Define a migration window. Execute the migration. Support the new environment exclusively. The clean break forces resolution of issues that parallel operations allow to fester.
When parallel operation is unavoidable, limit duration. Two weeks maximum. Longer parallel windows correlate with higher ultimate transition failure rates.
Vendor Relationship Transfers
Your software vendors don’t know your MSP changed. Why would they? The support contract names your company. The licenses belong to your organization. The relationship exists between you and them.
Onboarding must address vendor relationships explicitly. The MSP needs authority to contact vendors on your behalf. Support portals need MSP credentials. Escalation contacts need updating. Renewal notices need redirecting.
Organizations that skip vendor relationship transfer during onboarding discover the gap during incidents. The MSP can’t open a support ticket because they’re not authorized on the account. The software vendor requires the account owner to add them. The account owner email belongs to someone who left two years ago.
The Onboarding Investment That Pays Forever
Successful onboarding shares one characteristic: it prioritizes completeness over speed. The pressure to declare victory early is real. Executives want confirmation that the transition succeeded. MSPs want to shift from project mode to operational mode.
Rushing that declaration guarantees deferred pain. The gaps not addressed during onboarding become incidents during operations. Each incident costs more than the onboarding time it would have required.
| Onboarding Investment | Shortcut Cost |
|---|---|
| Complete credential audit | Lock-out during incident |
| Shadow IT discovery | Integration failures post-migration |
| Documentation creation | Extended resolution times |
| Vendor relationship transfer | Support delays during outages |
| Staff introduction meetings | Bypass escalation paths |
Questions That Predict Onboarding Success
Before engaging an MSP, assess your own readiness:
Can you produce a complete inventory of production systems within 48 hours? Do you know which employees hold credentials for critical systems? Have you identified every vendor relationship requiring transfer? Can you commit executive time during the transition window? Do you have documentation of known workarounds and exceptions?
Any “no” answer identifies work required before onboarding begins. Pretending readiness invites the 90-day cliff.
Sources
- MSP client churn in first 90 days: Cloudtango MSP Reports
- Shadow IT discovery rates: Industry onboarding analysis
- Documentation stability timelines: Managed services implementation studies