Move Email Mailboxes, Messages and DNS: Full Guide
- Average speed
- km/h
- Result
- Total minutes
- 120 min
- You entered
- Total distance
- 10 km
- You entered
Moving your email mailboxes, messages, and DNS means transferring your email accounts, stored emails, and domain name system settings from one provider or server to another. This guide explains what each part involves, how to do it safely, and what to watch out for.
What Does “Moving Email� Actually Mean?
When people say “move email,� they usually mean one of three things: moving the mailbox (the account itself), moving the messages (the stored emails), or moving the DNS (the domain’s settings that route email). These are separate tasks, but they often happen together when switching email providers or hosting. For example, moving from Google Workspace to Microsoft 365 requires all three: creating new mailboxes, importing old messages, and updating MX records in DNS. Understanding the difference helps you plan and avoid data loss.
Background: Why People Move Email
Common reasons include changing internet service providers, switching to a cheaper or more feature-rich email host, consolidating multiple accounts, or moving a business domain to a new registrar. Each reason affects which parts you need to move. A personal email move might only involve exporting messages and changing login details. A business move often involves DNS, multiple mailboxes, and compliance considerations like retaining old emails for legal or archival purposes. Knowing your reason helps you choose the right tools and timeline.
How It Works: The Three Components
Mailboxes are the accounts themselves (e.g., you@yourdomain.com). Moving a mailbox means creating a new account on the target provider and setting up the same username, password, and settings. Messages are the actual emails, folders, contacts, and calendar entries stored in the mailbox. These are usually transferred via IMAP (Internet Message Access Protocol) or a provider-specific export/import tool. DNS (Domain Name System) is the global directory that tells email servers where to deliver mail. The key DNS records for email are:
- MX (Mail Exchange) – directs incoming mail to the correct mail server.
- SPF (Sender Policy Framework) – lists which servers are allowed to send mail for your domain.
- DKIM (DomainKeys Identified Mail) – a digital signature that verifies email authenticity.
- DMARC (Domain-based Message Authentication, Reporting & Conformance) – tells receiving servers what to do if SPF or DKIM fails.
Changing MX records is the final step that switches mail flow to the new provider. Until that happens, new mail still goes to the old server.
How to Choose: What to Move First
The order matters. A typical sequence is:
- Set up the new mailboxes on the target provider, including users, aliases, and forwarding rules.
- Transfer messages using IMAP sync tools or the provider’s import feature. This can take hours or days depending on volume.
- Update DNS – change MX records to point to the new provider, and add SPF, DKIM, and DMARC records as instructed.
- Verify everything – send test emails to and from the domain, check that old messages appear, and confirm no bounce-backs.
- Keep the old server running for at least a few days (or longer) to catch any delayed mail.
If you’re moving only messages (e.g., from one personal account to another), you can skip DNS entirely. If you’re moving DNS but keeping the same email provider, you only need to recreate the same DNS records at the new DNS host.
Common Problems and How to Avoid Them
The biggest risk is losing email. Common issues include:
- Cutting over DNS too early – if MX records change before all messages are synced, new mail goes to the new server, but old mail may still be on the old server, causing split-brain.
- Missing SPF/DKIM/DMARC – without these, your mail may land in spam or be rejected. Always copy the exact values from your old DNS.
- IMAP folder structure mismatches – some providers use different folder names (e.g., “Sent� vs. “Sent Items�). Use a tool that maps folders correctly.
- Rate limits – many providers throttle bulk imports. If you have tens of thousands of emails, the sync may take days. Plan for this.
- Aliases and distribution lists – forgetting to recreate these can break internal communication.
A common misconception is that changing MX records immediately moves existing messages. It doesn’t. MX only affects new mail. Existing messages must be transferred separately.
Costs and Time Estimates
Moving email can be free if you use built-in tools (e.g., Outlook’s export/import, Gmail’s import from another account) and manage DNS yourself. Paid options include third-party migration services that handle everything, often charging per mailbox or per GB. Time depends on the number of mailboxes and the total data volume. A single personal account with a few hundred emails can take an hour. A business with 50 mailboxes and 100 GB of data might take several days for the message sync alone. DNS propagation (the time it takes for the new MX records to be seen worldwide) typically takes a few hours to 48 hours, though it’s often faster.
Safety and Best Practices
Before starting, always back up your email. Export a PST file (Outlook) or use the provider’s takeout/export feature. Keep the old server active for at least a week after the move. For DNS, write down all current records before changing anything. If you’re not comfortable with DNS, use a migration service or ask your new provider for step-by-step guidance. Never delete the old mailboxes until you’ve confirmed all messages arrived and you’ve been receiving new mail for several days. Also, update any email clients (Outlook, Thunderbird, phone apps) to use the new server settings after the move.
Frequently Asked Questions
How long does email migration take?
It depends on the number of mailboxes and the volume of data. A small personal account can finish in under an hour. A large business with many mailboxes and gigabytes of data can take days. The sync process runs in the background, so you can still use your email during the transfer, but you may see temporary inconsistencies.
Will I lose my emails if I change MX records?
No, changing MX records only affects new mail delivery. Your existing emails remain on the old server until you move them. However, if you cancel the old mailbox before moving messages, you will lose them. Always export or sync first.
What is the difference between IMAP and POP3 for migration?
IMAP syncs folders and keeps messages on the server, making it ideal for migration because it copies the entire mailbox structure. POP3 downloads messages to a single device and typically deletes them from the server, which can cause data loss if you’re not careful. Use IMAP for migration.
Can I move email between different providers like Gmail and Outlook?
Yes. Most providers offer built-in import tools (e.g., Gmail’s “Import mail and contacts� or Outlook’s “Import from Gmail�). You can also use third-party tools that connect via IMAP. The process is straightforward but may require you to enable “less secure app access� or generate an app-specific password for the old account.
Do I need to change DNS if I only move my email clients?
No. If you’re just setting up Outlook or a phone app to read email from the same provider, you don’t need to touch DNS. DNS only changes when you switch the server that hosts your mail.
What happens to my contacts and calendar during migration?
Most migration tools handle contacts and calendar entries alongside email, but not always. Check your provider’s import options. If they’re not included, export them separately as CSV or ICS files and import them into the new account.
Related
Formula used
in t | Total minutes | min | 120 | 0 in d | Total distance | km | 10 | 0 out pace | Average pace | min/km | t / d | 2 out speed | Average speed | km/h | d / (t / 60) | 2
Each line is one input (in, sel, list) or one result (out: label, unit, formula, decimals). How the calculators work
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.