Almost everything written about the MSP onboarding process is written for the provider: checklists for their technicians, templates for their welcome kits. Very little is written for you, the business that just signed, wondering what happens next and how to tell whether it is going well.
This guide takes your side of the table. It walks through what a competent provider should be doing in each phase of the first 90 days, what your business will be asked to contribute, why things often feel bumpier before they feel better, and the specific red flags that separate a disciplined onboarding from an improvised one.
Why Onboarding Predicts the Whole Relationship
Onboarding is the one phase where a provider's real habits are fully visible. A provider that documents carefully, communicates on schedule, and asks detailed questions in month one will usually behave that way in year three. One that improvises through onboarding will improvise through your next outage.
This article assumes the choosing is done; if you are still comparing providers, start with how to choose the right MSP and come back. That guide handles the comparing; this one covers everything after the signature.
It also stays out of the separation side of a switch, the contracts and offboarding mechanics involved in leaving your previous provider, which is its own subject. What follows is purely the incoming side: what your new provider should build, and when.
Days 1 to 30: Discovery and Documentation
The first month should be heavy on questions and light on changes. Before anyone touches a setting, the provider needs an accurate picture of what exists, and industry write-ups consistently put this information-gathering at dozens of hours of work per client. A provider that compresses it into a one-page form is not saving you time; it is choosing to guess.
What a Real Discovery Produces
By the end of the first phase you should be able to see concrete outputs, not just meeting notes. A complete asset inventory covering computers, servers, network equipment, cloud accounts, and software licenses. A list of every application your business depends on and who uses it. A credentials record showing where administrative access lives and who holds it. And an honest risk snapshot naming the obvious gaps, an unpatched server, a backup nobody has tested, accounts belonging to people who left.
Expect at least one thorough on-site walk-through as part of this, because server closets, wiring, and printers do not document themselves remotely, whether your office is in Simi Valley or mid-Wilshire. Expect interviews too: a good discovery talks to the people who use the systems, not only the person who signed the contract.
What Your Business Needs to Bring
Onboarding is not something done to you; it needs real inputs from your side, and delays here are the most common reason timelines slip. Plan to hand over administrative credentials for systems and cloud accounts, contact information for your internet provider, phone vendor, and software vendors, domain and licensing details, and any documentation the previous provider left behind, even if it is thin.
Just as important, assign one decision maker who can answer questions within a day, approve small changes, and champion the transition internally. A provider waiting three weeks for a password or a signature cannot onboard you in ninety days, and that part of the schedule genuinely belongs to you.
Days 30 to 60: Tools, Baselines, and First Fixes
With the picture drawn, the provider starts installing its operational layer, and how they do it matters as much as what they install. Two habits separate careful installations from careless ones.
Monitoring Goes On, Carefully
The core of modern support is remote monitoring and management software: small agents on each machine that report health, apply patches, and let technicians work without driving over. A careful rollout is staged, deployed to a pilot group first and confirmed clean before covering the whole fleet. A provider that pushes agents onto every machine on day one, before understanding your environment, is showing you its habits. Alongside the agents come patching schedules, alert thresholds, and maintenance windows agreed around your working hours, so updates stop interrupting your busiest mornings.
The Security Baseline
This phase should also close the risk gaps discovery surfaced. Typical early moves include bringing operating systems and software current on patches, rolling out multifactor authentication where it is missing, removing access for departed employees, and verifying that backups both run and restore. Many providers formalize this with a structured review of the environment, the same discipline behind a dedicated cybersecurity audit, so the fixes follow findings instead of assumptions.
Quick wins belong here too. Long-standing annoyances, the printer that never worked, the shared drive nobody can reach, are usually cheap to fix once someone competent is looking, and fixing them early builds the trust the rest of the transition runs on.
Days 60 to 90: Stabilization and a Working Rhythm
The final phase turns a project into a service. Ticket flow settles as your team learns the new way to ask for help and the provider learns your environment's quirks. Processes get standardized, including the everyday ones like IT onboarding and offboarding for employees, so a new hire's first day and a departure's last day follow a checklist instead of a scramble.
Reporting starts arriving on a schedule: what was monitored, what was fixed, what is trending. And the first strategic conversation lands on the calendar, a review of where the environment stands against the service level agreement you signed and a roadmap of what should improve next quarter. If ninety days pass with no reporting and no roadmap, the relationship has stalled at the tool-installation stage.
Why It Can Feel Worse Before It Feels Better
Here is the honesty most onboarding pages skip: the first weeks often feel like a step backward, and that is usually a sign the work is real. Ticket counts rise, partly because discovery surfaces problems that were quietly ignored for years, and partly because your team finally has somewhere responsive to send them. Password resets and multifactor prompts add friction exactly when everyone wants smoothness. New request channels take a few weeks to become habit.
The difference between a healthy bump and a real problem is communication. A good provider tells you this spike is coming, reports on it while it happens, and can show it declining by the second month. Silence during the same period is not calm; it is absence.
Red Flags Worth Acting On
A few behaviors during onboarding reliably predict trouble. No discovery phase, or one so shallow it fits on a page. Tools deployed everywhere at once before anyone understood the environment. No written documentation delivered to you, which quietly recreates the dependency you just escaped from your last arrangement.
Missed check-ins without explanation. And any reluctance to tell you what they found, good or bad, in plain language.
None of these is fatal on its own, but each deserves a direct conversation early, because the patterns a provider sets in the first ninety days are the patterns you will live with. A provider worth keeping will take the directness well.
What You Should Hold in Hand at Day 90
By the end of a competent onboarding, your business should possess, in writing:
- A complete environment document: assets, applications, licenses, network layout, and credentials custody.
- Live monitoring and patching across your fleet, with maintenance windows you agreed to.
- A verified backup, meaning a restore was actually tested, not assumed.
- A security baseline summary: what was fixed, what remains, and why.
- A support routine your team actually uses, with known contacts and hours.
- A first report and a scheduled review, with a short roadmap for the next quarter.
That list doubles as a set of interview questions. Ask any provider you are evaluating to describe their onboarding against it, and the quality of the answer will tell you most of what you need to know.
Frequently Asked Questions
Most small business onboardings are structured across the first 30 to 90 days, with discovery in the first month, tooling and security baselines in the second, and stabilization in the third. Simple environments finish faster and complex or neglected ones take longer. Be cautious of any provider promising full onboarding in a few days, because the discovery work alone takes real hours if it is done at all.
Administrative credentials for systems and cloud accounts, vendor contacts for internet, phones, and key software, domain and licensing details, and whatever documentation your previous arrangement left behind. Equally important is a designated decision maker who can answer questions and approve changes quickly, since waiting on client-side inputs is the most common cause of onboarding delays.
A well-run onboarding causes very little, because disruptive work is scheduled into agreed maintenance windows rather than business hours. Expect minor friction instead: new login prompts, password resets, and a new way to request help. Any provider promising literally zero disruption is overselling; the honest promise is that disruption is planned, communicated, and kept off your busiest hours.
Two reasons, and both are usually good news. Discovery surfaces problems that were being silently tolerated, and each becomes a tracked ticket instead of an ignored complaint. And employees who had given up on asking for help start asking again once responses actually come. The spike should be visible in reporting and should decline noticeably by the second month as the backlog clears.
Documentation of your environment delivered to you, monitoring and patching live across your machines, a tested backup restore, the urgent security gaps closed, a support routine your team uses without thinking, and a first report with a scheduled review. If most of that list is missing at ninety days, raise it directly, because onboarding has stalled.
A disciplined MSP onboarding process is not a favor the provider does for you; it is the foundation everything after it stands on, and you have every right to inspect the foundation while it is being poured. If you are planning a provider switch and want to see what a documented, phase-by-phase onboarding looks like before you commit, GlobeVM will walk you through ours, deliverable by deliverable, before you sign anything.
Comments
0 Comments