Switching IT providers makes owners nervous for one reason: you are handing over the keys to a business you still have to run on Monday. The worry is rarely that the new provider is worse. It is the gap in between — and that gap is a question of sequence.
A well-run MSP onboarding takes roughly 30 days in a fixed order: administrative control and documentation first, then monitoring and security, then the backlog of deferred problems, then verification and a written plan.
Day 0 is the credential handover. Week 1 is discovery and protection. Weeks 2–3 are remediation and the staff rollout. Week 4 is verification, documentation, and a roadmap. A provider who cannot describe that sequence before you sign is improvising.
Why the Order Matters More Than the Speed
Ask how fast a provider can onboard you and you get an optimistic number. Ask in what order, and you learn something:
- Control before change. Nobody can secure, patch, or back up an environment they do not yet administer.
- Knowledge before action. Most environments that change hands are undocumented; a project plan written before anyone looked at your network is a guess.
- Protection before projects. Monitoring, endpoint security, and working backups go in early, because they limit the damage if something goes wrong.
A provider who opens with a hardware quote has inverted all three.
Day 0 — The Handover Day
Day 0 is administrative, not technical, and it is where most transitions are quietly won or lost. By the end of it, your new provider should have verified control of the systems you depend on, and you should have a written record of what changed hands.
Credentials move through a password manager, not email, and each gets tested on the spot. A credential nobody logged into is not a handover; it is a hope. The two most costly to skip are your domain registrar and Microsoft 365 global admin account — without them, a provider can support your users but cannot fix your email. Expect every password rotated afterward: standard practice, not a judgment on your previous provider.
Week 1 — Discovery, Monitoring, and Protection
Week 1 is documentation and defenses. Discovery should produce an asset inventory, network map, Microsoft 365 tenant review, license count, backup review, and a plain answer to where your data lives. Monitoring and endpoint security deploy alongside it.
Backup verification deserves attention. “Verified” means somebody ran a test restore and watched a file come back — not that a dashboard showed green. Backups covering the file server but not Microsoft 365 are a common find.
By week’s end you should have two lists: what you own, and what is wrong with it, ranked by risk. Not a list of things to buy.
Weeks 2–3 — Remediation and the User Rollout
This is when the deferred-maintenance bill arrives: expired licenses, a firewall on default credentials, the server nobody patched since the last IT person left, multi-factor authentication on for some staff and not others. The list usually runs long. What matters is how it is presented — each item should carry a recommendation: fix now, schedule it, or accept the risk.
Your staff meet the new provider now: how to open a ticket, who to call, what to expect. If you are the office manager, this is your part of the project. The old remote-access agents come off now too.
Week 4 — Verification, Documentation, and the Plan
Week 4 is where good onboarding distinguishes itself: it is the week with no emergencies in it. Expect a walkthrough: here is your environment, here is what changed, here is what we have not reached and why.
Three deliverables are reasonable. Documentation you can open yourself — inventory, licenses, network notes, vendor contacts. A support rhythm, so everyone knows how tickets escalate. And a 12-to-36-month roadmap of what gets replaced or retired and when — the planning a vCIO conversation covers.
If week 4 is silence, your onboarding did not finish. It stopped.
The Switching Checklist: What Has to Change Hands
Most of this is yours to own regardless of who you hire — and better found now than during an outage.
- Administrative credentials, in a vault. Servers, workstations, network gear, firewall, wireless, line-of-business apps — tested individually, then rotated.
- Domain and DNS at the registrar. Who holds the registration, whose name it is in, when it renews.
- Microsoft 365 global administrator. An account under your control, plus partner-of-record and delegated-access relationships — old ones removed.
- Backup configuration and a verified test restore. What is backed up, how often, stored where, retained how long — plus proof a restore ran, Microsoft 365 included.
- Licensing and subscription inventory. Which licenses you own directly versus which sit on your provider’s agreement, with seat counts and renewal dates.
- Vendor and carrier contacts. Internet, phone, copiers, software publishers, alarm and access control, with account numbers.
- Documentation and configuration records. Network diagrams, static IPs, VPN and firewall rules, application notes, warranties — in writing.
- Offboarding the outgoing provider. Agents off every device, their tools removed once replacements work, staff accounts disabled, delegated access revoked, notice served.
Red Flags in the First 30 Days
- No written onboarding plan. If nobody can say what happens in week 2, the sequence is improvised.
- Software deployed before discovery. Agents rolling out before anyone inventoried the environment means the plan was pre-written.
- Backups described rather than tested. “Your backups look fine” without a restore is an assumption.
- Documentation you cannot see. Your own inventory treated as the provider’s property is a quiet lock-in.
- A quote before an inventory. That is a sales motion, not a finding.
- Silence, or one technician holding everything. No status update, no findings list, no documentation behind the person who knows your network.
Still deciding rather than switching? See signs you need to switch IT providers and our buyer’s checklist for choosing a managed IT provider. Settle co-managed versus fully managed IT first; what an MSP does covers the scope.
How This Works at TVG Consulting
TVG Consulting runs managed IT for small and mid-sized businesses from two bases: Burbank and greater Los Angeles, and Nashville and Franklin. Local matters most during a transition, because the first 30 days are when you are likeliest to need somebody on site.
Our onboarding starts with documenting what you have, because most environments we take over are not documented anywhere. Monitoring and security controls go in next, then we work the backlog of deferred problems the previous arrangement left behind. We do not charge separately for the transition — it is part of getting started.
If your current provider will not cooperate, that does not stop the switch: we can independently audit your environment, reset credentials, and establish management without their participation. Urgent issues get immediate engagement throughout.
Frequently Asked Questions
How long does it take to switch IT providers?
Plan on about a month. Core transition work runs two to four weeks for a typical office; the rest of the 30 days goes to remediation and the closing review.
Will my business go down while we switch?
Most of the work happens in the background and interrupts nobody. A few steps need brief scheduled interruptions — a firewall swap, a restart after an agent install — announced in advance.
What do I need to give a new MSP on day one?
Administrative credentials for servers, workstations, and network gear; your domain registrar login; a Microsoft 365 global admin account; backup access; your licensing list; and vendor contacts. If you cannot locate some, say so in week one.
What if my current IT provider will not cooperate?
An obstacle, not a blocker. Your environment can be independently audited, credentials reset, and management established without their participation — it just takes longer. Make sure your registrar and Microsoft 365 tenant are in your business’s name.
Who removes the old provider’s software from our computers?
Your incoming provider, and the order matters: replacement monitoring, antivirus, and backup tooling get confirmed working before the outgoing tools come off. Remote-access and RMM agents keep granting access until somebody removes them.
Should I tell my old provider before onboarding starts?
Check your agreement first: notice periods and auto-renewal dates decide the timing. Many businesses want a signed agreement and transition plan in hand before giving notice. Either way, give notice in writing.
Does MSP onboarding cost extra?
It varies, so get it in writing before you sign. Ask whether the quote covers discovery, documentation, agent deployment, remediation, and data migration — the pieces most often excluded. At TVG, transition work is included.
Thinking About Switching Providers?
A discovery conversation is exactly that: a look at your setup, what a transition would involve, and whether we fit.
Or call (818) 284-4118.
About the author
Garett Chipman - CEO, TVG Consulting
Garett Chipman is an IT executive and entrepreneur with more than 20 years of experience designing business technology solutions. He founded TVG Consulting in 2005 after holding CTO and management roles at companies including GRB Entertainment and AMG, and as CEO he oversees overall client operations, strategic technology decisions, and custom AI and automation design.