Your First 90 Days With an MSP: What Good Onboarding Looks Like

Agree what onboarding is meant to achieve

Signing a service agreement is not the same as completing a handover. The provider needs to understand your systems and the business needs to understand the service. Agree the scope, contacts, access arrangements and priorities before making broad changes.

The stages below are an example roadmap, not a promise that every environment will be fully remediated in 90 days. A complex handover or legacy application may require a different schedule.

Stage one: establish safe ownership

Identify the person who approves changes and spending. Record urgent support channels and how incidents are escalated. Agree how the outgoing provider, internal staff and new partner will coordinate access.

Create an inventory of users, devices, critical applications, domains, connectivity and suppliers. Record who owns each account and contract. Credentials should be transferred through an approved secure method, not copied into a shared spreadsheet.

Stage two: understand and prioritise the gaps

Ask for a findings register with business impact and proposed actions. Separate an urgent exposure from a routine improvement and a future project. Confirm what is included in onboarding and what needs a separate quote.

For each priority, record an owner, dependencies, approval and completion evidence. If backups are a concern, a useful outcome is an agreed coverage sheet and test result, rather than simply a new product name.

Stage three: make the daily service predictable

• Confirm how staff submit requests and what information helps.
• Test the starter, leaver and access-change processes.
• Check who follows up failed updates, protection alerts and backup jobs.
• Agree the reporting and management meeting format.
• Establish where maintained documentation is stored.

Stage four: prove the handover works

Select practical acceptance checks. Can staff reach support? Can authorised business representatives retrieve their account information? Can the provider show which devices are covered? Is an important recovery scenario understood?

Keep unresolved work visible. An onboarding report should distinguish completed actions from accepted exceptions and future projects, so a green status does not conceal unfinished tasks.

Make the first review useful

Review service experience, repeated faults and the next quarter's priorities. Ask whether proposed purchases solve a documented need. Keep spending decisions tied to the business plan.

Our managed IT services can be scoped around these responsibilities. For account continuity, also read the IT ownership checklist in this new article series.