You’ve signed with a managed IT provider. Now what actually happens? The first ninety days after hiring an MSP are the part nobody really explains before you commit, and the uncertainty is fair, because this is where a good provider proves they were worth choosing and a weak one quietly reveals they weren’t. Knowing what the process should look like lets you tell the difference while you can still do something about it.
Onboarding isn’t glamorous and it isn’t instant. A provider who promises to have everything humming on day two is either overpromising or planning to skip the unglamorous work that makes the relationship solid later. Here’s what a real onboarding looks like, roughly in the order it tends to happen.
The first week or two: discovery and stabilization
Before a provider can take good care of your environment, they have to understand it, and most businesses do not have a clean map of their own technology. So the early days are spent learning. A thorough provider documents everything, your servers, computers, network gear, software, cloud accounts, internet connections, who has access to what, and how it all fits together. This is tedious and essential. The quality of this documentation is the foundation everything else rests on.
Alongside discovery, they should be deploying their core tools onto your devices, the monitoring agents, the security software, the management platform that lets them actually do their job. You will notice some activity on your machines during this stretch. That is normal.
This is also when they tend to find things. Almost every onboarding surfaces surprises, a backup that has been quietly failing, accounts that should have been deactivated months ago, a piece of equipment well past its safe lifespan, a security gap nobody knew about. A good provider tells you about these plainly and helps you prioritize them rather than either hiding them or panicking you. How they handle the bad news they find is an early read on their honesty.
Weeks two through six: securing and fixing the urgent stuff
With the lay of the land understood, attention turns to the gaps that actually matter. The provider works through the issues discovery uncovered, in priority order. The dangerous stuff comes first, the failing backups, the missing multi-factor authentication, the unpatched systems, the accounts with far too much access.
You should expect a frank conversation here about what they found and what it will take to put right. Some of it falls inside your monthly fee. Some of it, particularly hardware that is genuinely at the end of its life, may need to be a project or a purchase, and a straight provider will lay that out rather than letting it ambush you later. This matters more here than it would Outside: replacing end-of-life equipment in Honolulu or Anchorage means real shipping lead times, so a genuinely local provider can do the discovery and on-site deployment in person and plan the timing around the freight rather than leaving you waiting. This is the stretch where the relationship’s honesty gets established, so pay attention to whether the recommendations feel like they serve your security or their invoice.
Weeks four through ten: settling into normal operations
As the urgent fixes land, things shift toward the rhythm you will actually live with. Your team starts using the help desk for day-to-day issues. The monitoring is live and catching problems. Patching is on a schedule. The provider learns the quirks of your specific business, which always takes a little time, because every company has its own peculiar software and its own way of working.
There is usually a short adjustment period for your people, learning the new way to get help, getting used to a security control that was not there before. A good provider supports your team through that change patiently instead of just flipping switches and walking away. If your staff are confused about how to reach support a month in, that is a communication failure worth raising immediately.
Around day ninety: the review that tells you the truth
The ninety-day mark is where it should all come together, and a serious provider treats it as a real milestone, not a formality. You should expect a proper review. What did they find, what did they fix, what is the current state of your environment, and what is the roadmap for the months ahead. This is where the value of the whole arrangement becomes visible, because for the first time you have a clear, documented picture of your own technology, often the first one you have ever had.
If you reach ninety days and your provider cannot tell you clearly what they found, what they did about it, and what comes next, that is a real warning sign. The relationship should feel more stable, more documented, and less mysterious than the day you started, not the same with a new logo on the invoice.
A word about switching from an existing provider
If you’re moving to a new MSP from an old one rather than starting fresh, onboarding carries an extra layer, because you have to extract your environment from the previous provider cleanly. Getting your passwords, your administrative access, and your data back, and making sure nothing gets dropped in the handoff, is its own discipline. We wrote a detailed guide on how to switch IT providers without downtime or losing data that covers exactly that transition, and it’s worth reading in parallel with this if you’re leaving someone behind.
What good onboarding feels like
You can usually tell whether it’s going well by how you feel about it. You should feel informed, not in the dark. You should be hearing about what’s being found and fixed, not wondering what’s happening on your systems. The surprises should be getting fewer over time, not multiplying. And by the end of it you should have something you didn’t have before, a real understanding of your own technology and a team you trust to look after it.
The other thing worth knowing is that onboarding is when the relationship’s character gets set. A provider who does the unglamorous documentation and the honest fixing in the first ninety days is one who will keep doing the right things when nobody is watching later. Our managed IT services guide lays out what to expect from the relationship beyond onboarding, once the foundation is in place.
If you want to know what these first ninety days would specifically look like for your business, what we’d likely find, how we’d prioritize it, and what the roadmap might be, that’s a conversation we’re happy to have before you commit to anyone. A discovery call costs you nothing and gives you a real sense of how we work. We’d be glad to help.