The short answer: Switching managed IT providers is a transition, not a flip of a switch. In a well-run 90-day onboarding, week one is discovery and documentation, month one is security tool deployment and access handover, month two is stabilization and learning your environment, and month three is a performance review against the commitments made at signing. Expect some bumps in weeks 2 to 4 — that’s normal. Equipment shouldn’t be replaced for the first 90 days unless absolutely necessary.
If you’ve signed with a new MSP, you’ve already done the hard part: picking the right partner. The next 90 days is about the partner earning the trust you’ve given them. Here’s what should happen, when, and what to watch for.
Why 90 Days Matters
An MSP transition isn’t like a software subscription. The new team is inheriting an environment they didn’t build, documentation that may not exist, and a user base that’s used to calling whoever they’ve always called. Rushing past discovery, swapping tools out the gate, or replacing hardware before anyone understands the environment is how good transitions go sideways.
A 90-day window gives the incoming MSP time to actually learn your business, establish baselines, and earn the right to recommend changes — instead of making changes they can’t defend yet. Done right, by day 91 you have a provider that understands your operation better than the one they replaced.
Week One: Discovery and Documentation
The first week isn’t about fixing anything. It’s about understanding everything.
What should be happening:
- Kickoff meeting** with your leadership and any internal IT staff to confirm priorities, pain points, and the handful of things that absolutely cannot break during transition
- Environment discovery** — mapping your network, servers, workstations, cloud services, line-of-business applications, vendors, and existing security tools
- Credential handover** — domain admin, firewall, O365/Google Workspace, backup systems, VPN, anything mission-critical
- Stakeholder interviews** — a few short conversations with people in different roles so the MSP hears what “slow” and “broken” actually means to your team
- Ticketing and communication channels set up** — email addresses, phone lines, portal access, so your team knows exactly how to reach the new support team
What you should feel: A lot of questions, a lot of note-taking, not a lot of action. That’s correct. If your new MSP is making major changes in week one, they’re moving too fast.
Common friction: Credentials nobody has. Old admin accounts belonging to people who left. Documentation that doesn’t exist. Budget a few hours of your time to help track these down — it’s painful once, and then it’s done forever.
Month One: Tool Deployment and Baseline
Weeks 2 through 4 are where the new provider’s management layer goes in.
What should be happening:
- Remote monitoring and management (RMM) agents** deployed to every managed endpoint so the MSP can see health, patch status, and alerts in real time
- Endpoint detection and response (EDR) / antivirus** replaced or layered onto the existing tool — without disabling what’s currently protecting you until the new tool is verified active
- Email and identity security** — MFA enforcement, phishing protection, DNS filtering, reviewed and brought up to modern standards
- Backup verification** — confirming that what you think is backing up actually is, and that a restore works
- Patch management cycle** established with a documented maintenance window
- User training** if MFA or new tools are being introduced, so your team isn’t blindsided
What you should feel: Some short, scheduled interruptions as agents install and reboots happen. A noticeable increase in security prompts (MFA especially) for a week or two while users adjust. Tickets starting to route through the new team’s system.
Commitment from a responsible MSP: No equipment replacement in the first 90 days unless something is genuinely failing. The incoming team doesn’t yet know your environment well enough to recommend hardware changes. Any MSP pushing replacement in month one is either over-selling or under-assessing.
Common friction: One or two applications will have compatibility quirks with the new security tools. Expect 1-3 days of tuning. This is normal and doesn’t mean the transition is failing.
Month Two: Stabilization and Institutional Knowledge
By week 5 or 6, the new infrastructure is in place. Month two is about learning your environment deeply enough to support it without constantly asking you questions.
What should be happening:
- Ticket patterns reviewed** — which users call most, which applications cause the most tickets, where the hidden complexity is
- Documentation written** — the runbooks, vendor contact lists, system diagrams, and recovery procedures that didn’t exist before
- Vendor coordination** — line-of-business software vendors, phone/internet providers, and facility vendors all know who the new IT partner is
- Baseline reporting** — uptime, security posture, patch compliance, ticket volume, all being tracked so there’s data to point to at the 90-day review
- First proactive recommendations** — the MSP should start surfacing small improvements they’ve noticed. Small. The big stuff comes at the 90-day review
What you should feel: Things getting quieter. Fewer surprises. Tickets resolving faster because the team knows your environment. Your internal point person spending less time on IT coordination than they did in month one.
Common friction: This is when inherited problems surface — a weak backup that’s been weak for years, a firewall rule nobody understood, a legacy server on borrowed time. A good MSP flags these with a recommendation and a priority level, not a panic.
Month Three: The 90-Day Review
At the end of 90 days, the new MSP should sit down with you — ideally in person — and have a structured review.
What should be on the agenda:
- Against the commitments made at signing** — did the MSP deliver what they said they would, on the timeline they promised? If not, why?
- Security posture snapshot** — what was the baseline on day one, what is it now, what’s still open
- Ticket metrics** — volume, response time, resolution time, trends over the 90 days
- Documentation deliverables** — what’s been written down, where it lives, what’s left to finish
- Your team’s experience** — what’s better, what’s worse, what’s the same
- Strategic roadmap** — the MSP’s recommendations for the next 12 months, prioritized by impact and cost
- Adjustments to the agreement** if anything isn’t working
This is the checkpoint where you decide if the fit is right. At ACS, the 90-day review isn’t a contract renewal — it’s an honest conversation about performance. Renew by performance, not penalty.
What You Should Commit to As the Client
A good transition requires both sides. Here’s what your new MSP is counting on from you:
- One empowered point of contact** on your side for the first 90 days. Someone who can make decisions, not just pass messages.
- Timely feedback.** If something’s off, tell the MSP in week two, not week twelve. Small course corrections are easy. Silent resentment is not.
- Your team uses the new ticketing system.** Phone calls and hallway asks in week one are fine. By week four, everyone should be using the new intake channel.
- Reasonable access to your environment.** If the MSP is being blocked from doing their job because nobody can find a password, the transition stalls.
- Willingness to accept recommendations.** The MSP can’t protect you from risks you won’t let them address.
What Good and Bad Look Like at Day 91
1. Every user has a clear way to get support and uses it
2. Monitoring is in place and someone is actively responding to alerts
3. MFA is on for every account that matters
4. Backups work and a test restore has been completed
5. You have written documentation of how your environment is configured
6. The MSP can answer questions about your environment without calling you
1. Your team still calls the old provider or a random technician for help
2. Tools from the old MSP are still installed and competing with the new tools
3. Nobody has tested a backup restore
4. Tickets are piling up and resolution time is getting worse, not better
5. Recommendations from the MSP feel like upsells, not improvements
If your 90-day review matches the bad list, that’s important information. A good MSP will acknowledge it. A bad one will blame you.
A Realistic Expectation
Transitions are bumpy in weeks 2 to 4. That’s normal. What matters is whether the bumps are getting smaller and whether the MSP is communicating through them. By week 6, things should feel calmer than before you switched. By day 91, they should feel significantly better.
If you’re in month one of an MSP transition right now and something feels off, the right move is to say so out loud — to them and to us if you’d like a second opinion. Schedule a conversation and we’ll walk you through what good looks like at your specific stage.





