Tenant-to-Tenant Migration

Microsoft 365 Tenant-to-Tenant Migration

After a merger, acquisition or carve-out, we move people, email, files and apps into their new tenant, and plan the cutover so work carries on.

Plan your tenant migration

When one business buys another, sells part of itself or brings its brands together, its Microsoft 365 tenant usually has to move. People, mailboxes, files, Teams and apps all go from one tenant to another, and the business can’t stop while it happens.

We plan and run that move. We find out what is in the source tenant, decide what goes and how, keep both organisations working together while it runs, and cut over so staff can sign in and work the next morning.

What Has to Move

Identities and domains

User accounts, groups and email domains, matched to the target tenant’s naming and sign-in.

Mailboxes

Email, calendars, contacts and shared mailboxes, copied ahead of time and topped up at cutover.

OneDrive

Each person’s files, with their sharing replaced by equivalent access in the new tenant.

SharePoint and Teams

Sites, libraries and teams, with permissions mapped to the new tenant’s groups.

Power Apps and flows

Apps, flows and connections that need reconnecting or rebuilding, not just copying.

Licensing

Licences in the target tenant before anyone moves, and a date to stop paying for the old ones.

Mergers, Acquisitions, Carve-Outs and Rebrands

The technical work is much the same in each case. What changes is who owns the source tenant and how long you have.

  • Merger or acquisition. The acquired business moves into the buyer’s tenant, often with a target date set by the integration plan.
  • Carve-out or divestment. The business leaves its parent group’s tenant for a new one of its own, or for the buyer’s. The seller still owns the source tenant.
  • Rebrand or consolidation. Several tenants become one, usually alongside a change of domain.

How It Works

1

Assess

inventory · dependencies

We map both tenants: users, domains, mailboxes, sites, teams, apps, flows, integrations and devices. Anything tied to the source tenant goes on a list to fix.

2

Plan

scope · waves · cutover date

We agree what moves, what is archived and what is left behind, then set the order of the move and the cutover date.

3

Coexist

cross-tenant access

We connect the two tenants so people can find each other, see calendars, chat and share files before anyone moves.

4

Pre-stage

mail · files · sites

We copy content into the new tenant ahead of time, so cutover only has to carry the changes since.

5

Cut over

domains · final sync

Usually over a weekend: we move the domain, run the final sync and switch people to their new accounts.

Working the Morning After

A migration succeeds or fails on the first morning. People need to sign in, see their email, open their files and join their meetings without calling the helpdesk. That means planning for the parts users touch: new sign-in details and multi-factor registration, Outlook and the OneDrive sync app pointing at the new tenant, devices enrolled in the new tenant’s management, and links and bookmarks that still go somewhere. We plan what staff are told before cutover, and the support they need on the first day, with you.

Carve-Outs and the Seller’s Tenant

In a carve-out, the business depends on a tenant it doesn’t own. Until the move is finished, the seller has to keep providing access, email, files and the systems around them, usually under a transitional services agreement. Every week of migration is a week of that arrangement, so the plan and its dates need to be realistic before the agreement is signed.

If you are still doing the deal, our Microsoft 365 due diligence sets out what the business depends on and what the separation will take.

Power Platform Needs Its Own Plan

Mail and files move with established tools. Power Apps and Power Automate flows don’t move that cleanly. Each connection belongs to a person in the old tenant, and apps and flows often point at sites, lists and accounts that will no longer exist. We map them, agree with their owners which are worth keeping, and reconnect or rebuild those in the new tenant. Where an app has outgrown Power Platform, the move is a good time to replace it: see Power Platform migration.

Why JFDI

Microsoft 365 Specialists

JFDI is a Microsoft ISV Success Partner and a Cloud Solution Provider (CSP). Our SharePoint work goes back to the platform’s origins, and our Microsoft cloud work to its first online services.

Migration Tooling

We helped build Casper365, the Microsoft 365 migration and automation platform, and still use it on migrations today.

From the Deal to the Move

The same team can assess the tenant before you sign and move it after completion.

Tenant-to-Tenant Migration FAQs

Moving a tenant after a deal?

Tell us about the deal, the tenants involved and your deadline, and we’ll plan the move around them.