Most provider changes do not fail at the technical cutover. They fail at the licensing layer, weeks earlier, when a company finds out it does not control the subscriptions its email and security tooling run on. Your Microsoft 365 tenant belongs to your organization and it does not move when you change providers. The billing relationship sitting on top of it usually belongs to the outgoing provider, and moving that relationship needs their cooperation inside a window that closes. Those are two different things, and treating them as one produces surprise invoices, a support gap, or a tenant migration nobody needed to pay for. Sort out custody before you give notice and the rest of the transition becomes ordinary project work.
Overview: The Five Facts That Decide How This Goes
Before any conversation about a new agreement, our team walks clients through five points that predict how smooth a provider change will be. Each one is a custody question rather than a technical one.
- Your tenant is not in play. The Microsoft 365 or Entra ID tenant is registered to your organization. A new provider takes over administration of it, so a migration into a fresh tenant is almost never required.
- Your subscriptions may not be yours to move alone. If licensing runs through the incumbent’s Cloud Solution Provider agreement, the billing transfer needs their approval, and the request expires if it sits unanswered.
- Annual commitments follow you. A New Commerce annual term cannot be cancelled part way through. Whoever bills it, the term stays until its renewal date.
- The tooling licenses are theirs. Remote monitoring, endpoint protection, mail filtering and backup platforms are usually licensed to the provider. Those stop at the exit date, and any backup data inside them stops with it.
- Global admin is not ownership. Stale admin rights are a security problem, so access gets inventoried on the way in and revoked on the way out.
Why Switching IT Providers Stalls at the Licensing Layer
Switching IT providers stalls at the licensing layer because subscription billing, platform tooling and administrative rights each sit with a different party, and none of them transfer automatically when a contract ends. The technical work of onboarding a new provider is well understood. The commercial plumbing underneath it is where companies find out that the thing they have been paying for every month is not a thing they hold.
We see the same pattern in the wild. A leadership team decides to move, gives notice as the agreement requires, and only then asks how the licenses come across. By then the outgoing provider has no reason to hurry and every reason to run the clock.
Why Buyers Assume the Licenses Are Already Theirs
Buyers assume their licenses are already theirs because the invoice says so, and in the accounting sense that is fair. You paid for a defined seat count every month, you saw those seats assigned to your staff, and nothing in that experience suggests a third party sits between you and the vendor.
The counter position is partly right. Your license entitlements are genuinely yours. The seats exist in your tenant, the data those seats produced is your data, and no provider can revoke either by walking away. What the provider holds is the transacting relationship: the agreement those subscriptions were purchased under, and the billing that flows through it. That distinction has no visible surface in day to day work, which is why it stays hidden until an exit.
Neither reading is complete on its own. You own the entitlement and the data. Someone else may hold the paper. A provider change is the one moment those two facts have to be reconciled, and the reconciliation has a deadline attached.
Why the Contract Decides More Than the Technology
The contract decides more than the technology because it sets the notice period, the renewal behavior, and whether anything is owed to you on the way out. Read it before the first conversation with a prospective provider, not after.
Three patterns matter. Auto renewal clauses can quietly commit you to another full term if notice lands a day late. Offboarding or transition assistance may be billable at a rate the agreement never highlighted, or may not be promised at all. And some agreements are silent on documentation, which means the network diagrams and password records built while managing your environment are not contractually owed to you.
Set against that, plenty of agreements are reasonable and plenty of providers behave well without being compelled to. Treating every incumbent as adversarial produces a worse transition than treating them as a party with legitimate interests. Read the document, ask direct questions, and write down the answers. The same discipline applies to the incoming agreement, and a structured way to compare managed IT providers before you sign is worth the hour it takes.
The 5 Hidden License and Tenant Traps in a Provider Change
The five traps below account for most of the delay and unplanned cost we see in provider transitions. None of them are technical faults. Each is a custody assumption that nobody tested until the timeline was already running.
Trap 1: Treating the Tenant and the Subscription as One Object
Your tenant and your subscriptions are separate objects with separate owners, and conflating them causes companies to buy migrations they do not need. The tenant is registered to your organization and stays where it is. The subscription is a purchase made through a transacting partner, and that partner can change without anything inside the tenant moving.
We have watched companies budget for a full mailbox and file migration into a new tenant, assuming that leaving a provider means leaving their environment. In nearly every case the tenant stays, the users stay, the data stays, and only the billing relationship and the administrative access change hands. The migration was never required.
Trap 2: Missing the Transfer Window
A billing transfer between providers requires the outgoing partner to approve the request, and per Microsoft’s Partner Center documentation that request expires after thirty days without a response. Silence is a valid strategy for a provider with no incentive to cooperate, and an expired request means starting again.
This is the trap with the sharpest edge, because the clock runs at the same time as your notice period. Start the transfer conversation while the relationship still has value to the other side. A request opened before notice is given tends to move. A request opened after tends to sit.
Trap 3: Assuming an Annual Term Can Be Cancelled
An annual New Commerce term cannot be cancelled mid term, so the commitment travels with your organization regardless of who bills it. Companies expecting to shed licenses on the exit date instead find they are committed until the renewal anniversary.
The practical consequence is a period of paying for seats you may no longer want. That is survivable when planned for and expensive when it arrives as a surprise on a first invoice. Ask for every subscription’s term type and renewal date in writing during the inventory, before any dates get committed.
Trap 4: Forgetting That the Tooling Licenses Leave With the Provider
The remote monitoring agent, the endpoint protection platform, the mail filtering service and the backup product are usually licensed to the provider rather than to you, and they stop working at the exit date. The tenant survives an exit. That tooling does not.
Backup custody deserves the most attention. If your backups live inside a platform the outgoing provider licenses, your retention history lives there too and may not be portable. Ask two questions early: where does the backup data physically sit, and what is the documented process for handing it over. If the answer is vague, treat the current retention as something you are about to lose and plan a fresh baseline with the incoming team.
Trap 5: Confusing Global Admin With Ownership, and Leaving Access Behind
Holding a global admin account is not the same as holding ownership, and an exit that does not revoke old access leaves a standing security exposure. Both halves of that sentence get missed. A company can hold global admin and still have its subscriptions transacted elsewhere. Meanwhile, modern delegated administration is the mechanism a new provider should use, granting the rights its engineers actually need rather than blanket control of your directory. That framework is also why the tenant migration in Trap 1 is unnecessary: a provider can administer your environment without owning it.
The offboarding half lingers. Old delegated relationships, standing global admin accounts, service accounts, and access to the domain registrar all need to be enumerated and closed on a named date. Our team treats this as a documented checklist item with a sign off, not a courtesy assumption, and it belongs in every managed IT engagement from the start.
How to Sequence a Clean Handover When Switching IT Providers
Switching IT providers cleanly means resolving custody first, running the two providers in parallel second, and closing out access last. The order is what prevents a coverage gap, and reversing any two steps is what creates one.
The sequencing of the technical cutover itself, including the parallel overlap window and the step by step order of operations, is covered in our guide to switching MSPs without business disruption. What follows is the licensing work that has to happen before that guide’s first step.
Build the Inventory Before Anyone Knows You Are Looking
Build the license and access inventory before giving notice, because every answer is easier to get while the relationship is intact. The inventory is a plain document, and it needs four columns: what the subscription or platform is, who transacts it, what term it sits on, and what it renews.
Cover the Microsoft subscriptions and their term types, the security and monitoring platforms, the backup product and its retention, the domain registrar, and any line of business application licensed through the provider. Add the administrative accounts and delegated relationships attached to each. Companies that do this quietly, over two or three weeks, arrive at the negotiation with facts. Companies that ask for it in the same email as their notice arrive with a request.
The counter argument is worth naming: some leaders find the discretion uncomfortable and would rather be direct from the outset. That is a defensible choice, and with a provider you trust it costs nothing. It removes a margin of safety you cannot rebuild later.
Run the Transfer and the Overlap Together
Run the billing transfer and the support overlap in the same window so neither one gates the other. The transfer request needs the outgoing partner’s approval and the overlap needs both teams working, and both are easier to hold in place at once than in sequence.
A parallel period of two to four weeks is normal. During it the incoming provider takes delegated administration and stands up its own monitoring, backup and endpoint tooling alongside what is already there, while the outgoing provider keeps answering the phone. Companies already familiar with how co-managed IT works tend to run the smoothest transitions, because the shape is one they have seen. Formal co-managed IT arrangements can carry the overlap on a defined footing rather than an informal one.
Then close it out on a fixed date. Old access revoked, old tooling uninstalled, final invoice reconciled against the inventory. Before you sign with the incoming team, the questions to ask a new IT provider about their transition process are the ones that surface whether they have done this before.
Frequently Asked Questions
Do I need a new Microsoft 365 tenant when switching IT providers?
No. In almost every provider change the existing tenant stays exactly where it is, because it is registered to your organization rather than to the provider. A new provider takes over administration through delegated rights, so your mailboxes, files and user accounts do not move and no migration is needed.
Who owns my Microsoft 365 licenses if my IT provider bought them?
You own the entitlements and the data those licenses produced, while the provider holds the transacting agreement the subscriptions were purchased under. Moving that agreement to a new provider is a billing ownership transfer, and it requires the outgoing partner to approve the request. Our Microsoft 365 administration work starts by confirming exactly where that agreement sits.
What happens if my old provider ignores the license transfer request?
The request expires after thirty days without a response, and you have to open a new one. This is why the transfer should be started while the incumbent relationship still holds commercial value, rather than after notice has been given, when there is little reason for the other side to act quickly.
Can I cancel unused licenses when I change IT providers?
Not if they sit on an annual term. An annual commitment runs to its renewal date and cannot be cancelled part way through, so the seat count and the cost travel with your organization to the new provider. Monthly term subscriptions are more flexible, which is why the inventory should record the term type for every subscription.
What should I secure before giving notice to my current IT provider?
Confirm you hold tenant ownership and at least one global admin account you control, then document every subscription with its transacting party and renewal date, the backup platform and its retention, and access to your domain registrar. Getting those answers is straightforward while the relationship is intact and difficult afterward.
The Experience Behind This Guidance
Mindcore has run provider transitions from both sides of the table, taking over environments where the licensing was clean and environments where the custody questions had never been asked. That work is where the traps above come from. It is also why we hand clients the inventory template before we talk about agreements: a company that knows what it holds negotiates from a stronger position, whoever it chooses.
Matt Rosenthal, Mindcore’s CEO, has spent more than two decades in managed IT and focuses the team on transitions where the client keeps control of their own environment throughout. That principle shapes how we scope every handover, including the ones where we are the provider being replaced. Regulated sectors need the same rigor applied to platform selection, which our work on Microsoft 365 providers for healthcare organizations covers on the compliance side.
Get the Ownership Facts Before You Commit to a Date
A provider change is a custody project wearing a technology project’s clothes. The companies that come through it without a surprise invoice or a coverage gap answered five questions before signing anything: who transacts my subscriptions, what term is each one on, where does my backup data live, who holds administrative rights today, and what does my current agreement owe me on the way out. Answer those while the relationship is intact and the transition becomes scheduling. Leave them until after notice and each one becomes a negotiation you are running from behind.
If you want a second set of eyes on your license and access inventory before you commit to a date, book a free strategy call with our team. We will walk your inventory with you, name what looks portable and what does not, and tell you plainly what a clean handover would involve. That conversation is useful whether or not we end up being your provider.
