trio.so
MSP

MSP Onboarding Checklist (Free Word + Excel Template)

Free MSP onboarding checklist in Word, Excel and PDF: access handover, inventory, enrollment, baseline policies, a security check and offboarding.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on

A good MSP onboarding checklist has six phases: access and discovery, inventory, enrollment, baseline policies, a security check, and handover with the first QBR. Most onboarding problems come from skipping the inventory and the baseline, so you end up managing devices you cannot name under rules nobody wrote down.

This post is for MSP owners and the lead tech who runs the project. The checklist is in order. The download has it as a Word checklist with forms and a filled-in example, an Excel tracker for every client you are onboarding, and a PDF.

Before Day One: Discovery, Contract and Access

Settle three things before you touch a device: who the client is, what you are on the hook for, and what access you have.

  • Get the signed agreement and the scope in one place. Note what is out of scope, such as line of business apps or a printer fleet you do not support.
  • Name two contacts at the client: a decision maker and a day-to-day person who can approve changes.
  • Ask for admin access to the identity provider (Microsoft Entra ID, Google Workspace or Okta), the Apple Business account if they have Apple devices, and any existing MDM. Use named admin accounts for your staff, never a shared login.
  • For Microsoft 365 clients, set up delegated access (GDAP) with the narrowest roles that cover your service. Review it at every renewal.
  • Run a short questionnaire: how many people, which devices, which apps, what regulated data they hold, who left in the last year.

Hand this over from sales to the technician in writing. Anything promised in the sales call and missing from the handoff becomes a problem in month two.

Inventory: Devices, Users, Apps and Licenses

Build one list before you change anything.

  • Devices: owner, model, serial number, operating system and version, and whether it is company owned or personal.
  • Users: pull them from the client's directory so the list matches who actually works there. Mark accounts that belong to people who have left.
  • Apps and licenses: what is installed, what is paid for, and what nobody uses.
  • Gaps: devices that are unmanaged, out of support, or sitting in a drawer.

Expect surprises. The first count rarely matches the client's own number. Tell them early, because it affects the quote.

Enrollment: Get Every Device Under Management

Enroll by platform, using the method that needs the least touch on the device.

  • Windows: Windows Autopilot for new devices, Microsoft Entra join with automatic enrollment for existing ones, or a provisioning package for a batch you image yourself.
  • macOS, iPhone and iPad: automated device enrollment through Apple Business (formerly Apple Business Manager), so devices enroll when they are first turned on. Devices bought outside the program need manual enrollment.
  • Android: Android Enterprise, either work profile for personal phones or fully managed for company devices.
  • Linux: enroll Ubuntu and Debian machines with an agent.

Most MSP onboarding checklists assume Windows. Many clients have a few Macs and a pile of phones, and those are the devices that get forgotten. Put them on the list from day one.

In trio.so's console for MSPs, each client's devices, users and policies are kept separate, so you enroll a client without mixing their fleet with another's. Directory sync from Entra ID, Google Workspace or Okta brings their users in, so you do not retype them.

Baseline Policies per Client

A baseline is the minimum every device at the client must have. Write it once, apply it to everyone, and treat exceptions as exceptions.

  • Passwords and screen lock: length, lock after inactivity, and a PIN or biometric on phones.
  • Disk encryption: BitLocker on Windows, FileVault on macOS.
  • Removable storage: decide whether USB storage is allowed, read only, or blocked.
  • Wi-Fi: push the company network profile so staff never type a password.
  • Updates: set the operating system update schedule, and how fast critical patches must land.
  • Apps: the standard set to install, and what is blocked.

Keep a baseline per client rather than one for your whole book. A dental office and a design studio do not need the same rules, and clients ask why when you treat them alike.

Security and Compliance Check

Before you call onboarding done, check what state the fleet is really in.

  • Which devices are missing patches, and which of those have known exploited vulnerabilities.
  • Which devices fail the baseline, and why.
  • Whether the client has a framework to follow, such as HIPAA, or a cyber insurance questionnaire to answer, and what evidence you will need to produce.

Record this as the starting point. When you show improvement at the first QBR, it is measured against something.

Handover and the First QBR

Close the project with a short document the client can read in five minutes: what you manage, how many devices and users, the baseline, how to reach you, and what you found. Book the first QBR before you leave the room, and bring the before and after numbers from the security check.

Update your internal documentation the same day, including credentials in your password manager and the client's entry in your PSA. Your PSA is a separate tool, and this checklist does not replace it.

Offboarding: A Client Leaves, or One of Their Employees Does

Offboarding is the part checklists skip, and it is where data leaks.

When a client leaves: agree a date in writing, export their inventory and documentation, remove your admin accounts and delegated access, unenroll managed devices cleanly, and confirm in writing that you hold no more of their data.

When a client's employee leaves: disable the account, recover or remotely wipe the device, and revoke app access. The full employee list is in our IT offboarding checklist, and the hardware side of a new hire is in the IT onboarding checklist.

Download the MSP Onboarding Checklist

The download turns this post into files you can use with each new client. The Word checklist has the 51 items in phase order with an owner, a due day, evidence and status, plus a kickoff list, a client information sheet, an access handover form with no passwords in it, and a filled-in example for a made-up dental practice. The Excel tracker holds every client you are onboarding at once.

The checklist PDF: the cover, the phase tables with owners and due days, and the access handover form
The checklist PDF: the cover, the phase tables with owners and due days, and the access handover form
  • The Word checklist (MSP-Onboarding-Checklist-trio.so.docx) has fillable fields, so you can copy it once per client.
  • The PDF (MSP-Onboarding-Checklist-trio.so.pdf) has the same checklist, forms and example, ready to print.
  • The Excel tracker (MSP-Onboarding-Tracker-trio.so.xlsx) has tabs for clients, checklist items, devices and findings. It shows each client's % complete, the earliest phase with open items, overdue items and clients with no progress in 14 days. Formulas only, no macros.
The tracker's Example tab: two made-up clients, one on track and one stalled, with their overdue items and devices
The tracker's Example tab: two made-up clients, one on track and one stalled, with their overdue items and devices

For the wider picture of running the practice, see what an MSP is and does, the MSP software stack and managed IT services. If your clients run several directories, multi tenant Active Directory explains how to keep them apart.

trio.so handles the device side of this list for MSPs: one console with each client's devices, users and policies kept separate, zero-touch enrollment with Windows Autopilot, Apple Business and Android Enterprise, Ubuntu and Debian enrollment, and the policy status of every device. Plans start at $5 per device. See how trio.so works for MSPs.

Start free trial Book a demo

14-day free trial. No credit card required.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Onboard every client in one console

trio.so keeps each client's devices, users and policies separate in one MSP console. Enroll with Windows Autopilot, Apple Business or Android Enterprise, set the baseline and check each device's policy status.

Start free trial

Get Ahead of the Curve

Every organization today needs a solution to automate time-consuming tasks and strengthen security. Without the right tools, manual processes drain resources and leave gaps in protection. trio.so is designed to solve this problem, automating key tasks, boosting security, and ensuring compliance with ease.

Don't let inefficiencies hold you back.

Every organization today needs a solution to automate time-consuming tasks and strengthen security. Without the right tools, manual processes drain resources and leave gaps in protection. trio.so is designed to solve this problem, automating key tasks, boosting security, and ensuring compliance with ease.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently asked questions

It should include access and discovery, a device and user inventory, enrollment, baseline policies, a security check, and handover with the first QBR. Add offboarding steps so the exit is planned from the start.

It depends on the number of devices and how clean the client's environment is. A small office with a clear directory can take days, while a client with unmanaged devices and old accounts takes weeks. Give the client a date after the inventory, not before.

Confirm scope and get admin access. After that, build the inventory, because every later step depends on it.

Use the lowest touch method for each platform: Windows Autopilot or Entra join, Apple Business automated enrollment, Android Enterprise, and an agent for Ubuntu and Debian Linux. Then apply the client's baseline policies.

Their legal name and sites, the number of staff, a decision maker and a day-to-day approver, the identity provider, the platforms in use, any regulated data, and admin access to their systems through named accounts. Passwords go into your password vault, never into email or the onboarding document.

It is the planned end of a client relationship, or the removal of one employee's access. For a client it means exporting records, removing your access and unenrolling devices. For an employee it means disabling accounts and recovering or wiping the device.

Unenroll them from your management so the client controls them, or hand over to the client's new provider. Remove your admin and delegated access, and confirm it in writing.

Related

From the blog

The related industry news, interviews, technologies, and resources.