Generic MSP Onboarding Checklist: What Any Provider Should Document
A managed IT onboarding checklist covering discovery, documentation, tooling, security baselines, and handover.
/ Guide map
Checks when changing IT providers
What should MSPs document before escalation support starts?
Best for
Businesses preparing to onboard a managed IT provider
Decision support
Direct answer
A proper MSP onboarding should document the environment before active management begins. That includes users, devices, servers, network equipment, cloud tenants, licenses, backups, security policies, admin access, known risks, and escalation paths.
Discovery
Inventory users, devices, servers, network equipment, SaaS platforms, cloud tenants, and vendors.
Security baseline
Confirm MFA, admin accounts, endpoint protection, patching, backups, email security, and conditional access.
Tooling deployment
Roll out RMM, EDR, backup agents, ticketing, documentation, and monitoring alerts.
Runbook creation
Document onboarding, offboarding, incident escalation, backup restore, and vendor procedures.
Handover
Review support channels, response targets, reporting cadence, emergency contacts, and first-month priorities.
Checks when changing IT providers
Agree the handover checks with both providers before removing access or cancelling services. Record who owns support, monitoring and recovery throughout the transition.
| Check | What to agree |
|---|---|
| Ownership | Identify who controls domains, DNS, tenants, licences, billing, backup repositories and documentation. Use approved channels to transfer access. |
| Service continuity | Confirm when incoming support and monitoring become active. Plan how overlapping agents and subscriptions will be handled, including responsibility for alerts, backups and open incidents. |
| Acceptance | Test agreed sign-in, critical applications, support contacts, alert routing and recovery checks. Record outstanding issues and the person approving the handover. |
| Closeout | Approve removal of outgoing access and tooling, reconcile subscriptions and rotate affected credentials where needed. Retain the handover record. |
What should MSPs document before escalation support starts?
- Ticket categories BPro Technologies can handle
- Escalation boundaries and approval rules
- PSA, RMM, tenant, and documentation access requirements
- Client communication rules and approval paths
- Handover notes, evidence expectations, and quality checks
Set after discovery, access checks and any provider handover; complexity and dependencies affect the schedule.
Every managed device and service accounted for
Known risks tracked from the start
/ Choose the next step
Move from guidance to a practical review path.
Pick the route that best matches the operational question behind this resource so the next conversation starts with the right scope.
Assessment path
Review support, monitoring, or ownership gaps
Use the free assessment when the issue involves helpdesk flow, documentation, Microsoft 365, Google Workspace, recurring support issues, vendor handoffs, or backup visibility.
Service path
Compare managed and co-managed support paths
See how BPro Technologies structures managed IT, co-managed escalation support, onboarding, reporting, and recurring operational ownership.
Team path
Share the support requirement
If you already know the problem area, send the users, tools, urgency, and support model question so the team can review the next step.
Questions buyers ask
Should onboarding be billed separately?
Sometimes. If the environment needs heavy cleanup, a migration, or broad tool deployment, onboarding is usually quoted as a separate fixed-scope project rather than absorbed into the monthly fee. That is reasonable, provided the scope is written down before work begins. What is not reasonable is discovering the charge mid-onboarding, so ask what triggers a separate onboarding fee during the quote stage.
Explore the service behind this guide
Review the delivery scope, responsibilities and assessment path before choosing your next step.