MSP client onboarding checklist: from signed agreement to steady service

An MSP client onboarding checklist is a list of steps a managed service provider follows between a signed agreement and normal day-to-day support. The first weeks set the tone for the whole relationship. If access is missing, staff do not know how to ask for help or a backup turns out not to work, the client starts to doubt the decision they just made. A written checklist makes onboarding the same for every client, whoever on your team runs it.

This checklist is for MSPs taking on small and mid-sized businesses, roughly 10–50 staff, in the UK and the US. It has six stages, each with its own short list.

What are the stages of MSP client onboarding?

MSP client onboarding checklist: six stagesProcess flow of MSP client onboarding: kickoff, handover from the old provider, access and documentation, security baseline, staff introduction, and a first review shown as a branch from the staff stage. No figures.Kickoffplan, contactsand datesHandoverfrom the oldproviderAccessinventory andadmin accessBaselinesign-in, devices,backupsStaffhow to gethelpFirst reviewend of monthor quarter
You cannot secure systems you cannot see yet: document first, then set the baseline.
Stage Goal Done when
1. Kickoff Agree plan, contacts and dates Plan sent and accepted
2. Handover Get what the old provider holds Credentials and documents received
3. Access and documentation Know and control the estate Inventory and admin access recorded
4. Security baseline Close the most important gaps Agreed baseline in place
5. Staff introduction Everyone knows how to get help Staff briefed; first tickets handled
6. First review Check expectations Review held; actions agreed

The stages overlap in practice, but the order matters: you cannot set a security baseline on systems you cannot yet see.

1. How do you run the kickoff?

Hold a short call with the owner and the person who will be your day-to-day contact. Use the proposal as the agenda, so nothing promised in the sale gets lost. Our proposal template for MSPs shows the sections to carry over.

Kickoff checklist

  • Day-to-day contact and a backup contact named
  • Who can approve changes and purchases agreed
  • Start date for support confirmed
  • Onboarding plan with rough dates shared
  • Known problems and urgent issues listed
  • First projects from the proposal confirmed in order

2. How do you handle the handover from the old provider?

If the client had another IT provider, you need what they hold: admin credentials, documentation, licence details and anything they manage on the client’s behalf. Ask the client to request it, because it is their data. Keep the tone neutral.

Example figures

Handover request wording (for the client to send)

"We have appointed a new IT provider from [date]. Please send the following to [contact] by [date]: admin access for all systems you manage, current documentation and network details, licence and subscription information, and any open issues. Thank you for your support."

Expect gaps. List what is missing and agree with the owner how to recover it, for example password resets on accounts the business owns.

3. What should you document about the client’s IT?

Build the inventory before you change anything. It is the base for support, pricing checks and the security baseline.

Access and documentation checklist

  • Users and their roles listed
  • Devices listed: laptops, desktops, phones, servers, network kit
  • Business accounts and services listed, with who owns each
  • Admin access moved into your password vault
  • Licences and renewal dates recorded
  • Network layout and internet provider details recorded
  • Website and domain hosting accounts identified, with owner
  • Software the business depends on identified

The NCSC’s guide for small organisations lists the kind of accounts to check, including "banking and finance accounts", "HR and payroll systems", "online storage" and "your company website (and domain hosting if that is a separate account)". See Secure your important online accounts.

4. Which security basics should you set first?

Agree a baseline with the owner and put it in writing. Official guidance gives you neutral wording to explain it.

  • Sign-in to important accounts. The NCSC says: "Protecting how users sign in to these accounts is one of the most effective ways to reduce the risk of compromise." It adds: "Where passkeys are available, you should enable them for business‑critical accounts as a priority." Where passkeys are not available, it recommends "a strong password and 2‑step verification (2SV)".
  • Devices. The NCSC says "it’s important to lock down access to all devices, including any personal devices that your staff use for work purposes". See Protecting your devices.
  • Backups. The NCSC says "you should make a copy (also known as a backup) of all the data that your business needs to operate", including "your website, emails, invoicing, documents, presentations, contacts and customer information". See Backing up your data. Test a restore during onboarding; a backup nobody has restored is an assumption.

For UK clients, the five technical controls of Cyber Essentials (firewalls, secure configuration, security update management, user access control and malware protection) make a clear structure for the baseline. Offer to help them prepare if they want certification, and never promise that they will pass.

5. How do you introduce yourself to staff?

Staff judge a new provider by their first support request. Send a short note, ideally from the owner, with:

  • how to ask for help (phone, email or portal) and your hours
  • what to expect in the first weeks, such as device checks or new sign-in steps
  • who to contact if something is urgent

Then make the first few tickets fast and friendly. That is when trust is built.

Keep the language plain. Staff do not need to know about your tools. They need to know who to call, what will change on their laptop and why. If a new sign-in step is coming, tell them a few days before, and offer a short call for anyone who gets stuck.

6. When should you hold the first review?

Book it at the end of the first month or first quarter, before onboarding starts. Cover what was done, what is still open, ticket themes so far and whether the service matches what was promised. Our client retention checklist covers reviews after that.

If the review shows the client needs more work than the fee covers, check the count of users and devices against the agreement; our guide to MSP pricing models explains true-ups.

What does a typical onboarding plan look like?

A short plan, shared at kickoff, tells the owner what happens and when. Adjust the timing to the size of the client; the order stays the same.

Period Main work What the client sees
First days Kickoff, handover request, admin access One named contact and a plan
First week Inventory, documentation, backup check Questions from your team, few changes
Following weeks Security baseline, device enrolment, first projects Planned changes, announced in advance
End of first month Staff introduction complete, first review held A summary of what was done and what is next

Which onboarding problems come up most often?

  • Missing credentials. The old provider is slow, or nobody knows who set up an account. Agree with the owner which accounts the business owns and recover access through the account provider.
  • Hidden devices and services. A laptop at home, a forgotten cloud account, a website managed by a relative of the owner. Ask staff directly; a short questionnaire helps.
  • Change fatigue. New sign-in steps and device checks in the same week annoy staff. Spread changes out and explain each one.
  • Scope creep. Requests that fall outside the agreement arrive early. Log them, handle the urgent ones and raise the rest at the first review.

Where does Arbyn Partners fit?

Arbyn Partners books meetings for B2B firms in the UK and the US, including MSPs, with business owners or decision-makers who have a real need, not a competitor or an existing client of yours. We fill your diary with first calls; onboarding and the service are yours. You pay only for qualified meetings that take place: £150 in the UK and $200 in the US. The first qualified meeting is free, one per company, and there is no retainer. See our page on lead generation for MSPs and the steps before onboarding in our MSP sales process.

More about Arbyn Partners is on our homepage.

FAQ

What is an MSP client onboarding checklist?

A list of steps from signed agreement to normal support: kickoff, handover from the old provider, access and documentation, security baseline, staff introduction and first review.

What should an MSP get from the previous IT provider?

Admin access to the systems they manage, documentation and network details, licence information and open issues. Ask the client to request it, because it is their data.

Which security basics should come first for a new client?

Official NCSC guidance for small organisations covers sign-in to important accounts (passkeys, or strong passwords with 2-step verification), locking down devices, and backups of the data the business needs.

Should you test backups during onboarding?

Yes. Restore a sample during onboarding, so you know the backup works before you need it.

When should the first review with a new client happen?

At the end of the first month or quarter. Book it at kickoff, before onboarding starts.

Does Arbyn Partners help MSPs win new clients?

We book qualified first meetings with owners or decision-makers who have a real need. You pay £150 in the UK or $200 in the US per qualified meeting held, and the first one is free.