How to Migrate to Microsoft 365: Your 2026 Pro Guide

When I first led a 300‑user migration for a regional law firm, the biggest surprise was not the technology but the human side of change. A clear plan, the right tools, and a few honest conversations with end users turned a daunting project into a confidence‑building experience.

What a Microsoft 365 migration actually looks like

A tenant‑to‑tenant migration copies identities, mailboxes, files, Teams data, and compliance records from a source Microsoft 365 environment into a destination tenant. The end goal is a single, cloud‑hosted workspace where Exchange Online, Teams, SharePoint, and OneDrive share the same security policies.

Two migration philosophies: phased versus single‑event

Phased migration spreads the workload across multiple waves, minimizes user impact, and gives you time to validate each step. It’s the default for most midsize organizations that value stability over speed.

Single‑event cutover moves every mailbox, file, and Teams channel in one weekend. The upside is a fast “all‑in” transition, but any error can affect the entire user base. Large M&A deals sometimes prefer this approach to lock in a new corporate identity quickly.

Both philosophies rely on the same core prerequisites—licensing, identity readiness, and data inventory—but the planning cadence, communication rhythm, and risk‑mitigation tactics differ dramatically.

Current trends shaping migrations

Zero‑trust and conditional access

• Perimeter firewalls are being replaced by policies that evaluate device health, location, and risk score on every login.
• Entra ID now talks directly to Microsoft Defender for Cloud, allowing least‑privilege enforcement without noticeable latency.
• Conditional‑access rules can be exported and re‑imported, which simplifies the post‑migration audit.

AI‑driven collaboration

• Teams is the hub for chat, meetings, and file sharing, and Copilot now drafts emails, summarizes threads, and suggests next steps.
• Early migration lets users benefit from AI assistance as soon as the new tenant is live.
• Power Automate flows that rely on AI‑generated content need to be re‑published after the tenant switch.

Regulatory pressure

• Data‑residency rules are tightening worldwide, pushing organizations to keep data within specific geographic boundaries.
• Purview’s automated labeling, DLP, and eDiscovery are fully auditable across all workloads, making compliance easier after a migration.
• Exporting the label taxonomy before the move is now a best‑practice recommendation.

Prerequisites you can’t skip

License requirements

Both source and destination tenants must run Microsoft 365 E3 or E5. Business Premium does not include the Cross‑Tenant User Data Migration add‑on, which is required for any mailbox or OneDrive move. The add‑on is billed per user per month; calculate total cost by multiplying the number of moved users by the add‑on price and adding the base E3/E5 subscription.

Identity readiness

Export a CSV of users, groups, and UPNs from Entra ID. Run Microsoft’s conflict‑detection routine to flag duplicate email addresses or mismatched display names. Resolve conflicts before you start moving data.

Data inventory and sensitivity labels

Run a discovery script that lists mailbox sizes, hold status, and any attached sensitivity labels. Because the native orchestrator strips labels, remove them before migration and re‑apply the taxonomy in the destination tenant after cutover.

Personas you’ll meet on the road

Quick quote from Maya

“When we ran the pilot, the biggest win was seeing the same conditional‑access rules work instantly in the new tenant. It saved us weeks of manual re‑configuration.”

Step‑by‑step migration walkthrough

1. Discovery – Run PowerShell scripts to inventory mailboxes, OneDrive usage, Teams channels, and sensitivity labels. Export the results to CSV for analysis.
2. Identity mapping – Use Entra ID’s export feature, then import the CSV into the chosen migration tool. Resolve any duplicate UPNs or mismatched domains.
3. Pilot wave – Select 5‑10 % of users (preferably a low‑impact department). Assign the Cross‑Tenant User Data Migration add‑on only to this group.
4. Pilot validation – Verify mailbox item counts, OneDrive sync status, and Teams chat history. Capture screenshots of the validation reports for stakeholder sign‑off.
5. Production wave planning – Group users into logical waves (by department, geography, or data volume). Schedule MX record switches during low‑traffic windows.
6. Production migration – Execute each wave, monitor the orchestrator dashboard, and be ready to abort with a single click if a critical error appears.
7. Post‑cutover hardening – Re‑apply sensitivity labels via Power Automate, enable conditional‑access policies, and run a Purview compliance scan.
8. Final audit – Generate a migration health report, compare pre‑ and post‑migration data‑integrity percentages, and archive any remaining source‑tenant compliance records.

Visual workflow diagram

The numbered diagram below mirrors the eight‑step list, giving readers a quick visual reference.

Choosing the right migration tool

Native Microsoft tenant‑to‑tenant orchestrator

This built‑in solution runs entirely inside Microsoft 365, requires no external staging, and supports three strategies: Single‑Event, Phased, and Tenant Move/Split. It moves IPM content (mail, files, SharePoint) but does not migrate Teams compliance records or archive mailboxes.

ShareGate Migration

ShareGate offers a single‑pane UI that handles identity, mailbox, SharePoint, OneDrive, and Teams migration. It includes conflict detection, safe wave abort, and automated label re‑application. ShareGate is a separate product; it does not bundle Microsoft’s native orchestrator.

BitTitan MigrationWiz

BitTitan provides a cloud‑based service that excels at large‑scale mailbox moves and supports a wide range of source platforms. Pricing is per‑mailbox per‑month, and it includes a built‑in pre‑stage copy feature.

Quest On‑Demand Migration

Quest focuses on hybrid environments, offering granular control over Exchange, SharePoint, and Teams migrations. It adds a “dry‑run” mode that simulates the move without touching production data.

Tool comparison matrix

Executing the migration

Assigning the Cross‑Tenant User Data Migration add‑on

Upload a CSV of the users in the current wave and assign the add‑on via PowerShell. Using the SKU part number makes the script future‑proof.

Import-Csv .\wave1-users.csv | ForEach-Object {
 New-MgBetaUserLicenseDetail -UserId $_.UserPrincipalName `
 -AddLicenses @{SkuPartNumber = "CROSS_TENANT_USER_DATA_MIGRATION"}
}

Moving Teams data with ShareGate

ShareGate extracts channel messages, files, and tabs. Remember that compliance records (retention policies, eDiscovery holds) stay in the source tenant and must be archived separately.

Validation checklist after each wave

• Run Get-MsolUser to confirm identity sync.
• Compare mailbox item counts with Get-MailboxStatistics.
• Ask pilot users to verify OneDrive sync status and Teams chat history.
• Generate a checksum report for SharePoint libraries.

Real‑world trade‑offs and performance

Speed vs. risk

Phased migrations spread the load but extend the overall timeline. A single‑event cutover finishes faster but raises the impact of any failure. In the Virginia Information Technologies Agency (VITA) case, a phased approach limited user downtime to under two hours per wave while keeping costs predictable.

Cost considerations

The Cross‑Tenant User Data Migration add‑on is $2 per user per month. For a 5 000‑seat move, the add‑on alone totals roughly $30 k over three months. When you add the base E3/E5 subscriptions and a ShareGate license, the total spend can approach $150 k, which aligns with the figures reported by the VITA project.

Case study: VITA acquisition

NTT Data helped VITA consolidate three legacy tenants into a single Microsoft 365 environment. By migrating one agency at a time, they achieved 99.99 % data accuracy and cut licensing spend by 22 %.VITA/NTT Data Migration Report, 2025

Best practices and tips

Security consolidation

After migration, enforce unified DLP, encryption, and anti‑phishing policies from a single Entra ID tenant. Conditional access can now be applied across all workloads with a single policy set.

Minimizing downtime

• Enable Known Folder Move for OneDrive to keep local files syncing during cutover.
• Switch MX records during a low‑traffic window (typically 02:00–04:00 UTC).
• Use the orchestrator’s “pre‑stage” option to copy data before the final switch.

Handling sensitivity labels

Because the native orchestrator strips labels, export the label taxonomy, recreate it in the destination tenant, and run a Power Automate flow that tags items based on metadata after migration.

Common mistakes and troubleshooting

Label gaps

If an item retains a label that the destination tenant does not recognize, the migration aborts. Run Get-Label on the source tenant and compare it to the destination list before each wave.

PST migration

The new Outlook for Windows no longer opens .pst files. Migrate legacy PST content into Exchange Online using the Import/Export wizard before cutover, or use a bulk ingestion tool.

License over‑allocation

Assign add‑on licenses only to users in the active wave. Remove them as soon as the wave completes to avoid unnecessary monthly charges.

Next steps for your organization

1. Run a full inventory of mailboxes, holds, and sensitivity labels.
2. Map identities with Entra ID and resolve any conflicts.
3. Select a migration strategy: phased for most midsize orgs, single‑event cutover for large M&A.
4. Assign the Cross‑Tenant User Data Migration add‑on only to users in the current wave.
5. Execute a pilot wave, validate with checksum reports, and adjust the plan.
6. Communicate cutover dates, deliver user training, and monitor post‑migration health for at least 30 days.

With a solid discovery phase, the right toolset, and clear communication, migrating to Microsoft 365 in 2026 can be a strategic win rather than a disruptive project.