MSP Onboarding Checklist: Step-by-Step List + Free Template
An MSP onboarding checklist for new clients: scope, contract, access, discovery, security, tools and the first 90 days, plus a free responsibility matrix.

An MSP onboarding checklist is the list a managed service provider works through when taking on a new client: agree scope and responsibilities, sign the contract, collect access safely, document every device and account, bring security up to a baseline, install your tools, tell users how to get help, and review the first 90 days.
Key takeaways
- Most bad MSP relationships start in onboarding: unclear scope, missing passwords, and a client who thinks “everything IT” is included.
- Write a responsibility matrix before go-live. The UK’s National Cyber Security Centre recommends one in its guidance on choosing an MSP.
- Never take credentials by email or WhatsApp. Collect them into your password manager and change them once you have control.
- Set a security baseline in the first 30 days: MFA on every admin and remote account, patching on a schedule, tested backups and logs kept long enough to investigate.
- Run onboarding as a project with owners and dates, not as a list in someone’s head.
Why an MSP client onboarding checklist matters
When you take over a client’s IT, you inherit everything the last provider (or the office manager’s nephew) left behind: unknown admin accounts, a router nobody has the password for, backups that haven’t run since 2023. A checklist makes sure you find these in week one, not during the first outage.
It also protects the relationship. CISA’s joint advisory on protecting against cyber threats to MSPs and their customers tells both sides to set out security roles and responsibilities in the contract, including who handles hardening, detection, response and incident notifications (checked on 1 October 2026). A clear onboarding is where that gets written down.
The complete MSP onboarding checklist
Copy this into your own system and adjust it to your service tiers.
Phase 1: Before you sign
Phase 2: Contract and admin
Phase 3: Access and credentials
Phase 4: Discovery and documentation
Phase 5: Security baseline
Phase 6: Tools and support
Phase 7: Go-live and first 90 days
Free template: responsibility matrix
Fill this in with the client before go-live. “R” is responsible for doing it; “I” is kept informed.
| Area | MSP | Client | Notes |
|---|---|---|---|
| User support (helpdesk) | R | I | Hours and channels as per contract |
| New starters and leavers | R | Tells MSP 3 working days ahead | Client approves access |
| Patching operating systems | R | I | Schedule agreed with client |
| Line-of-business app updates | I | R | Unless added to scope |
| Backups and test restores | R | I | Restore test each quarter |
| Hardware purchases | Advises | R | MSP quotes, client buys |
| Security incident response | R | Names a contact | Notification time in contract |
| Staff security awareness | Advises | R | |
| Domain and DNS renewals | R | Pays |
For your new client’s own staff joining later, our information technology onboarding checklist covers the per-person setup.
Worked example: onboarding a 15-person accounting firm in Lagos
Illustrative figures. A firm with 15 staff, one office, 16 laptops, one file server, a firewall and cloud email signs a monthly managed services contract.
| Week | What happens | Hours planned |
|---|---|---|
| Week 1 | Contract signed, access collected, MFA on admin accounts | 6 |
| Week 2 | Asset list and network map, old provider’s remote tool removed | 10 |
| Week 3 | Monitoring agent on 16 laptops and the server, backups fixed and test restore | 12 |
| Week 4 | Patching schedule live, user kickoff, help note sent | 4 |
| Total | 32 |
Discovery finds three admin accounts belonging to people who have left, and a server backup that last finished four months ago. Both go in the day-30 review as fixed items. If the firm pays a one-off onboarding fee to cover the 32 hours, the provider can set it from its own hourly rate; at an illustrative ₦25,000 an hour, that’s 32 × ₦25,000 = ₦800,000.
Common mistakes
- No onboarding fee. Onboarding is the heaviest month of work. Many MSPs charge it separately so the first monthly fee isn’t swallowed.
- Starting work before access is complete. You end up fixing things you can’t see.
- Letting “everything IT” stand. Without the out-of-scope list, every printer and phone becomes your problem.
- Skipping the test restore. A backup job that says “success” is not a working backup.
- Keeping documentation in one technician’s head. If they’re on leave, so is the client’s history.
Run your MSP onboarding in startbuddi
startbuddi isn’t a remote monitoring or ticketing tool, so keep your monitoring and remote access stack. Where it helps is the business side of onboarding: the client record, the project, the paperwork and the billing.
- Add the client. In Customers, create the company and its contacts, with the decision-maker named. Messages from the client’s email, WhatsApp or website chat land in the Inbox on their record.
- Send the paperwork. In Documents, send your proposal and contract for e-signature and keep both linked to the client.
- Turn the checklist into a project. In Work, start a project for the client (the Client delivery template is a good base), add each phase as a milestone and each checklist item as a task with an owner and due date.
- Log the hours. Use Time on the onboarding tasks to see whether your onboarding fee covered the work.
- Share progress. Create a client portal so the client sees agreed items and approvals without chasing you. Live portals are on paid plans; see the pricing page.
- Bill the service. Invoice the onboarding fee from Money Manager, and set the monthly fee up as a subscription plan or recurring invoice; recurring invoice drafts are created for you automatically.

For how startbuddi fits an IT business day to day, see startbuddi for IT teams and CRM for IT companies. The broader client onboarding process guide covers the relationship side, and our generic client onboarding checklist is a lighter version for non-IT services.
Turn this checklist into tasks
Copy the checklist into your next onboarding, then run it as a project with owners and dates. Start startbuddi free to keep each client’s record, contract, onboarding project and invoices in one place.
Frequently asked questions
What should an MSP onboarding checklist include?
It should cover scope and contract, a responsibility matrix, collecting access safely, documenting assets and accounts, a security baseline (MFA, patching, backups, logging), installing your tools, telling users how to get help, and reviews at 30, 60 and 90 days. Keep it as tasks with owners so nothing is left to memory.
How long does MSP client onboarding take?
For a small office of 10 to 25 users on one site, two to six weeks is common, depending on how good the existing documentation is and how quickly the client gives access. Larger or multi-site clients take longer. Set a go-live date in the contract so both sides plan for it.
Should MSPs charge an onboarding fee?
Many do, because the first month carries discovery, documentation, fixes and tool rollout that the monthly fee isn't priced for. Base the fee on the hours you expect, and show the client what the onboarding delivers.
How should an MSP collect client passwords?
Never by email, text or chat. Use a password manager or a secure sharing link, create named accounts for each technician, turn on MFA and change passwords the previous provider knew once you have control.
What is the first thing to do when onboarding a new MSP client?
Get the scope and responsibilities agreed in writing, then secure admin access to email, domain, DNS and the firewall. Everything else depends on knowing what you're responsible for and being able to reach the systems.
Omolola Akiyode is the operations and project manager at startbuddi, leading cross-functional projects and the content that helps founders get set up. Omolola writes about projects, websites and getting found online, and turns complex ideas into clear, practical steps.
Runs operations and projects at startbuddi




