Microsoft 365 migration between companies: mail, files and identities

Plan a Microsoft 365 tenant migration with inventory, identity mapping, licensing, coexistence, pilot testing, cutover and recovery.

01

Define the outcome before choosing a tool

An acquisition or divestiture is more than copying mailboxes. Decide who joins which organization, which information remains accessible, and when each team becomes independent. In this fictional example, Atelier Nord transfers a team to Atelier Sud. Business owners approve users and workspaces before configuration. This guide prepares a project; it does not replace a detailed assessment of both environments.

02

Inventory: build a dependency matrix

For each person, record source and target identity, primary address, aliases, shared mailboxes, delegation, archive, OneDrive, groups and applications. For each workspace, record owner, volume, permissions, external sharing, labels, automation and retention. Include Intune devices, application authentication, SMTP printers and service accounts. Protect the inventory as sensitive administrative information.

03

Read-only collection

In an Exchange Online session already connected to the intended tenant, these reads inventory recipients and relationships. Verify the connected tenant before collection. Store sensitive results securely. These commands do not prove migration eligibility; volumes, holds and permissions require additional checks.

PowerShell — lecture seule / read-only
# Existing authenticated Exchange Online session; no changes
Get-ConnectionInformation | Select-Object UserPrincipalName, TenantID
Get-EXORecipient -ResultSize Unlimited |
  Select-Object DisplayName, PrimarySmtpAddress, RecipientTypeDetails
Get-AcceptedDomain | Select-Object DomainName, DomainType
Get-OrganizationRelationship | Select-Object Name, Enabled, DomainNames
04

Identity: create an explicit mapping

The same address does not guarantee the same identity. Approve a source-to-target mapping with object identifiers, groups and guest accounts. Entra cross-tenant synchronization supports collaboration but still depends on the source tenant for authentication: it is not a migration tool. Separately plan MFA, Conditional Access, emergency access, consent and devices. In hybrid environments, establish attribute authority before changing a UPN.

05

Mail: prepare the target and coexistence

Native Exchange moves require correctly prepared target MailUsers and a per-user Cross Tenant User Data Migration licence, alongside applicable subscriptions. Holds can block moves. After completion, the source mailbox is not a recovery copy. Never remove a hold merely to unblock the project without a decision from the responsible authority.

06

Files: OneDrive, SharePoint and Teams have different scopes

Native OneDrive moves are one-time operations without incremental passes; the user licence also covers mailbox migration. SharePoint uses a separate shared-data offering, currently for Enterprise Agreement customers, licensed per 100 GB. Native moves cannot merge into an existing target site. Moving a Teams-connected site does not by itself migrate Teams conversations or structure. Validate the selected tool for each content type.

07

Licensing, permissions and method selection

Compare workload-specific tools with Migration Orchestrator and, where needed, a partner solution. Obtain written confirmation of supported features, editions, clouds and licensing before committing to a date. Use supported Exchange Online and SharePoint Online modules. Separate inventory reads from configuration: appropriate Exchange RBAC, SharePoint roles for relevant operations, and an authorized consent approver. Avoid a permanent Global Administrator account for the entire project.

08

Domain and cutover: prepare an ordered runbook

Inventory domain references in users, groups, applications and services, then document tenant transfer prerequisites. Plan temporary routing addresses and test communication between moved and unmoved users. Assign ownership for DNS, MX, Autodiscover, SPF, DKIM and DMARC. Lowering a TTL does not remove existing caches. Preserve anti-phishing protection and verify authorization of new senders.

09

Pilot: test business workflows, not just counts

Select a small group with a shared mailbox, delegation and shared documents. Validate internal and external mail, calendars, replies to old messages, Outlook, mobile, search and document access. Also test an identity that must not have access. Compare permissions and file versions, and obtain owner acceptance. Use pilot throughput and incidents to estimate waves; account count alone does not guarantee a duration.

10

Changes and rollback: define the decision point

Cross-tenant relationships, consent, migration batches and DNS edits are changes. Execute them within an approved window with pilot scope, logs and stop criteria. Before finalization, document what can still be paused. After a move, do not assume reversing DNS restores data or identity. Prepare workload-specific recovery with tested backup, handling of new writes, and vendor support where required.

11

Deliverables and project closure

Require an identity mapping, exception register, timed cutover runbook, validation evidence and recovery procedure. Provide additional support after each wave. Remove temporary secrets and permissions only after validating their dependencies. Retain evidence under the approved policy and retire source services when authorized. Infrastructure and Microsoft 365 consulting can turn the inventory into an executable plan.

12

Microsoft sources