Skip to content
home

Microsoft 365 After a Merger: Tenant-to-Tenant Migration Checklist

When one firm joins another, the deal closes on a Friday and the IT questions start on Monday. Whose email do we use? Where do the client files go? Why can't the new team see the shared calendar? Here's the order I work through when two Microsoft 365 setups become one, so nothing gets lost and clients barely notice.

Quick answer

Merging two firms' Microsoft 365 after an acquisition: connect or merge, what to inventory, moving email, OneDrive, SharePoint and Teams, the domain cutover and a day-one checklist for staff.

Daniel AwokunleDaniel AwokunleUpdated 21 November 2026 8 min read
Watch first: the whole guide in 102 secondsWatch on YouTube
Video transcript

Two firms just merged. Two sets of email, files and Teams. Here's how to make them one, without losing a single client email.

Step one. Don't move everything on day one. Connect the two setups first: shared calendars, guest access, and the sites people need.

Then pick the merge date. Every other step works back from it.

Step two. Take an inventory. Users, shared mailboxes, SharePoint sites and Teams, domains, and the apps plugged into Microsoft 365.

Step three. Clean up before you move. Archive leavers, delete empty Teams, and map every old folder to its new home.

Step four. Choose how the data moves. Microsoft's cross-tenant migration needs an add-on licence for each user. Teams chats are the hard part.

Run a pilot with three to five people first. They'll find the missing folders before everyone else does.

Step five. The domain can only live in one tenant. Move the mailboxes, remove the domain from the old tenant, add it to the new one, then update DNS. Do it on a Friday evening.

Keep the old address on every mailbox, so client replies keep arriving.

Step six. Monday morning. Send a one-page note: new sign in, Outlook, OneDrive, where the files live, and who to call.

And keep the old tenant until you're sure nothing is missing.

The full checklist is on winstack365.com. And tell me in the comments: what broke on your Monday?

1. Decide: connect first, or merge now

You don't have to move everything on day one. If the acquired firm keeps its name and office for a while, you can connect the two Microsoft 365 setups first: add the new team as guests or with Entra cross-tenant synchronization, share free/busy calendars between both, and give them access to the SharePoint sites they need.

Merge straight away when the acquired firm is dropping its name soon, its licences are about to renew, or people are already struggling with two logins. Most firms do both: connect in the first weeks, then merge on a planned date.

2. Take an inventory before anything moves

List what the acquired firm actually has. Missing one of these is the usual cause of the Monday-morning panic:

  • Users, including leavers whose mailboxes are still kept
  • Shared mailboxes and distribution lists (info@, accounts@, the ones clients write to)
  • SharePoint sites, Teams and channels, with their owners
  • OneDrive sizes per person
  • Email domains, and where their DNS is managed
  • Apps connected to Microsoft 365: practice management, client portal, e-signature, scanners
  • Retention policies and legal holds on mailboxes or sites

3. Clean up before you move

Every file you move costs time and has to be checked afterwards. Archive leavers' OneDrives, delete empty and duplicate Teams, and agree which old project sites can stay read-only instead of moving. Moving less makes the migration shorter and the new structure cleaner.

Map where things will land. Write a simple table: old site or folder, new site or library, owner. This one page settles most arguments later.

4. Choose how the data moves

Microsoft has built-in cross-tenant migration for mailboxes, OneDrive and SharePoint sites. It needs a Cross-Tenant User Data Migration add-on licence for each user you move. Third-party migration tools are the other route, and are often used when there are many sites or Teams.

Teams chat history is the hard part. Channel files live in SharePoint and move with the site, but chats and channel conversations need a third-party tool or an export. Decide early whether people really need their old chats, or whether an archive is enough.

5. Plan the email domain cutover

An email domain can only be verified in one Microsoft 365 tenant at a time. So on cutover day the order matters: move the mailboxes, remove the domain from the old tenant, add it to the new one, then update the DNS records. Plan it for a Friday evening and test sending and receiving before Monday.

Keep the old addresses working. Add the acquired firm's domain as an extra address on each person's new mailbox, so replies from clients who still use the old address keep arriving. Set an end date for it in your plan, often a year or more.

6. Day one for staff

Most support calls on Monday are the same five things. Send a one-page note on Friday that covers them:

  1. Sign in with the new account and set up multifactor authentication again
  2. Add the new account in Outlook (old cached profiles cause most email problems)
  3. Sign in to OneDrive and Teams with the new account, and stop syncing the old one
  4. Where the client files now live, with links
  5. Who to call when something is missing

7. Keep the old tenant until you're sure

Don't delete the old Microsoft 365 the week after the move. Keep it, with licences reduced, until people confirm nothing is missing and any retention or legal hold requirements are met. Accounting and law firms often have to keep client records for years, so export or migrate held data properly before the old tenant goes.

Frequently asked questions

What is a Microsoft 365 tenant-to-tenant migration?

It is moving mailboxes, OneDrive files, SharePoint sites and Teams from one company's Microsoft 365 to another's, usually after a merger or acquisition. Microsoft offers built-in cross-tenant migration with an add-on licence, and third-party tools are also common.

Can two firms share calendars and files before merging Microsoft 365?

Yes. You can share free/busy calendar information between the two organisations, add people as guests or use Entra cross-tenant synchronization, and give them access to specific SharePoint sites and Teams. Many firms do this for the first few weeks after a deal.

Will clients' emails to the old address still arrive after the merger?

Yes, if you add the old domain to the new tenant and give each person their old address as an extra address on their new mailbox. Replies to the old address then arrive in the new mailbox.

Want this done for you?

I build this for clients every week. Book a free 30-minute call and I'll tell you exactly what your team needs.

Free: the Microsoft 365 clean-up checklist

The 12 checks I run before building anything in a client's tenant: security, sharing, files and quick wins. Two pages, PDF.

Used only to send the checklist and the odd useful tip. Never shared or sold.

Daniel Awokunle · replies within a day

Tell me what's slowing your team down.

Thirty minutes, no cost, no pitch deck. You'll leave knowing exactly what to build and what it should cost.

Book a free 30-min call
  1. Step 1

    Free 30-min call

    Show me the problem. I'll tell you what I'd build and how long it takes.

  2. Step 2

    Clear quote

    A fixed price and timeline in writing, usually within a day.

  3. Step 3

    Built and handed over

    Built in your own Microsoft 365, with a walkthrough for your team.