The riskiest moment in any managed services relationship is the beginning. Knowledge sits in people's heads, documentation is incomplete and the outgoing team is busy. A rushed handover can mean the first major incident lands on a team that has never seen the system.
This guide explains an MSP onboarding process that avoids big-bang risk.
The riskiest moment in any managed services relationship is the beginning.
Why do MSP transitions fail?
- Handover compressed into days to save cost
- Undocumented systems and tribal knowledge
- Access and tooling not ready on day one
- No period of supervised operation before cutover
- Unclear responsibilities between client, outgoing and incoming teams
The five-phase MSP onboarding plan
Phase 1: Discovery and assessment
Inventory environments, accounts, applications, dependencies, monitoring, backups, security controls and known issues. Identify risks and constraints.
Exit criteria: complete inventory, risk register, agreed scope.
Phase 2: Planning and setup
Set up access with least privilege, connect monitoring and alerting, establish ticketing and escalation paths, and draft runbooks. Agree a RACI and communication plan.
Exit criteria: access working, monitoring live, runbooks drafted, escalation matrix agreed.
Phase 3: Knowledge transfer
Structured sessions with your engineers on architecture, deployment processes, recurring issues and business-critical periods. Record sessions and update documentation.
Exit criteria: documented architecture, validated runbooks, sign-off from system owners.
Phase 4: Shadowing and parallel operations
The MSP works alongside your team: first shadowing, then leading with your team observing. Incidents and changes are handled jointly.
Exit criteria: MSP has handled real incidents and changes successfully; client confident.
Phase 5: Full cutover and go-live
The MSP takes full operational responsibility under the agreed SLAs. Hypercare, with extra attention and daily check-ins, continues for the first weeks.
Exit criteria: SLAs met through hypercare, first monthly service review held.
Who does what during onboarding?
| Activity | Client | MSP |
|---|---|---|
| Provide access and context | Responsible | Consulted |
| Inventory and assessment | Consulted | Responsible |
| Runbook creation | Reviews | Responsible |
| Knowledge transfer sessions | Responsible (presenters) | Responsible (learners) |
| Parallel operations | Shared | Shared |
| Go/no-go decision | Accountable | Recommends |
How long does MSP onboarding take?
For most environments, four to twelve weeks, depending on size, number of clouds and documentation quality. Complex, multi-cloud estates with many legacy systems take longer. Resist pressure to shorten shadowing and parallel operations; that is where risk is removed.
What should you prepare as the client?
- Architecture diagrams, even rough ones
- List of critical systems and business calendar (peak seasons, month-end)
- Known issues and workarounds
- Contacts for vendors and third parties
- Access approvals and security requirements
- Time from your engineers for knowledge transfer
How Crozaint onboards clients
Crozaint's onboarding follows five phases: Discovery & Assessment, Planning & Setup, Knowledge Transfer, Shadowing & Parallel Operations, and Full Cutover & Go-Live. We run alongside your team before taking full responsibility, so there is no big-bang risk.
Once live, our ITIL-based service model, escalation matrix and SLAs (30-minute response for P1 and P2) apply across all eight service disciplines. The same approach underpins our observability engagements, which run parallel migrations instead of forced rip-outs.
Common mistakes to avoid
- Skipping parallel operations to hit a date
- Starting before access and monitoring are ready
- No exit criteria for each phase
- Releasing the outgoing team before knowledge transfer is complete
- No hypercare after go-live
Conclusion
A good MSP relationship starts with a careful transition. Assess, prepare, transfer knowledge, run in parallel and only then cut over.
Planning a transition? Tell us what you're running in a 30-minute call with Crozaint.
