Most owners decide to change IT providers long before they actually do it. The decision is rarely the hard part — the relationship has usually been fading for a year. What keeps people stuck is the transition itself: who actually has the passwords, what happens to email mid-switch, whether the old provider will make it ugly. Fair questions. This guide answers them in the order that matters — what you own, the sequence that removes most of the risk, and what a well-run handover looks like.
Why switching feels riskier than it is
The fear usually has three parts. First, that the current provider holds the keys — admin passwords, the domain, the firewall — and could hold them hostage. Second, that the switch means downtime: a week of flaky email and people who cannot get work done. Third, that it will be an ugly breakup with a company that knows your systems better than you do.
Here is the honest picture. The accounts, the data, and the environment are yours; a provider administers them on your behalf, and the overwhelming majority hand them over professionally, because their reputation in this market depends on it. The technical work of a transition is mostly invisible to your team — documentation, credential transfers, and monitoring changes happen in the background while everyone keeps working. And the transitions that do go badly almost always share one cause: sequencing. The business gives notice first, the outgoing provider disengages, and the incoming one starts from a standing stop with no documentation. Every step below exists to prevent exactly that.
What you own — and what to collect
Whatever the mood of the exit, these belong to your business, and you want each one in an account your business controls — not one owned by either provider:
- Documentation. Network diagrams, server and device inventory, configurations, and the notes on how things are set up. If it exists, request it; if it does not, the new provider rebuilds it during discovery.
- Administrative credentials. Server and workstation admin accounts, firewall and switch logins, remote-management tools, and any password vault your environment lives in.
- Domain registrar and DNS access. The account that controls yourcompany.com controls your website and where your email is delivered. It should be registered to your business, on your billing details, and you should be able to log in today.
- Microsoft 365 global admin. Your tenant should have a global administrator account that belongs to the business, not only to the provider. The same goes for Google Workspace.
- Licensing inventory. Which Microsoft 365 plans you pay for, line-of-business licenses, renewal dates, and which licenses are billed through the provider and will need to move.
- Backup access. Where backups live, the credentials to reach them, any encryption keys, and the retention schedule. Do not let this one wait until the end.
- Vendor contracts and accounts. Internet, phones, printers, industry software, warranties — know which vendors bill you directly and which run through the provider.
None of this depends on goodwill. A professional managed IT agreement has exit terms that spell out documentation and credential handover — it is question nine in our guide to choosing an IT company in Tulsa — and it is worth pulling your current contract now to read the notice period and what you are owed on the way out.
The overlap play: sign the new provider before you give notice
The single most effective thing you can do to protect the transition is counterintuitive: sign with the new provider first. Discovery — the assessment, the documentation, the credential verification, the backup check — then happens while everything still works and while the incumbent is still engaged and answering questions. Your new provider sees the environment healthy and plans the handover with full information instead of guesses. Only then do you give notice, on the terms your contract sets.
Run it in the reverse order and everything compresses: discovery happens inside the notice period, under time pressure, with a provider who has already mentally moved on. Nothing about overlapping is underhanded — it is how orderly handovers are done, and a professional outgoing provider expects it. You will pay two providers for a few weeks, and it is the cheapest insurance in the entire process.
How long does the switch really take?
Typically 30 to 60 days from signing with the new provider to steady state — the point where your team knows who to call, monitoring and security tooling covers everything, and the old provider is fully out. The honest variables are the state of your documentation, how much of the environment sits in the outgoing provider’s own accounts, and how many vendor relationships need re-pointing. The full onboarding arc, through optimization and forward planning, runs about ninety days. What the timeline should not include is disruption: your people work normally throughout, and the moments that need coordination — moving a licensing agreement, changing a DNS record — are small, scheduled, and brief.
What good onboarding looks like: the 30/60/90
Ask any provider you are considering to put their onboarding plan in writing; vagueness here predicts the next three years. This is how we work at NSN Management, and it is a fair template for judging anyone:
- Days 1–30 — assess and baseline. Discovery and documentation of everything: accounts, devices, network, vendors. A baseline risk and performance review, a check that backups exist and actually restore, and a licensing inventory. Nothing big changes yet — the point is to know the environment before touching it.
- Days 31–60 — stabilize and secure. The critical issues found in the assessment get fixed, security standards roll out, and monitoring reaches everything. This is where the backlog the last provider left behind gets worked down.
- Days 61–90 — optimize and plan. The optimization plan, the priority projects, and a quarterly roadmap — the shift from fixing what was to planning what is next.
- Days 1–30
Assess and baseline
Discovery, documentation, and a baseline review of risk and performance.
- Days 31–60
Stabilize and secure
Critical issues handled first; standards rolled out for endpoints, identity, email, patching, and backup.
- Days 61–90
Optimize and plan
Optimization plan, priority projects, and a quarterly roadmap.
- Ongoing
Steady state
Support, report, and review — help desk, monitoring, monthly reporting, strategy sessions
Two things to insist on whoever you choose: response and resolution standards agreed up front and reported monthly, and a written plan for the first ninety days rather than “we’ll get you set up.” A managed IT agreement is a multi-year relationship, and the first ninety days tell you what the rest will be like.
What to tell your team, and when
Your team should hear it from you before anything changes on their computers — in practice, shortly after you give notice and about a week before the new provider’s work becomes visible. Keep it short and plain: who the new company is, why you chose them, and what changes day to day, which at the start is very little. Give people the two things they need — how to ask for help under the new arrangement, and one internal person who owns the transition. Managers a day or two early, everyone else together after that. Uncertainty is the disruptive thing, and a two-paragraph note removes most of it.
Red flags in the incumbent’s response
Most exits are professional, and it is reasonable to expect yours will be. But know the behaviors that signal a problem, so you can respond early:
- Refusing or endlessly delaying handover. Documentation and credentials that are “coming next week” for a month. Put every request in writing with a date, addressed to the owner, not the technician.
- Transition fees that are not in the contract. An offboarding charge is legitimate only where your agreement provides for one. Ask them to point to the clause.
- Credential games. Passwords changed after notice, admin access quietly removed, or accounts that turn out to be registered to the provider rather than to you. This is why the collection list comes before notice, not after.
- Service fading during the notice period. You are paying through the last day; support and monitoring should continue through the last day.
If you hit real resistance: keep everything in writing, involve your attorney if access or money is being withheld, and remember that accounts registered in your business’s name are recoverable directly through the vendors — Microsoft, your domain registrar, and your backup platform all have ownership-recovery processes. Slower than a cooperative handover, but it works, and an experienced incoming provider will have been through it before.
The handover checklist
| What to collect | What it includes | Watch for |
|---|---|---|
| Documentation | Network diagram, asset inventory, configurations, setup notes | It may not exist; the new provider rebuilds it in days 1–30 |
| Admin credentials | Servers, workstations, firewall, switches, Wi-Fi, remote tools | Accounts that exist only under the old provider’s name |
| Domain and DNS | Registrar login, DNS records, certificates | A domain registered to the provider instead of your business |
| Microsoft 365 | A global admin account owned by the business | Tenants where the only admins are the provider’s |
| Licensing | Microsoft 365 plans, line-of-business software, renewal dates | Licenses billed through the provider that must transfer |
| Backups | Platform access, encryption keys, retention schedule, restore steps | Backups that live only in provider-owned storage |
| Vendor accounts | Internet, phones, printers, industry software, warranties | Support contracts held in the provider’s name |
When not to switch — and how to time it
There are wrong moments. Mid-project is one: if you are midway through an office move, a server migration, or a new line-of-business rollout, finish it or pause at a clean point first. Busy season is another — for CPA firms that means tax season is off the table; start onboarding in late spring or summer so the new provider has lived with your environment through a quiet stretch before January. The same logic fits any seasonal business: count backward from your busiest weeks and give the transition 60 to 90 days of calm runway. The one exception is genuine failure — if systems are down and your provider is unreachable, stabilize with whoever can help fastest and run the orderly process afterward.
The switch is a project, not a leap
Switching managed IT providers is a project with a known shape, and businesses complete it every week without their customers noticing. Collect what you own. Sign the new provider before you give notice. Hold the incoming company to a written 30/60/90 plan, tell your team plainly, and time it for a quiet stretch. The fear is understandable; handled in that order, the risk is small — and staying too long with the wrong provider is the more expensive mistake.
NSN Management is Tulsa-owned and has supported businesses across the metro since 2012, and a transition from another provider follows exactly the 30/60/90 plan described above. If you are at the deciding stage — or stuck at the hesitating stage — book a Discovery Call. We will walk through your environment and tell you honestly what your transition would involve, and the checklist is yours either way.
Questions Tulsa businesses ask about this
How long does it take to switch IT providers?
Typically 30 to 60 days from signing with the new provider to steady state, with the full onboarding arc — assessment, stabilization, and forward planning — running about 90 days. The biggest variables are the state of your documentation and how much of the environment sits in the outgoing provider’s own accounts.
Will we have downtime when we change MSPs?
A well-run transition does not require taking systems down. Documentation, credential transfers, and monitoring changes happen in the background while your team works normally. The few moments that need coordination — moving a licensing agreement, updating a DNS record — are small, scheduled, and brief.
What if our current IT provider won't hand over passwords?
Put every request in writing, check what your contract’s exit terms require, and involve your attorney if access is being withheld. Accounts registered in your business’s name — Microsoft 365, your domain registrar, your backup platform — are recoverable through those vendors’ ownership processes. It is slower than a cooperative handover, but it works.
When is the best time to switch IT companies?
During a quiet stretch, with 60 to 90 days of runway before your busiest season. Avoid switching mid-project, and if you run a CPA firm, avoid tax season — start in late spring or summer so the new provider knows your environment well before January.
Should we sign with the new provider before telling our current one?
Yes. Signing first lets the new provider run discovery — documentation, credential verification, backup checks — while everything still works and the incumbent is still engaged. Then give notice on your contract’s terms. A few weeks of overlap is the cheapest insurance in the process.
Does NSN Management handle the handover with our old provider?
Yes. Once you sign and give notice, we coordinate the handover directly — requesting documentation and credentials, verifying access, and re-pointing vendor relationships — so you are not stuck in the middle. Onboarding then follows our 30/60/90 plan, with response and resolution standards agreed up front and reported monthly.