MX records tell other mail systems where to deliver messages for a domain, but a successful Gmail cutover also requires prepared recipients, licensing, routing, domain authentication, testing, and support.
What an MX Record Does
A Mail Exchange record tells sending mail servers which host should receive email for a domain. The record includes a destination and priority.
MX records affect inbound delivery. They do not configure outbound authentication, create mailboxes, migrate historical email, or guarantee that every recipient exists.
Use the Values Provided by Google
Google's current setup flow may provide a simplified MX target for new configurations, while older Google Workspace environments may still use legacy Google MX hosts.
Use the values displayed in the current Admin console or official setup instructions for the specific tenant. Do not mix partial record sets from different guides.
Copy the tenant's current instructions
DNS guidance changes over time, so the implementation record should show exactly which Google-provided values were used.
Understand Priority
Lower priority numbers are generally preferred. When several MX records exist, sending servers normally try the available destinations according to priority and availability.
Do not leave an old provider at a competing or higher-preference priority unless a planned coexistence design requires it.
Inventory Existing MX Records
Before changing anything, record the current MX hosts, priorities, time-to-live values, DNS provider, mail provider, and date.
Determine whether the domain uses an email security gateway, spam filtering service, continuity service, split delivery, or another system in front of the current mailbox provider.
Inventory Every Recipient
List users, groups, aliases, shared addresses, automated systems, former employee addresses, catch-all behavior, and special routes.
Messages sent after cutover will fail or route incorrectly when the destination has not been created or intentionally mapped.
Prepare User Accounts
Create licensed users with the correct primary email addresses and organizational-unit placement.
Verify passwords, 2-Step Verification enrollment, Gmail service status, and first-day communication before directing production mail to Google.
Prepare Groups and Shared Addresses
Create Google Groups, collaborative inboxes, aliases, delegated mailboxes, or routing rules for departmental addresses.
Do not create one shared user password for addresses such as accounting, support, or information merely because the old provider used shared credentials.
Prepare Secondary and Alias Domains
Every domain that should receive Gmail delivery needs the correct domain addition, verification, activation, and mail routing.
Confirm whether the domain is a secondary domain or user alias domain and test addresses under that domain.
Lower DNS Time to Live
When the DNS provider and project plan permit it, reduce the MX time-to-live in advance of the cutover. This can help resolvers refresh the change sooner.
Lowering the value at the moment of cutover does not remove records already cached under the previous value.
Do not change MX records without a rollback record
Save the original hosts, priorities, screenshots, provider access, and restoration steps before the approved change window.
Choose the Cutover Window
Select a time with low business activity and available technical support. Avoid payroll deadlines, major events, fundraising campaigns, legal deadlines, and critical customer periods.
Communicate expected timing, possible delays, support contact, and device sign-in instructions.
Change the MX Records
Remove or replace the old provider records according to the approved mail architecture, then add the exact Google-provided records and priorities.
Save the configuration and verify the authoritative DNS response. Some provider interfaces automatically add the domain name to host values, so avoid accidental duplication.
Activate Gmail in the Admin Console
The setup flow may require an administrator to confirm that MX records are ready and activate Gmail for the domain.
Follow the current tenant prompts and confirm the Gmail service status for the intended users and organizational units.
Understand DNS Propagation
Different sending systems may cache the old MX answer for different periods. During the transition, some mail can arrive at Google while other mail still reaches the previous provider.
Keep the old environment accessible during the agreed coexistence period and monitor both systems.
Test Inbound Delivery
Send messages from multiple external providers to pilot users, aliases, groups, secondary-domain addresses, and shared addresses.
Verify the final mailbox, spam classification, recipient identity, timestamps, attachments, and replies.
Test Outbound Delivery
Send from pilot users and business addresses to multiple external domains. Review message headers for SPF, DKIM, DMARC, and TLS results.
Confirm that replies return to the intended address and that no old provider or gateway rewrites the sender unexpectedly.
Review Email Log Search
Use Email Log Search to trace accepted, delivered, rejected, quarantined, or routed messages according to available edition and retention.
Record sender, recipient, timestamp, and message identifier during troubleshooting.
Keep the Old Provider Temporarily
Do not cancel the old mail service immediately after changing MX records. Historical email, delayed senders, forwarding, archives, or migration tasks may still depend on it.
Set an approved end date and confirm migration and mail flow before cancellation.
Configure SPF
Update the domain's SPF policy to authorize Google and every other approved sender. Maintain one valid SPF record for the domain.
Remove retired provider mechanisms after confirming no systems still send through them.
Enable DKIM
Generate or obtain the DKIM record for each sending domain, publish it in DNS, then enable signing in the Admin console.
Verify the signature through received message headers.
Deploy DMARC Carefully
Begin with monitoring when the organization does not yet have a complete sender inventory. Review reports, correct legitimate alignment failures, then increase enforcement in stages.
A strict policy published too early can block business applications and vendors.
Troubleshoot No Inbound Mail
Check authoritative MX records, Gmail activation, user existence, aliases, groups, suspended status, domain verification, routing, gateways, and Email Log Search.
Confirm that the sender did not use a cached old route and that the old provider did not generate a bounce.
Troubleshoot Split Delivery
When some users remain at another provider, ordinary MX changes are not enough. The organization needs a documented split-delivery or dual-delivery design.
Define the authoritative directory, unknown-recipient behavior, loops, routing headers, and removal date.
Complete the Cutover Review
Confirm users, groups, aliases, mail flow, authentication, migrated data, mobile devices, applications, printers, websites, alerts, and support cases.
Raise time-to-live back to the normal standard when appropriate and document the final DNS state.
MX and Gmail Activation Checklist
- Record current MX records and mail architecture.
- Use the Google-provided values for the tenant.
- Create users, groups, aliases, and routes before cutover.
- Prepare secondary and alias domains.
- Save rollback records and DNS access.
- Choose a supported cutover window.
- Update MX records and complete Gmail activation.
- Monitor both old and new providers during propagation.
- Test inbound and outbound mail broadly.
- Validate SPF, DKIM, DMARC, and TLS.
- Keep the old provider until migration and validation are complete.
- Document the final records and review results.
Frequently Asked Questions
Should I delete every old MX record?
In a normal full cutover, old provider records are removed or replaced. A planned gateway or coexistence design may require different records.
Why is mail arriving at both providers?
Some senders may still have cached DNS, or competing MX and routing rules may remain active.
Do MX records migrate old email?
No. They direct new inbound mail. Historical data requires a separate migration process.
When Professional Support Helps
Professional support can inventory recipients, plan the cutover, update MX records, activate Gmail, configure authentication, monitor delivery, and preserve rollback options.
Need help applying this?
Set up and migrate Google Workspace with confidence.
J3 Systems Group LLC can plan Google Workspace deployments, verify domains, configure DNS and Gmail, design identities, migrate email and files, validate cutovers, and document the environment.