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.

Email Migration Checklist: Before, During and After the Move

An email migration checklist for IT heads moving mailboxes and files to Microsoft 365, in three stages of four checks. Each check says what passes, who signs it off and which record backs it. The checks cover counts, domain and DNS, licenses, a pilot, item counts, mail flow, files, MX, SPF, DKIM and DMARC, Outlook and phones, and the old server. No tools named.

This email migration checklist covers counts, domain, DNS, licenses and a pilot before the move; item counts, mail flow and files during it; and MX, SPF, DKIM, DMARC, Outlook and phones, and the old server after. Each check passes only with a named sign-off and a record.


Last reviewed 2026-11-16 by Manish Sharma.

The scope is mailboxes and files going to Microsoft 365 from an Exchange server or a different mail platform. Moving mail and files with Signisys is one route there. However, what follows is a set of checks, not the order of work. Each check shows a status of Pass or Not yet. A stage ends only when its four checks read Pass.

Email Migration Checklist at a Glance

Twelve checks sit in three stages, and each has one signer.

Stage Check Signed by
Before Mailbox, group and delegate counts recorded Mail admin
Before Domain verified, DNS access confirmed DNS owner
Before Licenses assigned, backup taken IT head
Before Pilot group named, move method chosen IT head with pilot team head
During Pilot users confirm daily work Pilot team head
During Source and target counts agree per group Mail admin
During Mail flows both ways before the MX change Mail admin
During Team files and permissions sampled Team heads
After MX pointed at Microsoft 365, wait allowed DNS owner
After SPF, DKIM and DMARC records set DNS owner with security lead
After Autodiscover set, desktops and phones reachable Support lead
After Old server kept until sign off IT head

Read the table down a stage, not across.

Three stages of four checks each, from counts and DNS before the move to the old server after it
Four checks in each stage, each with one signer.

Key Takeaway A stage closes only when all four of its checks read Pass.

Pass or Not Yet

Each check shows one of two states. Pass means the condition is met, the named person has signed and the team has stored the record. Anything else reads Not yet.

Before the Move: Email Migration Checklist

Nothing moves until all four of these checks read Pass.

Mailbox, Group and Delegate Counts Recorded

List the user and shared mailboxes, aliases, groups, delegates, forwarding and inbox rules, and archives. Give counts and sizes for each.

Groups also need preparation. Microsoft’s cutover migration guide (page dated 28 March 2024, updated 28 July 2026) says that, to keep security groups in Microsoft 365, an empty mail-enabled security group must exist before the move starts. It also says that anyone staying behind as manager or delegate must come off the objects that move.

  • Passes when: the mail admin has counted every mailbox, group and delegate, and the people who stay are outside the moved objects.
  • Signed by: mail admin.
  • Record kept: the inventory with counts and sizes.

Domain Verified and DNS Access Confirmed

Add the domain to Microsoft 365 and verify ownership. Microsoft Learn on adding DNS records (page dated 23 April 2026) describes the steps. Then name the person who can change DNS records and confirm that person is reachable on switch day.

Note every MX record and its TTL. The cutover guide recommends 3,600 seconds or less on each, ahead of the move. The DNS records page adds that Exchange Online supports TTL values of under 6 hours. If an SPF record exists, keep it and join it with the Microsoft 365 values into one record.

  • Passes when: ownership shows verified, the DNS owner has a name and is reachable, and the TTL is lower, or a note explains why not.
  • Signed by: DNS owner.
  • Record kept: a DNS snapshot before and after the TTL change.

Licenses Assigned to Every User, Backup Taken

Assign a license to every user who moves, in the Microsoft 365 admin center. The cutover guide says an unlicensed mailbox stops working once the 30-day grace period is over.

Take a backup or export of the source mail before the first group moves. A copy that exists only on the old server is not a backup.

  • Passes when: every moving user shows an assigned license and the team has restored the backup once as a test.
  • Signed by: IT head.
  • Record kept: the license report and the backup log.
Test the Backup

A backup that nobody has restored is only a hope. Restore one mailbox before the first group moves.

Pilot Group Named and Move Method Chosen

Choose a pilot that spans roles and includes one shared mailbox and one delegate, so the awkward cases surface early.

Name the method in one line: cutover, staged, hybrid or IMAP. An IMAP move carries mail folders only, not contacts, calendars or tasks. Microsoft’s IMAP migration page (page dated 12 March 2024, updated 28 July 2026) says so. Choosing between the routes is set out in when each move method fits.

  • Passes when: the pilot users have names, the method has a written line and the people who agreed appear on the list.
  • Signed by: IT head and pilot team head.
  • Record kept: the pilot list and the method note.

The Email Migration Checklist During the Move

These four checks run while mail is moving, and each reads Pass or Not yet on the day.

Pilot Users Confirm Daily Work

Pilot users send, receive, open the calendar, use the shared mailbox and check a phone. Each item gets Pass or Not yet.

Feed the result back into the plan before the first full group moves. Then the team fixes a pilot gap once, instead of everyone finding it.

  • Passes when: every pilot item reads Pass, or each Not yet has a fix and a retest.
  • Signed by: pilot team head.
  • Record kept: the pilot test list with dates.

Source and Target Counts Agree per Group

For each group, compare the number of items in the source and the target mailbox, mailbox by mailbox. However, any gap needs an explanation in writing, not a shrug.

If the move uses IMAP, switch off retention and archival policies on the source first. The same Microsoft page says items those policies delete or move to archive show up as missing.

  • Passes when: counts agree for every mailbox in the group, or the mail admin has explained each gap.
  • Signed by: mail admin.
  • Record kept: a count report per group.

Mail Flows Both Ways Before the MX Change

The cutover guide states that mail for a moved user still lands on the old server while the MX record is unchanged. Send test messages each way between users who have moved and users who have not.

If a moved user cannot reach a colleague on the old side, or the reverse, the check reads Not yet.

  • Passes when: test messages arrive both ways, with no bounce and no long delay.
  • Signed by: mail admin.
  • Record kept: the test message log.

Team Files and Permissions Sampled

Personal files go to OneDrive and team files to SharePoint. Sample the sharing and folder permissions for each team, and open files as a different user would. For the file move itself, Microsoft documents a file share migration tool in the SharePoint admin center (page dated 29 April 2026).

  • Passes when: each team’s sample opens for the right people and stays closed to the rest.
  • Signed by: team heads.
  • Record kept: a permission sample per team.

After the Move: Email Migration Checklist

The last four checks close the move. The first of them depends on DNS.

MX Pointed at Microsoft 365, Wait Allowed

Point the MX record at Microsoft 365. Microsoft’s cutover guide says customer and partner mail systems may need up to 72 hours to see the new record. The check therefore builds in that wait.

The same guide says you can raise the TTL again after the switch.

  • Passes when: a DNS lookup shows the new MX, and mail from outside arrives in the new mailboxes.
  • Signed by: DNS owner.
  • Record kept: a DNS lookup with the date and time.

SPF, DKIM and DMARC Records Set

Three records protect the domain’s mail.

  • One SPF TXT record carries the Microsoft 365 value and any sender still in use. Keep a single SPF record, as the DNS records page says.
  • DKIM CNAME records sign mail for the custom domain.
  • A DMARC TXT record starts at p=none. It then moves to p=quarantine and p=reject once the reports look clean, per Microsoft Learn on DMARC setup (page dated 3 July 2026). We last checked these pages on 16 November 2026.
  • Passes when: all three records resolve and the first DMARC report arrives.
  • Signed by: DNS owner and security lead.
  • Record kept: the three records and the first DMARC report.

Autodiscover Set, Desktops and Phones Reachable

An Autodiscover DNS record lets Outlook and phones find the new mailbox without manual setup. Tell users how to sign in, and then check a sample of desktops and phones in each team.

  • Passes when: the sampled devices connect and users know the sign-in steps.
  • Signed by: support lead.
  • Record kept: the reconnection list.

Old Server Kept Until Sign Off

Before anyone deletes the migration batch, every user must be on the new mailboxes. The batch must also have synced at least once after mail began arriving directly, per the cutover guide. After deletion, the service does not copy over mail sent to the old server.

  • Passes when: both conditions are met and the IT head agrees.
  • Signed by: IT head.
  • Record kept: the last sync time and the sign-off note.

One Mailbox Group Through the Email Migration Checklist

Take a made-up case, labeled as such and no real client. It is a sales team of 25 people with one shared mailbox and one delegate.

Before the move, the admin records counts and verifies the domain. Licenses are assigned too, a backup is tested and a pilot of three people has names. During the move, the pilot passes. Then the count check reads Not yet, because one salesperson’s target mailbox is short of the source.

Email migration checklist parts: what passes, who signs and which record is kept
Every check carries these three parts.

The next stage waits. The mail admin finds that a large archive folder had not synced, reruns it and compares counts again. The check turns to Pass and the group moves on. Mail flow and the files sample pass. Then the MX switches, the three records resolve, phones reconnect, and the IT head signs the last line.

Who Signs Off the Email Migration Checklist

A stage closes only when all four of its checks read Pass. However, a single Not yet stops the next stage.

Signisys’s working view is to name an owner for each stage, plus one person who signs the whole list. The basis is that a check with several owners tends to have none. Also, a list with no final signer has no end. The same applies to an office 365 migration checklist.

When a check fails, the order of work for each move shows how to carry it out again. Also, what tends to cause a failed check lists likely causes.

Keeping the Signed Email Migration Checklist After the Move

Keep the signed list with the DNS records and the DMARC reports. They serve the next move, an audit or a new admin who asks why a record looks as it does.

Where to Store It

Store the list where the IT team will find it in a year, not in one person’s mailbox.

Key Takeaway A signed list with its records lets the next admin see why each setting looks as it does.

Signisys provides this work through end user computing services and a digital workplace solution for staff devices. It also partners with Microsoft. A working session then covers your list, your DNS records and your sign-off owners, with no result promised beforehand. No charge, with a fixed scope.

Book a consultation
Check your mailbox move with us

Email Migration Checklist: FAQ

Does a small office need the whole list?

Yes, the same three stages, with fewer rows in each check. An IMAP move from another mail platform carries mail only, so contacts and calendars need a check of their own.

Who closes each stage of the list?

Signisys’s working view is that the mail admin, the DNS owner, the team heads and the IT head sign their own checks, as the table shows. One person signs the full list. That single signer keeps the list from stalling between owners.

What happens when a check stays at Not yet?

The next stage waits. The team fixes the gap and runs the check again. The old server stays in place until the last check passes, as the cutover guide advises for the old mailboxes.

Should the list cover files as well as mail?

Yes. Check OneDrive and SharePoint, with sharing and folder permissions sampled for each team. Mail and files move together in many projects, and a permission slip-up shows up fast.

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.