Move business email in stages: inventory mailboxes and connected senders; create target accounts; choose a migration method that supports the data you need; copy and verify historical mail; prepare DNS and authentication; then change MX and test delivery. Use a final sync where the supported method provides one, and keep access to both services until verification is complete. No migration method guarantees that every item will copy.

Inventory the current email system

List more than the visible staff addresses.

Include:

  • user mailboxes;
  • aliases;
  • shared addresses such as accounts@;
  • forwarding rules;
  • distribution lists;
  • catch-all addresses if used;
  • calendar and contacts requirements;
  • mobile and desktop clients;
  • scanners or systems that send mail;
  • website forms;
  • CRM;
  • invoice and accounting platforms.

A move can appear successful until the forgotten quotes@ forwarder stops working.

Confirm who controls the domain and DNS

Before the migration date, make sure the business can edit:

  • MX records;
  • SPF;
  • DKIM;
  • DMARC;
  • verification TXT records;
  • autodiscover or provider-specific DNS where required.

Confirm who can edit the DNS account before scheduling the move. Record the access owner and recovery route without putting passwords in the project spreadsheet. For account ownership and recovery, see the domain, hosting and website ownership guide.

Choose the migration method by the data you need

Different tools move different data.

For example, Microsoft says its IMAP migration moves email folders but not contacts, calendars or tasks. Email-only moves may fit IMAP when both providers support it. If contacts, calendars or shared data must move too, choose a source-to-target method that explicitly supports those items and lets you verify them. Microsoft’s migration overview describes available approaches.

Write down what must move:

  • email;
  • folders/labels;
  • read/unread state;
  • contacts;
  • calendars;
  • shared mailboxes;
  • aliases;
  • signatures;
  • rules;
  • delegated access.

Do not assume “IMAP migration” means a complete account clone. Confirm what the selected method includes before starting.

For a Google Workspace target, staff can use Gmail in a browser or the Gmail app if their accounts and administrator settings allow it. The app experience does not determine what data migrates: confirm folders, contacts and other items against the chosen method and written scope. Google documents adding a Workspace account to the Gmail app in its mobile setup guidance. For other target providers, check the available apps and account policies before choosing.

Confirm a recoverable source copy

Before migration, ask the current provider whether it supports an export, backup or retention option for the data in scope. Confirm how the saved copy can be opened or restored. If no recoverable copy is available, keep the source account accessible until the target is verified and every known omission is resolved.

Create the target mailboxes before changing MX

Provision users on the new service while mail still routes to the old one.

Check:

  • correct primary addresses;
  • aliases;
  • licences;
  • mailbox quotas;
  • shared mailbox access;
  • admin accounts;
  • multi-factor authentication;
  • recovery methods.

Send internal test messages within the target system if the provider allows it.

The new mailboxes should exist before external senders are directed to them.

Migrate historical mail before cutover

Start copying data while the old provider still receives new mail.

This reduces the amount that must be handled during the final switch.

Monitor:

  • completed mailbox count;
  • failed items;
  • large messages;
  • skipped folders;
  • quota issues;
  • authentication failures.

Review provider-specific migration limits.

Check migration limits for the exact source, target and method before promising a completion date.

Verify the copied data

Do not accept “migration completed” as the only check.

Sample several mailboxes:

  • oldest expected message;
  • newest migrated message;
  • important folders;
  • Sent items;
  • attachments;
  • search;
  • large customer threads;
  • mail from several years.

Compare source and target counts where the tools expose reliable counts.

Record known exclusions so users do not report them later as unexplained data loss.

Lower MX TTL before the switch when appropriate

DNS resolvers cache MX information for the record’s time-to-live.

For migrations where you control DNS and the provider recommends it, lower the MX TTL in advance so external systems may refresh the destination sooner after cutover.

Microsoft’s IMAP migration guidance recommends reducing TTL ahead of the final MX change and restoring a longer value later. Follow the guidance for the selected provider and DNS host.

Do this ahead of time. Lowering TTL one minute before cutover does not immediately remove caches that already stored the old value.

Prepare SPF and DKIM for the new sender

Mail routing and outbound authentication are different changes. SPF identifies authorised sending systems, DKIM adds a verifiable signature to outgoing messages, and DMARC checks alignment between authentication and the visible sender domain. For configuration and verification steps, use the SPF, DKIM and DMARC guides for Google Workspace or Microsoft 365 and hosted email.

Before staff send through the new provider, prepare the required authentication:

  • new provider added to the existing SPF policy, with one SPF record per hostname;
  • DKIM DNS records published;
  • DKIM enabled in the new service;
  • legitimate senders inventoried, and test messages pass the provider’s SPF/DKIM alignment checks for the visible sender domain.

Keep the old sender authorised while legitimate mail still leaves through it.

Remove old authorisation only after the old path is no longer used.

Change MX when the target is ready

MX records tell external mail systems where to deliver incoming email.

Before cutover, agree a provider-specific recovery procedure with a named decision owner. It should state which account remains authoritative, how both systems stay accessible, how messages received on the new service will be reconciled if MX must be restored, and which inbound/outbound checks must pass before retrying.

Change only the required mail records. Preserve unrelated DNS records used by the website and other services. Change MX only after:

  • target mailboxes exist;
  • initial migration is complete enough;
  • users can sign in;
  • authentication is prepared;
  • support contact is available;
  • a rollback or old-system access plan exists.

Record the previous MX values before editing DNS, and verify the website still resolves after the change.

Test inbound and outbound mail immediately

Use external accounts from more than one provider where possible.

Test:

  • external Gmail to new mailbox;
  • new mailbox to Gmail;
  • Microsoft/Outlook recipient;
  • reply chain;
  • attachment;
  • alias;
  • shared address;
  • website form;
  • invoice/CRM sender.

Inspect SPF, DKIM and DMARC on outbound test messages.

Confirm the website still sends to the right address after the mail provider changes.

If delivery fails, pause further changes and keep both providers accessible. The named decision owner should follow the agreed recovery procedure with the providers, including reconciling any messages already delivered to the new service before restoring old MX values. Retry only after the provider confirms the target, DNS and external delivery checks are ready again.

Run a final sync

Mail may arrive at the old system during DNS propagation or between the initial migration and MX change.

Use the migration tool’s final, incremental or delta sync where supported.

Google documents delta import for new or changed content in supported Workspace migrations. Microsoft documents synchronisation during supported migrations until an administrator stops the migration batch. These behaviours depend on the selected source, target and migration method.

Follow the method for your specific source and target.

Keep the old system alive while routing settles

Do not cancel the old provider when the first message reaches the new mailbox. Monitor both systems and complete final verification under the provider’s migration plan before ending old-service access.

The exact overlap period depends on the migration method and DNS environment.

Update every connected system

After the mailboxes move, update systems that depended on the old provider:

  • website form recipient;
  • SMTP settings;
  • CRM;
  • accounting software;
  • scanner;
  • WordPress or ecommerce mailer;
  • support desk;
  • mobile devices;
  • Outlook profiles;
  • shared mailbox permissions.

A migration is not complete while an old SMTP password remains embedded in the website.

Preserve the business identity

Customers should continue using the same domain address where possible.

A provider change from cPanel email to Google Workspace or Microsoft 365 should not force customers to learn a new public address unless the business is also changing domain.

If the domain changes, plan forwarding and customer communication separately.

Record the handover

Document the mailboxes and aliases, source and target providers, data included or excluded, recoverable-copy status, migration and final-sync results, DNS changes, authentication checks, message tests, connected systems updated, and any unresolved exclusions.

For branded mailboxes, device setup and email authentication, review the business email service. Existing mailbox migration, provider changes and website work depend on your setup and must be confirmed in the written quote.