Switching managed IT providers usually takes weeks rather than days, and very little of that time is your new provider working. The technical setup is the short part. Agents get deployed, monitoring comes online, and a competent team does most of that inside a fortnight.
What takes the weeks is everything around it. The notice period sitting in an agreement you signed three years ago. The administrator password to your firewall, held by one person who no longer works at the company you are leaving. The renewal date on your Microsoft licences. A domain registered in the name of a web designer you last spoke to in 2019.
So the honest answer is that it depends on what you can hand over on day one, and you can find that out this week without telling anybody you are shopping.
Key Takeaways
- Three things set the calendar, and none is your new provider’s speed: your current notice period, how complete the handover is, and a few clocks owned by other companies.
- Read your existing agreement first. The notice period in it is the earliest real date you have, and the one thing you cannot fix later.
- Missing credentials are what stalls a transition. Utah businesses that have used the same small provider for years are the most exposed.
- Microsoft 365 involves two separate relationships with your old provider. You can cut their admin access yourself. Licence billing moves on the renewal calendar instead.
- Some clocks belong to other people. ICANN locks a domain against transfer for 60 days after a registrant change, and an annual Microsoft subscription cannot be cancelled after its seven day window.
- One provider for the network, the support and the connection removes a handover rather than adding one, which is how 1Wire’s managed IT solutions are put together for Utah businesses.
What a provider transition actually looks like
A managed IT transition runs in four phases: notice, discovery, deployment and a supervised overlap, with the first phase usually the longest and the least in anyone’s control.
The table below is the shape of the work rather than a promise about dates. A five person insurance office in Bountiful with everything in Microsoft 365 moves faster than a forty person manufacturer in Ogden running production on a server in the back room. The phases stay the same. Their lengths do not.
| Phase | Usual span | What happens | What decides the length |
|---|---|---|---|
| Before notice: getting ready | Two to three weeks, and it is free | You read your current agreement, find the notice and renewal dates, and start collecting what you already hold. Your new provider writes the handover list. | Nothing external. This is the only phase entirely under your control, and doing it properly shortens every phase after it. |
| Notice served | Whatever your agreement says | Notice goes in writing to your current provider. The handover request goes with it, item by item, with a date attached. | Your existing contract, and nothing else. This is usually the longest single stretch and you cannot shorten it after the fact. |
| Discovery | One to two weeks, overlapping the notice period | Everything gets found and documented: servers, workstations, firewall, switches, access points, licences, backups, line of business vendors. In a Layton office this includes walking the closet. | How much documentation exists. A well-documented environment is days. An undocumented one is where the surprises live. |
| Recovering what is missing | Runs alongside discovery, or adds weeks if it starts late | Vendor account recoveries, evening resets of devices nobody has the password for, services rebuilt alongside the old ones where recovery is not possible. | Other companies' recovery processes and your out-of-hours windows. This is the single biggest cause of a transition running long. |
| Deployment | Around one to two weeks | Monitoring and management agents onto every machine, backup configured and a restore tested, security tooling applied, documentation written up, support routes published to your staff. | Number of sites and machines, plus how many devices are only reachable in person. Rarely the bottleneck. |
| Supervised overlap | Days to a couple of weeks | Both providers still have access. Your staff in Ogden or Murray start calling the new number on an agreed date. Old accounts are identified but not yet removed. | A written cutover date and a checklist. Ambiguity, not technology, is what stretches this phase. |
| Old access removed | One day, once the checklist is clear | Previous administrator accounts disabled and confirmed disabled. Partner admin roles removed in Microsoft 365. Documentation handed to you, not just held for you. | Nothing, if the checklist was kept. Everything, if anybody skipped it. |
| Licence and billing moves | On your renewal date, whenever that is | Microsoft and other subscriptions move to the new provider's billing relationship as their terms come up for renewal. | Your subscription terms. An annual licence bought in March moves in March, no matter when you switched. |
Notice that nothing in the deployment phase is difficult. That is the point. When a transition runs long it is almost never because deployment was hard, it is because discovery found a hole and the fix was waiting on somebody else. What gets deployed there, and what it covers once running, is listed on our managed IT solutions page.
The clock starts with your current agreement
The first date on your calendar is the end of your notice period, and it is set by a document you already have.
Go and find your current managed services agreement before you do anything else. You are looking for three things: how much notice you owe, whether the term renews automatically and on what date, and what the provider owes you on the way out. Most Utah owners we talk to have not read theirs since the day they signed it, and a fair number cannot find it at all, which is itself a finding.
Then work backwards from the renewal date. If the agreement renews in November and wants notice beforehand, every other decision here has a deadline attached, and it is earlier than the one in your head. We see businesses in Provo and Draper discover in October that the window closed in September, then spend another year with a provider they had already decided to leave.
What belongs in a managed IT agreement, and which terms are worth negotiating, deserves its own post. For now the only thing you need out of the document is the date.
The handover is the whole job
The handover is the transfer of the credentials, documentation and vendor relationships that let anybody manage your systems, and it decides your timeline more than anything else.
Here is the part most posts on this skip. Your outgoing provider is not obliged to be enthusiastic. Most are professional, some are slow, and a few are slow on purpose. Plan for the middle case: a provider who hands over what you name and volunteers nothing you did not.
So you need the list. Not a general request for documentation, which gets you a network diagram from 2021. A specific list of accounts, devices and vendors, item by item, with a date attached. Your new provider should write that list for you, and if they cannot, that tells you something before you have signed anything.
| What to ask for | Who usually holds it | Why the switch stalls without it | If nobody has it |
|---|---|---|---|
| Access and identity | |||
| Microsoft 365 or Google Workspace global admin | Outgoing provider | Nothing else can be inventoried until somebody can see the tenant. | Recoverable through the vendor with proof of business ownership. Start it first, because it gates everything. |
| Firewall and router administrator credentials | Outgoing provider | No visibility of your rules, VPN or address ranges, and no safe way to change anything. | Factory reset and rebuild, scheduled for an evening. Fast to do, slow to schedule. |
| Switch, access point and server local accounts | Outgoing provider | Devices cannot be monitored, patched or reconfigured, so they quietly stay unmanaged. | Reset device by device. In an older Ogden building this is the row that finds hardware nobody knew was there. |
| Domain registrar and DNS logins | Often a third party entirely | Mail routing and website records cannot be changed, and ICANN rules put fixed waiting periods on registrar moves. | Registrar account recovery, then sequence carefully. Changing the registrant can lock the domain for 60 days. |
| Documentation | |||
| Network documentation and diagram | Outgoing provider | Without it, discovery is done from scratch, which is the difference between days and weeks. | Rebuilt on site. This is the single largest chunk of avoidable time in a transition. |
| Hardware inventory with ages and warranty dates | Outgoing provider | You cannot plan replacements, and a failure mid-transition becomes an argument about whose job it was. | Counted in person, serial by serial. Slow but straightforward. |
| Licence and subscription records with renewal dates | Split between you and them | Renewal dates decide when billing can move. Miss one and it auto-renews under the old arrangement. | Pulled from the vendor portals once admin access is back. Your accounts payable records are a good second source. |
| Continuity | |||
| Backup data, its configuration and its retention | Outgoing provider | This is the row with real risk in it. Backups held in a provider's platform do not automatically become yours. | New backups start immediately, and historical data is requested in writing early. Do not leave this to the last week. |
| Line of business software vendor contacts and account numbers | Usually one person in your office | Practice management, dispatch, estimating and POS vendors will only talk to the contact on file, and updating that takes their timeline. | Each vendor's own authorization process. A Utah clinic or contractor should start these in week one. |
| Monitoring, ticket and asset history | Outgoing provider | Nothing breaks without it, but you lose the record of what has failed before and what was already planned. | Ask once, in writing, and move on. Useful to have, never worth delaying a switch over. |
| Internet, phone and cabling vendor details | Spread across several companies | Each separate vendor is another handover and another company's schedule to wait on. | Recovered from your own invoices. Fewer vendors means fewer of these rows, which is the argument for consolidating. |
Run that list against your own business today. Anything you cannot answer with certainty is a candidate for the delay that adds two weeks. A dental practice in Lehi that knows who holds the practice management vendor relationship has a shorter transition than the same practice that does not, and the difference was decided before anybody signed anything.
What happens when nobody has the keys
Missing credentials are recoverable, and the recovery is what costs the time rather than the money.
It is the most common stall in the process, and it is worst in the businesses that feel safest. A construction firm in Syracuse that has used the same two person IT shop since 2014 has the most undocumented environment we see. When one person set everything up and never left, nothing had to be written down.
When an account cannot be produced there are three routes. The vendor’s own recovery process, which needs proof that you own the business and takes as long as that vendor takes. A factory reset and rebuild, quick to do and scheduled for an evening. Or the service gets stood up alongside the old one and cut over, the cleanest and the slowest.
None of those is a disaster. All of them are calendar. Finding out early lets you run the recoveries during the notice period, when they cost you nothing. One safety net is worth knowing about: if a user account is deleted during a transition, Microsoft Entra ID keeps it suspended for 30 days and it can be restored with its properties intact inside that window, after which permanent deletion starts on its own and cannot be stopped.
Not sure what you could produce today? Book a time with us. No obligation. Just expert advice.
Microsoft 365 is where most Utah transitions get decided
Your old provider holds two separate positions in your Microsoft tenant, and they end on two different schedules.
The first is administrative access. In the Microsoft 365 admin center, under Settings and then Partner relationships, you can see every partner holding a role in your tenant and remove those roles yourself, without your outgoing provider’s cooperation. Microsoft’s own documentation, updated on 3 September 2026, walks a customer through it and adds a caveat worth reading twice: even with the Global Administrator role removed, the partner can still make purchases on your behalf, so ask them to end that in Partner Center.
The second is the reseller relationship, which is who bills you for licences, and that one does not end on request. Microsoft’s Partner Center documentation states that if any subscriptions are still active, the option to remove the reseller relationship is inactive. This is why licence billing moves at renewal rather than on the day you switch.
One more number from the same source sets the date. Under Microsoft’s new commerce cancellation policy, a subscription can be cancelled for a prorated refund within seven calendar days of purchase, after which the window does not reopen until it renews into a new term. So an accounting firm in Murray on annual subscriptions that renew in March can change provider in October and should expect the licences to move in March.
That is not a delay anybody caused. It is a term you already agreed to, and a good provider tells you in the first meeting rather than the sixth week. What we take over is set out on the managed IT solutions page.
The clocks nobody can compress
Some parts of your setup are governed by third party rules with fixed waiting periods that no provider on either side can speed up.
Your domain catches Utah businesses most often, because it is so often registered to somebody who no longer works with you. ICANN’s Transfer Policy, which every accredited registrar follows and which took effect on 21 February 2024 with compliance required by 21 August 2025, sets two rules worth knowing. A domain is generally locked against transfer to a new registrar for 60 days after a change of registrant. And a registrar must either let you generate your own authorization code or provide it within five calendar days of your request.
Sixty days. If you discover in week two that your domain sits with a former marketing contractor in Salt Lake City, and you fix the ownership record first, you may have just locked the registration for two months. The fix is sequencing, decided before anybody touches anything. Most transitions do not need the domain to move at all, because DNS hosting can change without the registration changing hands, but you need to know which one you are doing in week one.
The same applies to every other contract with a clock in it: alarm and camera monitoring, copier agreements, software renewals. None stops a switch. All have dates, and dates are the currency of this exercise.
The overlap is a feature, not a gap
A supervised overlap is the period when both providers still have access, and it is the safest part of the transition rather than the riskiest.
Owners worry about this stretch because it feels like nobody is in charge. Done properly it is the opposite. The new provider has monitoring in place and can see what is happening, the old one is still reachable for the thing nobody documented, and nothing has been switched off yet.
What makes it work is one decision made in writing before it starts: from this date, employees in your Layton office call this number. Ambiguity about who answers the phone is the only real risk here, and an email and a card by the coffee machine solves it.
What ends the overlap is a checklist. Old administrator accounts disabled and confirmed disabled, backups running from the new system with a restore actually tested, alerting going to the right people, documentation delivered to you rather than held for you. Then the old access comes out.
For a smaller version of the same choreography, our guide to switching to managed WiFi without disrupting your business walks through a single site cutover hour by hour.
Fewer handovers beats a faster handover
Every separate vendor in your setup is another handover, another set of credentials and another company whose schedule you wait on.
A Utah business with one company for internet, another for phones, a third for IT support and a fourth for cabling has four relationships to unwind and re-establish. With those functions under one roof it has one.
We have been an internet provider since 2006, so when we take over managed IT for a business in Orem or Clearfield, the connection, the network hardware and the support sit with the same company. There is no handover between us and the carrier, because we are the carrier, which during a transition is one fewer schedule to wait on.
For the full picture of what the term covers, start with our guide to the different types of managed IT, and our comparison of help desk support and managed IT services covers what level of service you actually need.
Switching IT providers in Utah
We are a Utah company, and the transitions we run are for businesses here: Salt Lake City, Ogden, Provo, Orem, Layton, Murray, Midvale and Draper.
That matters during a switch in a way it does not on a normal Tuesday. Discovery goes faster when somebody can walk your closet instead of asking you to photograph it, and the handover list gets written by people who have seen the same three surprises in a hundred Utah offices.
Bring us your current agreement and whatever documentation you can find, even if it is nothing. We will tell you what is missing, what recovering it involves and what the realistic calendar looks like, including the answer that you should wait for your renewal date rather than pay twice.
Book a time with us. No obligation. Just expert advice. Everything included is set out on the managed IT solutions page.
Frequently Asked Questions
How long does it take to switch managed IT providers?
Weeks rather than days for most businesses, with the notice period in your current agreement usually the longest single stretch. The technical deployment is the short part. What extends a transition is missing credentials, undocumented vendor relationships and third party waiting periods such as licence renewal dates and domain transfer locks. A business with complete documentation moves considerably faster than one without, and you can find out which you are this week.
Will my business have downtime when switching IT providers?
A well planned switch does not require downtime, because the old systems keep running while the new monitoring and management tools are put in place alongside them. The exceptions are scheduled and small: a firewall or switch that has to be reset because nobody has the administrator password is usually done in an evening. Anything that does need an interruption should appear on the plan with a date on it before you sign.
What should my old IT provider hand over?
Administrator credentials for every system they manage, network documentation including the firewall configuration and address ranges, your backup data and its configuration, licence and subscription records, vendor contacts and account numbers for your line of business software, hardware inventory with warranty dates, and any monitoring or ticket history you are entitled to. Ask for it as a specific list with a date attached rather than as a general request.
What if my current provider will not cooperate with the transition?
It slows things down but it does not stop them. Most credentials can be recovered through the vendor’s own account recovery process, most devices can be reset and rebuilt during an evening window, and most services can be stood up alongside the old ones and cut over. Your new provider should assume a minimal handover and plan for it rather than being surprised by it in week three.
Can I remove my old IT provider’s access to Microsoft 365 myself?
Yes. In the Microsoft 365 admin center, under Settings and then Partner relationships, you can see which partners hold roles in your tenant and remove those roles without the partner’s involvement. Microsoft notes that a partner may still be able to make purchases on your behalf after their admin role is removed, so ask them to end that separately. The reseller relationship that bills your licences is different and generally ends when those subscriptions move at renewal.
When is the best time to switch IT providers?
Work backwards from two dates: the notice period in your current agreement and the renewal date on your licences. Starting the conversation two to three months ahead of the earlier of those gives you room to recover anything missing while you are still under contract, which costs nothing. Switching in the middle of an office move, a busy season or an audit is the one timing choice we would talk a Utah business out of. See managed IT solutions for what 1Wire takes over, and bring your renewal dates to the first conversation.
