Merging Two Companies Means a Microsoft Tenant Migration

The deal is signed. Lawyers have been paid, the announcement has gone out, and everyone is talking about culture and org charts. Meanwhile two companies have two email systems, two sets of files, two lots of licences and two directories full of accounts that do not know about each other.

A Microsoft tenant migration is the technical translation of a merger, and it is consistently underestimated. Not because it is difficult in an exotic way, but because it touches everything people use all day and there is no version of it that nobody notices.

Why you cannot just merge two tenants

The instinctive assumption is that Microsoft has a button for this. It does not. A tenant is a separate world with its own identities, licences, policies and data, and there is no supported way to pour one into another as a single operation.

What actually happens is a migration: you choose one tenant to keep, then move users, mailboxes, files, groups and permissions across from the other, and decommission what is left behind. Every item moves deliberately.

That is why timelines surprise people. A small merger of two thirty-person companies is a project of weeks, not a weekend.

The three ways a Microsoft tenant migration usually goes

Absorb. The larger company keeps its tenant, the smaller one moves in. Simplest, most common, and the right answer most of the time.

Build new. Both move into a fresh tenant. More work, but sometimes the right call when both environments are messy or when the merged entity has a genuinely new identity and neither side should feel absorbed.

Coexist. Both keep their tenants and you connect them so people can find each other, share calendars and collaborate. Sometimes chosen deliberately when the businesses stay separate, and sometimes chosen by accident because nobody decided. The second version is expensive: two of everything, forever.

Decide which of the three you are doing early, and write down why. Merger and acquisition IT work goes wrong most often when this choice is never actually made and the default becomes coexistence by neglect.

What a Microsoft tenant migration actually moves

The list is longer than people expect, and most of it needs a decision rather than just a copy.

• Identities. Every account, plus the question of what the new email addresses look like and whether the old domain keeps receiving mail.
• Mailboxes. Mail, calendars, contacts, shared mailboxes and rules. Mailbox migration is well-trodden ground, but calendar permissions between colleagues break easily and are noticed immediately.
• Files. SharePoint sites and OneDrive contents, along with the permissions on them. This is usually the largest volume and the slowest part.
• Teams and groups. Channels, membership, and the files attached to them. Chat history is the awkward one, since it does not move cleanly and people expect it to.
• Devices. Laptops enrolled in one tenant have to be moved, which for some devices means a rebuild.
• Licences. Two Microsoft 365 agreements, different renewal dates, possibly different plans for people doing the same job.
• Applications. Anything that signs in through Microsoft has to be reconnected on the other side.

The parts people forget

Three things reliably get missed.

Email routing during the transition. For a period, some people are on one side and some on the other. Getting mail to flow correctly between them, and from outside, is fiddly and highly visible when it goes wrong.

Domain migration and DNS. A domain can only be verified in one tenant at a time. Sequencing this incorrectly means an outage on the most conspicuous system you own.

Permissions history. Files move, but the reasoning behind who could see what does not travel with them. A Microsoft tenant migration is an unusually good moment to review access rather than faithfully recreating years of accumulated sharing.

What it feels like for staff

Be straight with people. On migration weekend, they sign out of everything and sign in again with a new address. Some will need help. Old chat threads may not come across. Shared calendars will need re-adding.

Announced in advance, this is an inconvenient Monday. Sprung on people during a period when they are already anxious about a merger, it becomes evidence that nobody has a plan.

Let us run the technical merger

Mergers are demanding enough without IT becoming the thing everyone complains about. And because a Microsoft tenant migration happens once, it is not work your team will get better at by doing it.

At EvolvingDesk we run these end to end. We inventory both environments, recommend which tenant to keep and why, sequence the domain and mail routing so nothing goes dark, move mailboxes and files in planned waves, rationalise the licences across both companies, and support your people through the weekend they actually notice.

You get one company on one system, with an environment that reflects how the merged business works rather than two histories bolted together.

Merger or acquisition on the horizon? Plan a call early. The decisions are much cheaper before the deal closes than after.

Read more

• What is Microsoft Copilot and how can your business use it
• What happens to your data when an employee leaves
• Managed IT services at EvolvingDesk

Background: the Microsoft documentation on tenant-to-tenant migrations and the guidance on cross-tenant mailbox moves.