Microsoft 365 migration checklist for a safer move

1. Define the business outcome and scope

Write down why the organization is moving and what a successful result looks like. The objective might be to retire an unsupported mail server, consolidate tenants after an acquisition, improve collaboration, or simplify remote access. That objective determines which workloads should move together and which can wait.

Record what is out of scope as carefully as what is included. Public folders, shared mailboxes, archives, line-of-business applications, scanners, meeting rooms, and automated email systems are easy to miss because they do not belong to a standard user account.

2. Build a reliable inventory

Inventory active and inactive users, aliases, groups, domains, mailboxes, file shares, OneDrive and SharePoint sites, Teams workspaces, applications, devices, and administrative accounts. Add an owner, data volume, sensitivity, dependency, and disposition decision to each item.

Use the inventory to remove obsolete content and resolve ownership before migration. Moving an unknown permission structure into a new platform preserves the uncertainty and makes validation harder.

• Identify legal holds, retention rules, privacy requirements, and data residency decisions.
• Map mail routing, identity synchronization, single sign-on, and application integrations.
• Confirm target licences and service limits before scheduling batches.

3. Design identity and security first

Decide how accounts will be created, matched, authenticated, and removed. Confirm user principal names, domain transfers, multi-factor authentication, administrator roles, emergency access, guest access, and the process for devices that need to enrol in management.

A migration can temporarily increase risk because people expect unusual prompts and support teams make rapid changes. Communicate how legitimate sign-in and support requests will look, and require independent verification for privileged actions.

4. Choose the migration approach and sequence

Microsoft supports different paths depending on the source platform and whether the move crosses tenants. Workload dependencies affect sequencing: email, calendars, files, permissions, Teams, and identities may need coordinated batches or a coexistence period.

Estimate time using real data volumes and a pilot rather than a simple user count. Service throttling, large mailboxes, unsupported items, and internet capacity can change migration velocity.

5. Run a representative pilot

Choose pilot users who represent different roles, locations, devices, mailbox sizes, file permissions, and application dependencies. Define acceptance criteria before starting so the team can distinguish a successful pilot from one that merely completed.

• Validate sign-in, multi-factor authentication, mail flow, calendars, delegated access, and mobile devices.
• Test file access, sharing, search, Teams meetings, printers, scanners, and integrated applications.
• Measure migration duration, support volume, and the time required to correct exceptions.

6. Prepare cutover, communication, and recovery

Write a cutover runbook with owners, times, dependencies, validation steps, decision points, and escalation contacts. State when the team will stop, correct, or roll back. Preserve the source until validation and retention requirements allow it to be retired.

Tell users what will change, when it will happen, what they must do, and where to get help. Provide short task-based guidance for sign-in, mobile setup, file locations, sharing, and reporting suspicious prompts.

7. Stabilize and govern the new environment

After cutover, compare migrated item counts, review failed objects, validate important workflows, and monitor authentication, mail flow, sharing, and security alerts. Keep enhanced support coverage until common problems and ownership questions settle.

Close the project with current documentation, licence and cost reviews, backup and recovery decisions, administrative role reviews, and a schedule for ongoing security and usage governance.