Skip to main content
Email Migration

How to Migrate Your Business Email Without Losing Data

Switching email providers is one of the riskiest IT changes a business can make. Done wrong, you lose emails, break communication, and confuse clients. Here's how to do it right.

Why Businesses Migrate Email

Most businesses do not migrate email because they want to. They migrate because something has stopped working. The most common triggers are deliverability collapse (legitimate emails landing in spam folders), provider price hikes that no longer match the value, security gaps that cannot be closed on the current platform, or a merger or rebrand that forces a domain consolidation.

Email is also one of the few systems where every minute of downtime is felt by every employee, every customer, and every prospect. A migration that loses two days of mail does not just inconvenience users; it sends invoices into the void, drops time-sensitive replies, and erodes trust with the contacts who needed to reach you that week. The plan below treats email like the production system it is, with backups, fallback windows, and verification at every step.

Before starting, write down what success looks like. For most businesses it is three things: zero email lost, every user productive on day one, and external senders never getting a bounce or spam classification because of the change. Hold the project to that bar.

Phase 1: Planning

Audit Your Current Setup

Document everything: how many mailboxes, total storage used per mailbox, shared calendars, distribution lists, forwarding rules, aliases, and any third-party integrations (CRM, helpdesk, marketing tools) that send email through your domain.

Back Up Everything

Before touching anything, export a full backup. For Microsoft 365, use PST exports. For Google Workspace, use Google Takeout. For cPanel/webmail, use IMAP sync to a local client. Store backups on a separate drive, not on the mail server being migrated.

Choose the Right Timing

Schedule the migration for a low-activity period. Friday evening or weekend works well for most businesses. Avoid month-end, quarter-end, or any period when email communication is critical. Plan for 24-48 hours of potential disruption.

Phase 2: Choose Your Migration Method

IMAP Migration

Connect old and new servers via IMAP and sync mailboxes. Works with any provider.

  • Universal compatibility
  • Syncs mail, folders, read status
  • Does not sync calendars or contacts

PST Export/Import

Export mailboxes to PST files and import into the new system. Best for Outlook/Exchange.

  • Includes calendar and contacts
  • Works offline
  • Large files, slow for big mailboxes

Admin Migration Tools

Use built-in admin tools from Microsoft 365 or Google. Fastest and most reliable method.

  • Full mailbox + calendar + contacts
  • Automated batch processing
  • Requires admin access to both platforms

Phase 3: DNS Changes

After mailbox data is migrated, you need to update your domain's DNS records to point to the new email provider. This is the critical step where things most commonly go wrong.

MX Records: Point to your new email provider. This tells the internet where to deliver email for your domain. Old MX records must be removed.
SPF Record: Update to include your new provider and remove the old one. Having both during migration is acceptable temporarily.
DKIM Records: Add DKIM keys from your new provider. Each provider uses different CNAME or TXT records for DKIM.
DMARC Record: If you have a strict DMARC policy (reject), temporarily relax it to quarantine during migration to avoid losing legitimate emails.
Autodiscover/Autoconfig: Update CNAME records that help email clients automatically configure server settings for your domain.

Important: DNS changes take up to 48 hours to propagate worldwide. During this period, some emails will go to the old server and some to the new one. Keep both servers active until propagation is complete.

Common Migration Failures

  • Turning off the old server before DNS propagation is complete (emails lost)
  • Forgetting to update SPF records (emails from new server go to spam)
  • Not migrating shared calendars and distribution lists
  • Overlooking email forwarding rules that existed on the old server
  • Not updating third-party services that send email on your behalf (CRM, invoicing, etc.)
  • Changing passwords during migration, locking users out of both systems
  • Not communicating the migration timeline to employees

Post-Migration Checklist

  • Send test emails to and from external addresses (Gmail, Outlook.com, Yahoo)
  • Verify SPF, DKIM, and DMARC pass checks using our email security assessment
  • Confirm all users can send and receive on all devices (desktop, phone, tablet)
  • Check shared calendars and distribution lists are working
  • Verify email signatures display correctly
  • Test any third-party integrations that use email
  • Monitor for bounce-backs over the next 48 hours
  • Keep the old server running for at least 2 weeks as fallback

Email Migration FAQ

How long does a business email migration take?

Most small business migrations take 2 to 5 business days when planned correctly. Mailbox copy is usually the longest step (multiple gigabytes per user can take many hours), followed by DNS propagation which can take up to 48 hours globally. Larger organizations or migrations with complex shared resources can take 2 to 4 weeks.

Will we lose any emails during the migration?

Not if the migration is done correctly. The key is keeping both old and new mail servers running until DNS propagation completes. We sync mail twice (once before the cutover, once after) so any messages that arrive at the old server during the cutover window are also copied to the new one.

Do we need to change our email addresses?

No. Your domain stays the same. Only the underlying mail provider changes. Customers and contacts will not see any difference, except your email may actually deliver more reliably afterward if the old provider had deliverability issues.

What about calendars, contacts, and shared mailboxes?

Calendars and contacts migrate automatically when you use admin migration tools (Microsoft 365 or Google Workspace). For IMAP-based migrations, calendars and contacts must be moved separately. Shared mailboxes, distribution lists, and resource calendars need to be re-created on the new platform and permissions reapplied.

Can we keep our old emails after the migration?

Yes. A complete migration includes copying every existing message, folder, and read/unread state. We also recommend keeping a separate PST or archive backup independently of the new mail server in case of long-term retention or compliance needs.

Need Help With Email Migration?

We handle business email migrations every day. From planning through DNS configuration and post-migration testing, we make sure nothing is lost.

Get Security Insights Delivered

One email per month with our best articles. No spam.

Unsubscribe anytime. Privacy policy