Whether leaving a slow provider, chasing better pricing, or consolidating platforms after a merger, migrating business email is a genuine risk point — done wrong, it means lost messages and confused clients during the switch. Done right, most users never notice it happened.

Before Migration

  • Inventory every mailbox, alias and distribution list currently in use.
  • Confirm mailbox storage sizes to plan adequate space on the new platform.
  • Note current DNS records (MX, SPF, DKIM) as a reference and rollback point.
  • Choose a low-traffic window for the cutover — weekends or holidays for most businesses.

During Migration

  1. Set up the new platform fully before touching DNS — mailboxes, aliases and distribution lists all created and tested.
  2. Migrate mail data using IMAP migration tools that most providers offer, preserving folder structure.
  3. Test the new mailboxes by sending and receiving before cutover — do not skip this step.
  4. Lower DNS TTL 24-48 hours in advance so the eventual MX change propagates faster.
  5. Switch MX records during the planned low-traffic window.
  6. Update SPF and add DKIM for the new provider immediately after cutover.

After Migration

  • Monitor mail flow closely for the first 48–72 hours as DNS propagation completes globally.
  • Keep the old provider active in read-only mode for a few weeks as a safety net.
  • Update mobile devices and desktop clients with the new server settings.
  • Confirm sent-mail history and contacts transferred correctly for every user.

A Realistic Timeline for a 10-Person Team

For a small business migrating around ten mailboxes, a sensible schedule spreads the work across roughly two weeks rather than compressing it into one weekend: week one for setting up and thoroughly testing the new platform in parallel with the old one still fully live, a planned cutover on a Friday evening or weekend when email volume is naturally lowest, and a two-week overlap period afterward where the old provider stays active read-only in case anything was missed. Rushing this into a single evening is the most common cause of overlooked distribution lists or a forgotten shared mailbox surfacing as a problem days later.

Common Mistakes That Cause Lost Mail

  • Canceling the old provider immediately instead of keeping it live briefly as a safety net.
  • Forgetting SPF/DKIM updates, causing new mail to land in recipients' spam folders.
  • Migrating during business hours without warning staff, causing confusion over which inbox is active.

Frequently Asked Questions

How long does DNS propagation actually take?

Usually a few hours with a properly lowered TTL, though full global propagation can occasionally take up to 48 hours.

Can this be done with zero downtime?

With careful planning and a brief old-provider overlap, disruption is minimal to unnoticeable for most businesses.

Who should lead a migration for a non-technical small business?

A hosting provider offering managed migration support removes most of the risk covered in this checklist, since the technical steps (IMAP migration, DNS timing, DKIM setup) are exactly where non-technical teams most often make costly mistakes.

Planning a migration? See our free migration service or get expert help with the switch.