Microsoft 365 Migration Checklist: 8 Phases for IT Teams

A Microsoft 365 migration checklist is the single list that keeps a move to the cloud on time and on budget. Most failed migrations do not fail on the day of cutover. They fail weeks earlier, when a team skips discovery, guesses at license counts or forgets a shared mailbox nobody owns.

This guide gives you the full checklist in eight phases: discovery, identity, licensing, mail, files, Teams, cutover and post-migration. Each phase lists the exact tasks, the Microsoft tools to use and the checks that tell you it is done. A printable checklist table sits in the middle so you can copy it into your project plan.

What should a Microsoft 365 migration checklist include?

A Microsoft 365 migration checklist should cover eight phases. They are discovery, identity, licensing, mail, files, Microsoft Teams, cutover and post-migration cleanup. Each phase needs an owner, a tool, a test step and a sign-off before the next phase starts.

Key takeaways

• Discovery drives everything else. Count mailboxes, data volume, devices and apps before you pick a method.
• Fix identity first. Clean Active Directory, align UPNs with email addresses and set up Microsoft Entra Connect Sync or Cloud Sync.
• Cutover mail migration supports up to 2,000 mailboxes, but Microsoft recommends 150 or fewer. Larger estates usually need hybrid.
• Use Migration Manager for file shares, Box, Dropbox, Google Drive and Egnyte. Use the SharePoint Migration Tool (SPMT) for SharePoint Server 2010, 2013 and 2016.
• Exchange Server 2016 and 2019 left support on October 14, 2025. Plan your exit if they still host mailboxes.
• Post-migration work (adoption, security baselines, decommissioning) is part of the project, not an afterthought.

What are the M365 migration steps, phase by phase?

The eight phases below follow the order most enterprise projects use. Some run in parallel, such as licensing and identity. Do not start mail or file moves until identity and licensing are signed off.

Phase 1: Discovery and inventory

Discovery tells you what you are moving and how big it is. Without it, every estimate is a guess. Collect these facts in one workbook:

• Number of user, shared, resource and room mailboxes, with sizes and archive sizes.
• Source mail platform and version, such as Exchange 2013, Exchange 2019, Google Workspace or an IMAP host.
• File data volume per share or site, file counts, and folders with deep paths or blocked file types.
• Line-of-business apps that send mail through SMTP relay or depend on on-premises Exchange.
• Devices, operating systems and how they are managed today.
• Compliance rules: retention periods, legal holds and data residency needs.

Agree on scope and success criteria at the end of this phase. Write down what is out of scope too.

Phase 2: Identity and directory sync

Identity is the foundation of Microsoft 365. Every mailbox, file and Teams chat ties back to a user object in Microsoft Entra ID (formerly Azure AD).

• Run IdFix against Active Directory to find duplicate, invalid or badly formatted attributes.
• Add and verify your domains in the Microsoft 365 admin center.
• Align each user principal name (UPN) with the primary email address so sign-in matches mail.
• Choose Microsoft Entra Connect Sync or Microsoft Entra Cloud Sync, and pick password hash sync, pass-through authentication or federation.
• Turn on multifactor authentication and baseline Conditional Access policies before users move.
• Create admin accounts that are cloud-only and protected with phishing-resistant MFA.

Phase 3: Licensing

Licensing decides which features users get on day one. Map every user group to a plan, such as Microsoft 365 E3, E5, Business Premium or a frontline F-plan.

• Match license counts to the discovery data, including shared mailboxes that exceed 50 GB or need an archive.
• Use group-based licensing in Microsoft Entra ID so new hires get the right plan automatically.
• Check that the plans you buy include Exchange Online Archiving, Intune or Defender if your design depends on them.
• Set a date to cancel old licenses and hosting contracts after cutover.

Phase 4: Mail migration

Choose the method based on source platform, mailbox count and how long you need both systems to run side by side.

• Lower the TTL on your MX and Autodiscover records a few days before cutover.
• Create migration endpoints and test them with a pilot batch of 5 to 10 mailboxes.
• Migrate shared mailboxes, delegates and calendar permissions together with the people who use them.
• Reconfigure SMTP relay for printers, scanners and apps.
• Publish SPF, DKIM and DMARC records for every sending domain.

Phase 5: File migration to SharePoint and OneDrive

Plan the target structure before you copy a single file. Lifting a messy file server into SharePoint just moves the mess.

• Map each share or folder to a SharePoint site, library or OneDrive account.
• Check limits: SharePoint and OneDrive allow files up to 250 GB and a decoded path of up to 400 characters.
• Run a scan in Migration Manager or SPMT to flag errors before the real copy.
• Use OneDrive Known Folder Move to redirect Desktop, Documents and Pictures folders.
• Run an incremental pass close to cutover to catch late changes.

Phase 6: Microsoft Teams setup

Teams often replaces several tools at once, so it needs rules before it needs users.

• Decide who can create teams, and set naming and expiration policies.
• Configure external access and guest access to match your security policy.
• Plan Teams Phone, number porting and meeting room devices if voice is in scope.
• Agree on how chat history from older tools will be handled. Most tools do not move it natively.

Phase 7: Cutover

• Freeze changes on the source systems and send users a short notice with the date and what to expect.
• Run the final mail and file sync.
• Switch MX records to Exchange Online and update Autodiscover.
• Confirm mail flow in both directions and test from mobile devices.
• Staff a help desk for the first two business days.

Phase 8: Post-migration

• Review Microsoft Secure Score and close high-impact gaps.
• Set retention policies and decide how you will back up Microsoft 365 data.
• Run adoption sessions for Outlook, OneDrive and Teams.
• Decommission old servers only after a stable period and a final backup.
• Cancel old hosting, licenses and third-party archive contracts.

Printable Microsoft 365 migration checklist

Copy this table into your project tracker. Each row needs a named owner and a sign-off date.

How do you build an Office 365 migration plan and timeline?

An Office 365 migration plan turns the checklist into dates. Microsoft now calls the service Microsoft 365, but the planning steps are the same. Follow this order:

1. Complete discovery and agree on scope with business owners.
2. Pick a migration method for mail and files based on size and source.
3. Set up identity, domains and licensing in the target tenant.
4. Run a pilot with 10 to 20 users from different departments.
5. Fix what the pilot reveals and update user guides.
6. Schedule migration batches by department or location, not alphabetically.
7. Plan cutover for a low-traffic window, such as a weekend.
8. Run hypercare for two weeks, then start decommissioning.

Timelines depend on mailbox count, data volume and network speed. Our guide on how long a Microsoft 365 migration takes breaks down typical durations by project size.

Which method should you use to migrate to Microsoft 365?

There is no single best method. The right one depends on your source system and how long you need coexistence. This table compares the main Microsoft-supported options.

If you are merging two companies, read our comparison of tenant-to-tenant vs staged migration for UAE mergers before you choose.

Common mistakes that break a Microsoft 365 migration checklist

These are the issues we see most often. Each one is avoidable with the checklist above.

• Skipping the pilot. A pilot finds broken permissions and app dependencies while the impact is small.
• Ignoring UPN mismatches. Users end up with sign-in names that do not match their email.
• Forgetting SMTP relay. Printers and finance apps stop sending mail on cutover day.
• Moving files without cleanup. Old, duplicate and orphaned data inflates time and storage.
• Leaving MFA for later. New cloud accounts without MFA are an easy target.
• Shutting down servers too early. Keep source systems until you confirm nothing is missing.
• No user communication. People who do not know what is changing flood the help desk.

For fixes to the harder problems, such as throttling and large archives, see common challenges in Microsoft 365 migration.

What should UAE and Saudi organizations add to the checklist?

Organizations in the UAE and Saudi Arabia have extra checks. These apply mainly to regulated sectors and government-linked entities.

• Confirm where tenant data is stored. Check Settings, Org settings, Organization profile, Data location in the Microsoft 365 admin center.
• Map personal data handling to the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) where it applies.
• Review sector rules, such as the UAE Information Assurance standards or the Saudi NCA Essential Cybersecurity Controls (ECC).
• Plan Arabic language settings, right-to-left display and regional time zones for mailboxes.
• Schedule cutover around the regional weekend and public holidays.

Plan Your Microsoft 365 Migration With M365 Enterprise Hub

A checklist tells you what to do. Experience tells you what will go wrong. Our team runs Microsoft 365 migration services in the UAE and KSA for mid-market and enterprise organizations, from discovery to decommissioning.

We handle Exchange Online migration with pilot batches and tested mail flow. Our SharePoint and OneDrive migration work includes structure planning and pre-migration scans. Contact us to review your current environment and get a phased plan.

Frequently Asked Questions

How long does a Microsoft 365 migration take?

A small migration of under 150 mailboxes can finish in two to four weeks. Mid-size and enterprise projects with hybrid mail, large file shares and Teams usually take two to six months. Data volume, network speed, source platform and the time needed for user communication drive the timeline more than user count alone.

What are the main Microsoft 365 migration services?

Microsoft 365 migration services usually cover discovery, identity setup and mailbox moves to Exchange Online. They also cover file migration to SharePoint and OneDrive, Teams setup, cutover support and post-migration security. Partners also handle tenant-to-tenant moves for mergers. A good provider runs a pilot first and gives you a written rollback plan.

Can I migrate to Microsoft 365 without downtime?

Yes, most migrations avoid real downtime. Mail is copied in the background and users switch over at cutover. Hybrid deployments let both systems share mail flow and calendars during the move. Users may need to restart Outlook or sign in again, so plan short support windows rather than outages.

What tool does Microsoft provide to migrate file shares?

Microsoft provides Migration Manager for file shares and cloud sources such as Box, Dropbox, Google Drive and Egnyte. It runs scans, schedules tasks and reports errors from one console. For SharePoint Server 2010, 2013 and 2016, Microsoft provides the SharePoint Migration Tool, also called SPMT.

Do I need to keep an Exchange server after migration?

It depends on how you manage identities. If you still sync users from on-premises Active Directory, you may need Exchange management tools to edit mail attributes. Exchange Server 2016 and 2019 left support on October 14, 2025, so any server you keep should run a supported version.

What is the difference between M365 implementation and migration?

Migration moves existing mail, files and users from an old system into Microsoft 365. Implementation sets up the tenant itself, including identity, security, device management, compliance and Teams policies. Most projects need both. A clean implementation before migration prevents rework and security gaps later.