Microsoft 365 migration playbooks

Microsoft Entra has no "move user" button. This guide shows how to use cross-tenant access settings and cross-tenant synchronisation for coexistence, how to turn synced accounts into real internal users when you migrate, and how to rebuild groups, licences, MFA and Conditional Access in the target tenant.

Pick the right method for your Exchange version and mailbox count, set up hybrid or a cutover batch, move mailboxes and public folders, then switch MX and Autodiscover to Exchange Online.

A device enrolled in one Intune tenant cannot simply be pointed at another. This guide covers the documented path for each platform: rebuild the target configuration, move Autopilot and Apple registrations, back up BitLocker keys, then wipe or retire and re-enrol on cutover day.

Microsoft has no native tool that moves a Microsoft 365 group or its Planner plans between tenants. This guide shows how to inventory them, recreate each group with its owners, members and settings, and rebuild plans with the Microsoft Graph Planner API.

The complete runbook for Microsoft's native cross-tenant mailbox migration: the licence, the migration app and consent, organisation relationships in both tenants, correctly stamped MailUsers, batches, completion and the day-one fixes for Outlook and mobile.

What a tenant-to-tenant move involves, which workloads Microsoft's native tools cover, the order to do the work in, the licences you need and how the domain cutover weekend runs. Each workload links to its own detailed runbook.

Microsoft Forms has no tenant-to-tenant move. Inside one tenant you move a form to a group; across tenants you copy the form with a duplicate link and keep the responses in Excel. This guide covers both.

Microsoft's cross-tenant OneDrive migration moves each account inside the Microsoft cloud and leaves a redirect behind. This runbook covers the trust between tenants, the identity mapping file, the compatibility check, scheduling up to 4,000 moves and the clean-up afterwards, plus when a third-party tool is the better choice.

Power BI content is rebuilt, not moved, when you change tenants. This guide covers the inventory, .pbix downloads and their limits, gateways, workspaces and roles, publishing, refresh, deployment pipelines and apps, with the MicrosoftPowerBIMgmt cmdlets and REST API calls for each step.

Bulk import Outlook PST files into users' mailboxes or archive mailboxes with the Microsoft Purview Import service, from collecting the files to turning off retention hold afterwards.

Microsoft's cross-tenant SharePoint migration moves whole sites, including group-connected and Teams sites, from one tenant to another and leaves a redirect behind. This runbook covers who can use it, how to size the licence, how to precreate Microsoft 365 groups the only way that works, the identity map, the move commands and what you rebuild afterwards.

Export Slack, import channels and history with Microsoft's Slack to Teams Migration Tool, replace apps and webhooks, and get people working in Teams.

Teams content is split across several services. Files move with SharePoint and OneDrive, chats and meetings now have Microsoft cross-tenant tooling, and teams and channel conversations still need rebuilding or a third-party tool.

Checklist for moving Exchange Server to Exchange Online: choosing cutover, staged or hybrid, hybrid prerequisites, migration batches, MX and Autodiscover.

A go/no-go checklist for Microsoft 365 migration cutover weekends: batch status, licences, DNS readiness, rollback, support roster and sign-off criteria.