Email DNS Checklist Before You Move MX Off Gmail

Do not change MX until you can name every Google-related record on the zone. Inventory Google’s MX records (smtp.google.com or the legacy aspmx set), SPF includes, DKIM selectors, and the DMARC record first. In ArawaMail, activating receiving is the MX change itself, so plan that step as the cutover, then create mailboxes, activate sending, and remove Google’s outbound records only after ArawaMail authentication passes.

This is the Gmail-specific pre-flight list for operators who have already decided to move a custom domain off Google Workspace (Gmail for your domain), or off a setup that forwards domain mail into a personal Gmail inbox. It does not replace the generic migration checklist or the Workspace export guide. It focuses on the DNS inventory and the order of operations so mail keeps flowing.

How we checked the cutover order

Checked on 27 October 2026 against the current ArawaMail docs (Onboard a Domain, Cloudflare Requirements, Activate Receiving, Enable Sending, Email Accounts, Connect a Device) and Google Workspace Help on MX records, SPF, and DKIM. Activating receiving in ArawaMail publishes the MX records (through Cloudflare, or directly for domains registered with ArawaMail) and asks you to confirm before it replaces existing MX records. Enabling sending adds DKIM CNAMEs plus custom MAIL FROM MX and SPF records; DMARC is not among the records it lists. ArawaMail publishes these values for you, so confirm them with a DNS lookup instead of typing hostnames by hand.

Numbered pre-flight checklist before you move MX

1. Inventory every Google record.
   • MX: Google’s current value is a single smtp.google.com record at priority 1. Domains set up before 2023 may still use the legacy records that start with aspmx. Either shape means Google still receives your mail. If MX points to your registrar or a forwarding service instead, Gmail only receives forwarded copies, so note that service too.
   • SPF: look for include:_spf.google.com in the TXT record that starts with v=spf1.
   • DKIM: Google’s default selector is google, published at google._domainkey. Your domain may use a custom selector, so check the live zone.
   • DMARC: note the _dmarc TXT record and its p= and rua= tags. See how to check a domain’s DMARC policy.
   Copy the exact current values before you change anything. Changing MX does not remove outbound SPF includes or DKIM keys.
2. Prepare the domain in ArawaMail. Add the domain under Domains. Unless you registered it with ArawaMail and it still uses ArawaMail’s nameservers, it must be an active Cloudflare zone whose name matches the domain exactly, and you need access to the Cloudflare account that owns it. See Cloudflare Requirements.
3. Treat “Activate receiving” as the MX cutover. Activation publishes ArawaMail’s MX records and routes inbound mail to ArawaMail. Because Google MX records already exist, ArawaMail shows a confirmation step before replacing them. Confirm only when you are ready for inbound mail to move. See Activate Receiving and the ArawaMail DNS reference.
4. Create mailboxes right away and test inbound. Email accounts can only be created once receiving is active, so have the list of addresses and passwords (at least 12 characters) ready beforehand. Optionally choose one active mailbox as the domain’s catch-all. Mail to an address that has no mailbox is discarded unless a catch-all is set, so do this immediately after activation, then send test messages from an outside account.
5. Activate sending and verify authentication. Enable Sending (it requires receiving to be active) so ArawaMail adds the DKIM CNAMEs and MAIL FROM records. Confirm they resolve and that a test message shows SPF and DKIM passing. Keep the Google SPF include and DKIM record until then. Publish or update your own DMARC record (at least p=none with a rua= address) if it is missing.
6. Re-point mail clients. Desktop and mobile clients set up for Gmail need new settings: IMAP on port 993 and SMTP on port 465, both SSL/TLS, signing in with the full email address and the mailbox password. Use the server names provided for your ArawaMail account (the public Connect a Device guide shows placeholders). Phone users can install the SDP Email app instead.
7. Remove leftover Google outbound records only after success. Once Authentication-Results headers and DMARC reports show ArawaMail mail passing, and nothing else still sends through Google, remove the Google SPF include (which also keeps you further from the SPF 10-lookup limit) and retire the unused Google DKIM record.

What breaks and what does not

• Google Calendar, Drive, and Meet are Workspace products, not mailbox DNS. Moving MX does not move them, and cancelling Workspace would affect them separately. See the Workspace migration guide for export steps.
• Mail apps and phones configured for Gmail stop receiving new mail for the domain after the cutover until they are re-pointed to ArawaMail.
• Removing Google SPF or DKIM before ArawaMail sending is active leaves outbound mail unauthenticated. Google’s sender guidelines require every sender to use SPF or DKIM, and senders of 5,000 or more messages a day to Gmail accounts to use SPF, DKIM, and DMARC with an aligned From domain. Keep both stacks live until the new one passes.

Rollback plan

If inbound mail stops, restore the Google MX records you inventoried in step 1 at your DNS host. How quickly senders follow the change depends on the TTL of the records being replaced, so lowering the MX TTL a day before the cutover shortens the window. Then check the domain’s receiving status in ArawaMail. ArawaMail’s Reset option disconnects the domain and stops receiving and sending, so use it only if you are abandoning the move.

This checklist is Gmail-specific. For a source-agnostic cutover and rollback, use the custom-domain email migration checklist. Comparison context lives in custom-domain email vs Gmail.

Related operator notes

• SPF must stay under the 10 DNS lookup limit. See SPF 10 DNS lookup limit.
• Catch-all behavior is set per domain after receiving is active. See catch-all inboxes.
• MX basics: MX records explained. To confirm which provider a domain uses today, see how to tell which email provider a domain uses.
• IMAP vs POP3 for the client side: IMAP vs POP3.

FAQ

What Google DNS records should I copy down before changing MX?

The Google MX records (smtp.google.com or the legacy aspmx set), any Google SPF include, the Google DKIM record (default selector google), and the _dmarc TXT.

Will Google Calendar and mobile mail keep working after MX moves?

Calendar, Drive, and Meet are Workspace products and are not controlled by MX, but they depend on your Workspace subscription, not on this checklist. Mobile and desktop mail clients must be re-pointed to ArawaMail’s IMAP and SMTP settings.

Do I turn on ArawaMail receiving and sending before or after removing Google SPF/DKIM?

Before. Activate receiving (the MX cutover), create mailboxes, activate sending, and verify authentication. Remove the old Google outbound records last.

How do I roll back if inbound mail stops?

Restore the previous Google MX values you inventoried. How fast the change takes effect depends on the TTL of the replaced records.

Is this the same as leaving Google Workspace?

No. This is the DNS inventory and cutover order. The Workspace export and mail-copy steps live in the dedicated migration article.

After the cutover, check the final MX, SPF, DKIM, and DMARC state with the free checkers at ArawaMail free email tools.