Business Email Migration: How to Move Old Emails and Contacts

The items most often overlooked during email migration aren't the inbox—they're Sent items, subfolders, shared address books, group aliases, and mobile client d…

Insights:Business Email Migration: How to Move Old Emails and Contacts

Six Categories of Data to Audit Before Migration

Type What to audit Common oversights
Accounts Active, resigned, and shared accounts Counting only active users and missing shared mailboxes
Mail Inbox, Sent, Drafts, Archives, subfolders Migrating only the Inbox
Contacts Personal address book, shared address book, groups Missing shared contacts and groups
Calendars Personal calendar, shared calendar, meeting invites Migrating only email data
Aliases Department aliases, role aliases, group addresses Bounces on old addresses after cutover
Clients Outlook, mobile, IMAP, POP Continuing to connect to the old server after migration

First build an account inventory table: old address, new address, whether shared, mailbox capacity, special folders, and owner. Migration is not just a "technical operation" — it is an asset handover.

Recommended execution order

  1. Create accounts and aliases in the new email service.
  2. Migrate one pilot account first and confirm that mail, folders, and contacts are intact.
  3. Batch-migrate mail while preserving the original folder structure.
  4. Migrate contacts, calendars, and shared addresses.
  5. Lower the DNS TTL, at least one full TTL cycle in advance.
  6. Switch MX records; keep the old mailbox receiving or read-only.
  7. Verify sending/receiving, clients, aliases, and groups item by item.
  8. Monitor for a period before deciding whether to decommission the old mailbox.

Avoid cutting over MX during business hours. Keep a maintenance window and rollback plan ready.

How to move mail

There are three common approaches:

  • IMAP Sync: Configure both the old and new mailboxes in your client or migration tool, then sync folder by folder. Works for most business email accounts.
  • Provider Migration Tool: Batch pull by account for speed, but check whether subfolders, shared mailboxes, and archives are supported.
  • Export and Import: Export to a universal format then import; suitable for small batches or offline archiving, but folder structure and labels may be lost.

Regardless of method, confirm first:

  • Sent items and drafts are included.
  • Large attachments arrive intact.
  • Email labels and read/unread status are preserved.
  • The process is retryable and idempotent on failure.

How to Migrate Contacts and Calendars

Personal contacts can usually be exported as vCards, and calendars as ICS files. Shared contacts and groups depend on whether the new service supports import.

After migration, verify item by item:

  • Contact name, company, phone, and email are complete.
  • Groups are intact.
  • Shared contacts are visible to the right people.
  • Calendar sharing permissions and meeting invites work correctly.

What to Watch During DNS Cutover

Email-related DNS records include more than just MX:

  • MX: inbound routing.
  • SPF: sending authorization.
  • DKIM: signature verification.
  • DMARC: policy and reporting.
  • Auto-discover records: for Outlook and similar clients.

Lower TTL before switching, and do not delete old records immediately after. Confirm the new mailbox can send and receive before cleaning up the old service.

Post-Switch Verification Checklist

  • Internal, external, and overseas send/receive tests.
  • Log-in on mobile and desktop clients.
  • Old addresses, aliases, and group addresses still receive mail.
  • No abnormal spam or bounce issues.
  • Calendar invites and shared contacts are functional.
  • Whether admins can view bounces and logs.
  • Common Pitfalls

    • Migrating only the inbox and missing sent items and archives.
    • Failing to lower TTL before cutover, leaving old DNS records active for a long time.
    • Deactivating the old mailbox immediately, making it impossible to roll back when bounces occur.
    • Not creating aliases in advance, so customers emailing the old address get no delivery.
    • Clients still pointing to the old server after migration, leading users to believe emails are lost.

    Set Expectations Upfront

    Email migrations rarely guarantee zero downtime. What we can commit to: a defined maintenance window, a pilot phase, a rollback plan, and a verification checklist. Historical message volume, shared mailboxes, archives, and third‑party client usage all impact timeline — a proper inventory should be completed before quoting.

    Related reading: