We are currently revamping our website to improve user experience. During this time, some pages or links may not function as expected. We regret any inconvenience and appreciate your patience and continued support.

How to Migrate Email to Microsoft 365 Step by Step

For teams running IT in India or the GCC, this guide covers moving mailboxes from Exchange or a different mail platform to Microsoft 365 in ten steps, each with a named output and owner: inventory, tenant and domains, DNS and the coexistence period, method, pilot, group moves, the MX switch, Outlook and phones, files, and retiring the old server. No tools and no prices.

To learn how to migrate email to Microsoft 365, list every mailbox and set up domains and DNS. Then move a pilot group. Then move the other groups, switch MX, reconnect Outlook and phones, and retire the old server. Until you switch the MX record, mail still arrives at the old server. So both systems run side by side for a while.


Last reviewed 2026-11-16 by Manish Sharma.

The move here starts on an Exchange server or another mail platform. Files also take one step near the end. To migrate email to Office 365 in a set order, read on. Each step also has an output and an owner. For the wider job, see planning a mailbox and file move with us.

How to Migrate Email to Microsoft 365: 10 Steps at a Glance

The table below gives each of the ten steps, in four stages, its output and owner. The email migration process stays the same at small and large size, but the waves get longer.

Step Output Owner
1. List every mailbox, archive and rule Full inventory IT lead
2. Set up the tenant, domains and licenses Verified domain, users IT lead
3. Prepare DNS and the coexistence period DNS record list DNS owner
4. Pick the move method Method named IT lead
5. Move a pilot group Signed pilot Team head
6. Move one group at a time in waves Matched item counts IT lead
7. Switch MX and watch mail flow Mail arriving in Microsoft 365 DNS owner
8. Reconnect Outlook and phones Working profiles IT lead
9. Move files to OneDrive and SharePoint Files in place Team head
10. Decommission the old server Retired server IT lead
1
Prepare

Steps 1 to 4 list the mailboxes, set up the tenant and DNS, and then pick the method.

2
Pilot and waves

Steps 5 and 6 move a pilot group, then one group at a time.

3
Switch-over

Steps 7 to 9 switch MX, reconnect Outlook and phones, and move files.

4
Retire

Finally, step 10 decommissions the old server after sign-off.

Ten steps in four stages to migrate email to Microsoft 365: prepare, pilot and waves, switch-over, then retire the old server
Ten steps, four stages.

Before Any Mailbox Moves: Prepare to Migrate Email to Microsoft 365

Four steps set the ground before the first mailbox moves.

Step 1: List Every Mailbox, Archive and Rule

Record user and shared mailboxes, delegates, groups, forwarding and inbox rules. Also record archives, PST files and public folders, with sizes and item counts. Teams that ask how to migrate a shared mailbox to Office 365 start here. If you leave a shared mailbox off the list, it does not move.

Groups need an empty mail-enabled security group in Microsoft 365 before a cutover move. Also, take any delegate that stays behind out of the object first. Both come from Microsoft’s cutover migration guide, dated 28 March 2024. We last checked the pages linked in this guide on 16 November 2026. Each link shows the date its page carries.

  • Output: a full inventory.
  • Owner: the IT lead.
  • Done when: every mailbox, group and rule has a line and a named owner.
A missing mailbox does not move

Every mailbox, group and rule needs a line in the inventory before any move starts.

Step 2: Set Up the Tenant, Domains and Licenses

Create the Microsoft 365 tenant. Then verify your domain with a TXT record at your DNS host, the route the cutover page lists. Create the users and assign licenses, as Microsoft Learn says you must still assign licenses to users whose mailboxes move. We give no license figures here.

  • Output: a verified domain and users.
  • Owner: the IT lead.
  • Done when: every user to be moved has an account and a license.

Step 3: Prepare DNS and the Coexistence Period

Note every MX record and its TTL, which is the time other systems keep the old answer. Lower the TTL to the value Microsoft gives before the switch: 3,600 seconds or less on each record. Decide how mail flows both ways while both systems run.

  • Output: a list of DNS records with their TTLs.
  • Owner: the DNS owner.
  • Done when: you have lowered the TTLs and agreed the mail flow between systems.
Lower the TTL early

Lower it well before the switch, because other systems keep the old answer until it runs out.

Step 4: Pick the Move Method

Microsoft Learn names the routes in its guide to ways to migrate multiple email accounts, dated 13 July 2026: cutover, staged, hybrid and IMAP. Choosing between them is a separate topic.

  • Output: the method named.
  • Owner: the IT lead.
  • Done when: the team has written down and agreed the method.

Key Takeaway Prepare in four steps: inventory, tenant, DNS and method, before any mailbox moves.

How to Migrate Email to Microsoft 365 With a Pilot, Then in Waves

Start with a few people, then move the rest by team.

Step 5: Move a Pilot Group

Pick a small group across roles, including one shared mailbox and one delegate. Test send, receive, calendar and phone mail before you move on. Signisys’s working view is that a pilot of only one kind of user hides the problems that shared mailboxes and delegates cause. We reach this because those two depend on rights that a simple mailbox does not use.

  • Output: a signed pilot.
  • Owner: the team head.
  • Done when: the pilot users sign off.
Include a hard case

Put one shared mailbox and one delegate in the pilot, so the problems show on a small group.

Step 6: Move One Group at a Time in Waves

Group by team and shared mailbox instead of alphabetically. Match item counts per group. In an IMAP move, items that retention policies removed show as missing, as the IMAP migration guide, dated 12 March 2024, says. Teams searching for mailbox migration to Office 365 steps will find that this loop repeats, because every wave follows it.

  • Output: matched item counts per group.
  • Owner: the IT lead.
  • Done when: each group’s counts match, apart from expected gaps.

Switch-Over Day as You Migrate Email to Microsoft 365

Three steps run on or near the day when mail routing changes.

Step 7: Switch MX and Watch Mail Flow

Point MX at Microsoft 365. Other systems can take up to 72 hours to recognize the changed record. So mail may land in both places for a while. Then test mail in both directions.

  • Output: mail arriving in Microsoft 365.
  • Owner: the DNS owner.
  • Done when: test mail passes both ways from outside senders.

Step 8: Reconnect Outlook and Phones

Set an Autodiscover DNS record so Outlook and phones find the new mailbox. Also send users a short note on how to sign in, and who to call.

  • Output: working profiles.
  • Owner: the IT lead.
  • Done when: pilot and first-wave users read mail on Outlook and phone.

Step 9: Move Files to OneDrive and SharePoint

Move personal files to OneDrive and team files to SharePoint, then check permissions. The three Microsoft Learn pages cited here do not cover file limits. So ask each team which files it needs, then test opening them.

  • Output: files in place.
  • Owner: the team head.
  • Done when: each team confirms it can open its files.
Switch-over checks: switch MX, test mail both ways, reconnect Outlook and phones, then wait 72 hours before deleting the batch
Wait before you retire anything.

After You Migrate Email to Microsoft 365: Retire the Old Server

One step closes the move.

Step 10: Decommission the Old Server

Wait at least 72 hours after the MX change before deleting the batch, as Microsoft’s cutover page says. Keep the old server read only until the owner signs off, then retire it.

  • Output: a retired server.
  • Owner: the IT lead.
  • Done when: the owner signs and the wait has passed.

Four Slips When You Migrate Email to Microsoft 365

Four slips repeat across moves, while what breaks when a step is skipped has its own guide.

  1. Skipping the inventory. Do Step 1 in full.
  2. Switching MX before the last group is ready. Finish Step 6 first.
  3. Running no pilot with a shared mailbox. Include one in Step 5.
  4. Retiring the old server before sign-off. Wait for Step 10.

Key Takeaway Slips come from skipping the inventory, the pilot or the wait. Each skip removes a safety check, so keep all three.

What Comes After the Move

Once the old server is retired, you have a working mail system and a record of how you got there. Two questions sit outside this guide.

This guide names no prices.

Signisys provides these services and partners with Microsoft. See workplace and device management solution and device lifecycle and user support services. A working session covers your mailbox list, DNS records and group plan, and promises no result or price. No charge, with a fixed scope.

Book a consultation
Plan your mailbox move with us

How to Migrate Email to Microsoft 365: FAQ

How do you move one mailbox, or a handful, to Microsoft 365?

Use the same order at small size, but expect fewer waves. For how to migrate a mailbox to Office 365 by IMAP or user import, read Microsoft’s pages on the routes and on IMAP. Expect mail only on IMAP.

Can staff keep working while mailboxes move?

Yes. The old server keeps receiving mail until the MX record changes. Also tell users which day their group moves.

How to Migrate Email to Microsoft 365: Who Should Own Each Step?

The IT lead owns the plan, the DNS owner owns the records, and team heads sign off the pilot and each group. Signisys’s working view is to name each owner before Step 1 starts.

What should we tell users before their group moves?

The day, what to expect in Outlook and on phones, how to sign in and who to call.

Newsletter

Security Insights, Delivered.

Practical, vendor-neutral analysis of threats, tools, and architecture decisions.

Book a Consultation

A practice principal will contact you within 1 business day.

Thank you! A Signisys principal will be in touch within 1 business day.