Email Migration

Can a Migration Batch Remain Open After an MX Cutover?

Algirdas JasaitisAlgirdas Jasaitis Oct 22, 2026 869 views

Question details

The user needs to know whether incremental mailbox synchronization continues after an MX record cutover to Microsoft 365, and if the migration batch should remain open.

Can a Migration Batch Remain Open After an MX Cutover?
Product
Microsoft 365
Device & OS
not provided
Scenario
Finalizing a cutover email migration after updating the MX records to point to Microsoft 365.
Observed behavior
Seeking clarification on the correct administrative procedure for handling a completed cutover migration batch once mail routing has been updated.
Before you start

Ensure that your DNS MX records have fully propagated to point to Microsoft 365 and that incoming mail is actively and successfully routing to the new mailboxes.

Solution 1Recommended

Verify Mail Flow and Delete the Migration Batch

Once the MX record points to Microsoft 365 and mailboxes have synchronized post-cutover, you should delete the cutover migration batch rather than leaving it open.

While incremental synchronization occurs during the initial migration phase, leaving a cutover migration batch open indefinitely after the MX cutover is not recommended. Microsoft's best practice dictates deleting the completed cutover batch once the MX cutover is fully verified. Deleting the batch cleans up the temporary migration records and prevents administrative confusion.

1
Verify mail routing

Send test emails to confirm that all new incoming mail is correctly routed directly to the users' Microsoft 365 mailboxes.

2
Confirm final synchronization

Ensure that every mailbox has synchronized successfully at least once after the mail began routing directly to Microsoft 365. This guarantees no emails were left behind during DNS propagation.

3
Delete the migration batch

Navigate to the Exchange admin center, go to Migration, select the completed cutover migration batch, and click the Delete icon. This safely removes the migration tracking records.

Verify Mail Flow and Delete the Migration Batch
Data Safety: Deleting the migration batch only removes the migration status logs and records from the admin center. It does not delete any mailboxes, users, or migrated email data.
Free Microsoft Office alternative

Empower Your Migrated Users with WPS Office

After successfully migrating your organization's email to Microsoft 365, equip your team with a highly compatible, fast, and free productivity suite. WPS Office offers a seamless user experience for handling all everyday document tasks.

  1. 1. Download the installer: Visit the official WPS Office website to download the free installation package for Windows, Mac, or Linux.
  2. 2. Install the software: Run the installer to quickly deploy the lightweight suite across your organization's devices.
  3. 3. Open existing files: Launch WPS Office and instantly open your existing Word, Excel, and PowerPoint files with zero formatting loss.
Provides a reliable document editing environment for users after finalizing your Microsoft 365 email migration.Fully compatible with Microsoft Office formats, including .docx, .xlsx, and .pptx.Lightweight design ensures faster installation and smoother performance on older hardware.Familiar tabbed interface reduces the learning curve for newly migrated staff.
microsoft office alternative - wps office

Frequently Asked Questions

What happens if I don't delete the cutover migration batch?

If the batch is left open, it can clutter your Exchange admin center with unnecessary logs. Microsoft officially recommends deleting the batch once the MX cutover is complete to cleanly finalize the migration process.

How long should I wait after changing the MX record before deleting the batch?

You should wait until DNS propagation is fully complete (typically 24 to 72 hours) and verify that all incoming mail is successfully flowing to Microsoft 365. Always ensure at least one successful mailbox synchronization has occurred since the routing change before deletion.

Can I resume a deleted migration batch if something goes wrong?

Once a migration batch is deleted, it cannot be resumed. If you discover issues later, you would need to investigate specific mailboxes individually or create a new migration batch, which is why verifying mail flow before deletion is critical.