The hidden cost of a bad Microsoft 365 tenant migration
A Microsoft 365 tenant migration moves an organisation’s entire Microsoft 365 environment, including email, files, user identities, permissions, and devices, from one Microsoft tenant to another. It usually happens after an acquisition, a demerger, a rebrand, or a change of IT provider. The point most buyers miss is that the headline quote is rarely the real cost. When a migration is rushed or under-planned, the true cost turns up later as downtime, lost data, broken access, and weeks of re-work that never appeared on the original figure. This article sets out where those costs hide and how to avoid them. As a Microsoft Direct Cloud Solution Provider accredited with the Microsoft Support Service Designation, an accreditation held by only a handful of partners worldwide, Lanmark plans and runs these moves with direct Microsoft support behind the work.
The intention here is not to sell you a migration. It is to help you understand the risk before you commit to one, so that whoever carries it out, the money you spend buys a clean result rather than a clean-up job.
What a tenant migration actually involves
It helps to be clear about what is being moved, because the scale is easy to underestimate. A tenant migration is not one task, it is several interconnected ones happening at once.
The move includes mailboxes and their full email history, OneDrive and SharePoint files, Teams and the structures that sit beneath them, user identities and passwords, permissions and sharing links, device enrolment, and licensing. Think of it less like moving boxes between two offices and more like relocating a building where the plumbing, wiring, and locks all have to work on the first morning in the new premises.
The reason this matters is that the elements depend on one another. Identities are the foundation. If a user’s identity does not come across cleanly, they cannot log in, which means they cannot reach their files, which means the carefully migrated documents are worthless until the identity is fixed. A single mistake in one layer cascades into the others. That interdependence is what turns an apparently routine project into a high-stakes one.
When tenant migrations happen, and why the trigger matters
Tenant migrations are almost always driven by a business event rather than a technical decision, and the nature of that event shapes the risk.
The most common trigger is post-acquisition integration. Two organisations, two Microsoft estates, two sets of habits, and a deadline set by the deal rather than by the IT team. A demerger or carve-out is the mirror image, splitting one tenant into two while keeping both halves running. A rebrand or domain change forces a move when the company name and email addresses have to change. And a change of IT provider often means lifting the environment out of a tenant the outgoing provider controls.
The common thread is that the timeline is imposed from outside. When a deal completes on a fixed date, or a brand launches on a set day, the migration has to fit around it. An externally imposed timeline is precisely where corners get cut, and cut corners are where the hidden costs begin.
Where the real costs hide
This is the part that catches businesses out. The migration project has a price, and that price is visible. The costs below are the ones that do not appear on the quote, and they are usually larger than the quote itself.
| Hidden cost | What it looks like in practice |
|---|---|
| Downtime | Staff unable to send email or reach files during and after the cutover. Every hour of it is paid for in salaries and stalled work. |
| Lost or orphaned data | Email history, shared files, or permissions that do not come across cleanly, and are sometimes not noticed as missing until someone needs them. |
| Broken access and permissions | People locked out of what they need. Worse, the wrong people keeping access they should have lost. |
| Re-work and rollback | Fixing a failed migration costs more than doing it once, properly. You pay twice, and the second attempt runs under pressure. |
| Lost productivity tail | The weeks after cutover where small breakages, a broken link here, a missing calendar there, quietly drain hours across the whole business. |
| Security exposure | Misconfigured identity or conditional access during the move opens a window that attackers are known to watch for. |
| Reputation and client impact | Bounced email and missed deadlines are visible to clients. That cost does not sit on your books, it sits on your relationships. |
Read together, these explain why a migration that looked cheap can become the most expensive IT project a business runs in a given year. The saving on the quote is real. It is just smaller than the bill that follows a rushed job.
Why migrations go wrong
The failures are predictable, which is the good news, because predictable problems can be planned out. Almost every hidden cost above traces back to one of a short list of causes.
The first is under-planning, and specifically no pre-migration audit, so nobody knows exactly what is being moved until something breaks. The second is an unrealistic timeline set by the corporate event rather than the work. The third is a big-bang cutover with no pilot, so the first time anyone tests the migration is when the whole company depends on it. The fourth is treating identity and permissions as an afterthought rather than the foundation. And the fifth is having no rollback plan, so when something does go wrong there is no clean way back.
None of these is exotic. They are the ordinary consequences of doing a complex job in a hurry, which is why the honest advice is to protect the planning time even when the deadline is fixed.
How to migrate without the hidden costs
The constructive version of the list above is short and practical.
Start with a proper pre-migration audit that establishes what exists, what is actually used, and what can be retired before the move rather than carried across as clutter. Plan identity and permissions first, because they are the foundation everything else stands on. Run a phased or piloted cutover, moving a small group first, learning from it, and then scaling, rather than switching everyone at once. Keep a tested rollback position so there is always a way back. And communicate clearly with users about what is changing and when, because a well-briefed team absorbs disruption that an unprepared one turns into a support queue.
For the practical, step-by-step version of this, our companion Microsoft 365 to Microsoft 365 migration readiness checklist walks through the pre-migration audit and cutover sequence in detail. The National Cyber Security Centre’s guidance on managing change securely is also worth reading for the security side, since the migration window is one of the moments an environment is most exposed. Microsoft’s own cross-tenant mailbox migration documentation sets out how the mailbox move is handled at a technical level.
How Lanmark approaches tenant migrations
We treat a tenant migration as a planning problem first and a technical one second, because that is where it is won or lost.
Lanmark is a Microsoft Direct CSP partner, which means we hold a direct billing and support relationship with Microsoft rather than working through a distributor. We are also accredited with the Microsoft Support Service Designation, held by only a handful of partners worldwide, which gives us a direct line to Microsoft’s support when a migration needs it. In practice that means a pre-migration audit, a phased cutover, identity and permissions planned first, and a tested rollback position, all with Microsoft support behind the work rather than a ticket in a global queue.
Because a migration is also the natural moment to check that licensing is right, we fold a Microsoft 365 licence review into the planning, so you are not carrying licences you no longer need into the new tenant. The principle throughout is simple: the cost of doing it properly is almost always lower than the cost of doing it twice.
Frequently asked questions
What is a Microsoft 365 tenant migration?
A tenant migration moves an organisation’s entire Microsoft 365 environment, including email, files, user identities, permissions, and devices, from one Microsoft tenant to another. It is most common after an acquisition, a demerger, a rebrand, or a change of IT provider. Because these elements are interconnected, a tenant migration is more involved than moving a single mailbox or a set of files.
How much does a Microsoft 365 tenant migration cost?
The visible cost is the migration project itself, which varies with the number of users, the volume of data, and the complexity of the environment. The cost that catches businesses out is the hidden one: downtime, lost data, broken access, and re-work when a migration is rushed or under-planned. A well-planned migration costs more upfront than a quick one but far less than fixing a failed one.
Why do tenant migrations go wrong?
The most common causes are under-planning, no pre-migration audit, an unrealistic timeline driven by a corporate deadline, no pilot or phased cutover, identity and permissions treated as an afterthought, and no rollback plan. Almost every hidden cost traces back to one of these.
How long does a Microsoft 365 tenant migration take?
It depends on the size of the estate and the amount of data, but the timeline that matters is the planning, not just the cutover. A migration that is properly audited, piloted, and phased takes longer to plan and less time to recover from. A rushed big-bang cutover can appear faster and then cost weeks in clean-up.
Can we avoid downtime during a tenant migration?
You can minimise it. A phased or piloted cutover, identity and permissions planned first, and clear user communication keep disruption low. Some change is unavoidable, but the difference between a planned migration and a rushed one is usually the difference between a few managed hours and several disrupted days.
Does Lanmark handle Microsoft 365 tenant migrations?
Yes. Lanmark is a Microsoft Direct CSP partner accredited with the Microsoft Support Service Designation. We plan and execute tenant migrations with a pre-migration audit, a phased cutover, identity and permissions planned first, and a tested rollback position, with direct Microsoft support behind the work.
Talk to us before you migrate, not after
The best time to involve an experienced partner in a tenant migration is at the planning stage, before a timeline is locked and before the first cutover. If an acquisition, a rebrand, or a change of provider means a Microsoft 365 tenant migration is on your horizon, get in touch and we will help you scope it properly. You can also read more about our wider Microsoft cloud services.
Lanmark is a Microsoft Direct CSP partner accredited with the Microsoft Support Service Designation, an accreditation held by only a handful of partners worldwide.