Changing Email Providers: How to Update MX Records With Zero Downtime

Switching email providers is one of those tasks that sounds simple until you're halfway through it and emails start bouncing. The good news is that with a little preparation, you can move from one email provider to another without losing a single message or experiencing any downtime. The key is updating your MX records the right way and in the right order.

This guide walks you through the entire process, from pre-migration planning to post-switch cleanup, in plain language that doesn't require a computer science degree.

Why MX Records Matter When You Switch

Your MX records are the signposts that tell the internet where to deliver email for your domain. When you change email providers, the new provider needs to be the one receiving those deliveries, but the internet won't know that until you update your MX records.

If you update MX records incorrectly, or in the wrong order, you can end up with email being delivered to the old provider (where you no longer have an account), messages bouncing outright, or a confusing split where some email arrives at the new provider and some doesn't.

The goal is a clean handoff: at a specific moment, all new incoming email goes to the new provider. Here's how to make that happen.

Pre-Migration Checklist

Before you touch a single DNS record, work through this checklist:

Set up your account with the new provider fully. This means creating mailboxes, aliases, and distribution groups in the new system before you flip the switch. If you try to redirect email to a provider that isn't configured to accept it, messages will bounce.

Export or migrate existing email if needed. Your old emails don't move automatically. If you want historical messages in your new inbox, migrate them now, either through your email client or using a migration tool your new provider may offer.

Write down your current MX records. Log into your domain registrar (GoDaddy, Namecheap, Cloudflare, wherever you manage DNS) and take note of your current MX records. You'll want these as a reference in case you need to roll back.

Identify your SPF record. Your current SPF record authorizes your current email provider to send email on your behalf. After the switch, you'll need to update it to authorize your new provider instead.

Give yourself time. Don't do this migration on a Friday afternoon or before a product launch. Pick a quiet window, ideally in the evening or on a weekend, when email volume is low.

Step 1: Lower Your TTL

TTL stands for Time to Live, and it controls how long DNS servers around the world cache your MX records before checking for an update. If your TTL is set to 86400 (24 hours) and you change your MX records, some mail servers might keep delivering to your old provider for up to a day.

To minimize this window, lower your MX record TTL 24-48 hours before your planned migration. Set it to 300 (5 minutes) or 3600 (1 hour). This gives DNS caches time to expire, so when you make your actual change, it propagates much faster.

Log into your DNS management panel, find your MX records, and lower the TTL value on each one. Save the changes and wait at least 24 hours before proceeding.

Step 2: Set Up the New Provider Completely

While waiting for the TTL change to propagate, use this time to finish configuring your new email provider:

Create all mailboxes and aliases your team needs
Set up any email routing rules or shared inboxes
Configure your email client or mobile app to connect to the new provider
Verify the new provider has confirmed your domain ownership (most require this as part of setup)

Your new provider will give you a set of MX records to use, typically a hostname and priority number for each. Keep these handy. You'll need them in the next step.

Step 3: Update Your MX Records

This is the actual migration moment. Log into your DNS management panel and make the following changes:

Delete your old MX records. Remove every existing MX record for your domain. Don't worry, email won't stop instantly because of DNS caching, and you're about to add new ones immediately.
Add your new provider's MX records. Enter each MX record your new provider gave you, including the correct hostnames and priority values.
Save the changes.

For example, if you're switching to Google Workspace, your new MX records would be:

@ → aspmx.l.google.com        (priority 1)
@ → alt1.aspmx.l.google.com   (priority 5)
@ → alt2.aspmx.l.google.com   (5)
@ → alt3.aspmx.l.google.com   (priority 10)
@ → alt4.aspmx.l.google.com   (priority 10)

For Microsoft 365, you'd add a single record like:

@ → yourdomain-com.mail.protection.outlook.com  (priority 0)

Your new provider's setup documentation will have the exact values.

Step 4: Verify with the MX Checker

Don't assume the change worked. Confirm it. Go to mxrecordchecker.com and enter your domain name. The tool will show you which MX records are currently live in DNS.

If you see your new provider's mail servers listed, the migration is working. If you still see your old provider's servers, DNS propagation is still in progress. Give it a bit more time and check again.

Because you lowered your TTL in Step 1, propagation should happen within an hour or two rather than the full 24-48 hours it would otherwise take.

Step 5: What Happens to In-Flight Email

You might be wondering: what about messages that were sent just as you were switching?

The good news is that email is designed with this in mind. If a sending mail server tried to deliver a message during your transition and temporarily couldn't reach a valid server, it will retry delivery for up to several days (the exact window depends on the sending server's configuration; most try for 72 hours or more).

Once your new MX records propagate, those queued messages will be delivered to your new provider. You shouldn't lose them; they'll just arrive a little later than usual.

During the transition period itself, some messages may still arrive at your old provider if caches haven't expired yet. If you still have access to your old account during this time, check it and forward anything important to your new address.

Step 6: Update Your SPF Record

Once your MX records are updated and email is flowing to the new provider, your next task is updating your SPF record. SPF (Sender Policy Framework) tells the world which mail servers are authorized to send email from your domain.

If your SPF record still references your old email provider and not your new one, email you send may be flagged as spam or rejected by some recipients.

Your new provider's setup guide will include the SPF record value to add or update. Typically, you'll replace the old include: statement with the new provider's equivalent. For example:

Google Workspace: include:_spf.google.com
Microsoft 365: include:spf.protection.outlook.com

Check your current SPF record at spfrecordcheck.com and update it in your DNS management panel.

Post-Migration Cleanup

After email is confirmed working with your new provider, wrap up a few loose ends:

Cancel your old email plan. Don't forget to close or downgrade your account with the previous provider. It won't happen automatically, and you don't want to keep paying for something you're not using.

Raise your TTL back to normal. Now that the migration is complete, set your MX record TTL back to 3600 (1 hour) or 86400 (24 hours). A higher TTL reduces DNS query load and is fine for a stable configuration.

Set up DKIM and DMARC if you haven't already. Ask your new provider for DKIM record values and add them to DNS. Consider adding a DMARC record as well to protect your domain from spoofing. You can check your DMARC status at dmarcrecordchecker.com.

Monitor for a few days. Keep an eye on your inbox and ask a colleague or friend to send you a test message from an external address. Check that replies go out successfully too.

Common Mistakes to Avoid

Skipping the TTL reduction. Without lowering TTL first, propagation takes much longer and the overlap period where old and new providers might both receive mail is extended.

Forgetting to update SPF. Email deliverability suffers immediately when SPF doesn't match your sending provider. This is one of the most commonly overlooked steps.

Not testing the new provider before cutting over. If you flip MX records to a provider that isn't configured to accept your domain, you get bounces, not a graceful transition.

Rushing the migration. Give yourself a quiet time window. A migration done in 20 minutes of panic leads to mistakes that take hours to undo.

With this process in hand, switching email providers becomes a manageable, methodical task rather than a stressful guessing game. The free MX record lookup at mxrecordchecker.com is your best friend throughout, so use it liberally.