Google Workspace Migration

When to Change DNS Records During Google Workspace to Microsoft 365 Migration

Ayan Masood Sep 29, 2026 869 views

Question details

An administrator needs to know the correct timing for updating domain DNS and MX records when migrating mailboxes from Google Workspace to Microsoft 365.

When to Change DNS Records During a Google Workspace to Microsoft 365 Migration

Product: Microsoft 365
Device & OS: not provided
Scenario: Performing a cutover migration from Google Workspace (formerly G Suite) using the Exchange Admin Center, and deciding the exact step to switch the mail routing.
Observed behavior: The migration batch has successfully reached the 'Synchronized' state in the Exchange Admin Center, pending the final cutover steps.

Before you start

Before updating your MX records, consider lowering your DNS TTL (Time to Live) settings to 300 seconds (5 minutes) a few days in advance to ensure rapid propagation during the actual cutover window.

Solution 1Recommended

Update DNS Records During the Planned Cutover Window

The safest approach is to update your DNS records only after the migration batch reaches the 'Synced' status, routing new mail to Microsoft 365 before triggering the final batch completion.

Changing the MX records prematurely will route new emails to Microsoft 365 before the mailboxes are ready, while waiting until after completing the migration batch can result in new emails being delivered to the old Google Workspace mailboxes and potentially lost. The ideal window is right in the middle: after the initial sync, but before the final completion.

Verify synchronization status

Log in to the Exchange Admin Center. Navigate to Migration and check your current migration batch. Ensure the status explicitly says 'Synced'. Verify that users can log into their Microsoft 365 accounts and see the migrated data.

Update MX and DNS records

Access your domain registrar or DNS hosting provider's portal. Update your MX records to point to Microsoft 365 (e.g., yourdomain-com.mail.protection.outlook.com). This is also the best time to update your SPF, DKIM, and Autodiscover records.

Confirm new mail flow

Send test emails from an external email address (like a personal Outlook or Gmail account) to the migrated accounts. Confirm that these new emails arrive directly in the Microsoft 365 inbox.

Complete the migration batch

Allow adequate time for global DNS propagation based on your TTL settings. Once confirmed, return to the Exchange Admin Center, select your synced migration batch, and click 'Complete' to perform the final delta synchronization and finalize the migration.

Update DNS Records During the Planned Cutover Window

DNS Propagation Delay: Keep in mind that DNS propagation can take anywhere from a few minutes to 48 hours depending on your previous TTL settings. Wait until you are confident the new MX records have propagated before clicking 'Complete' on the batch.

Free Microsoft Office alternative

Discover a Lightweight and Free Microsoft Office Alternative

As you transition your organization's IT infrastructure, you might be looking for ways to optimize software costs. WPS Office is a highly compatible, free, and lightweight alternative to traditional Microsoft Office desktop applications, making it ideal for viewing, creating, and managing your migration spreadsheets and business documents.

1. Download the installer: Visit the official WPS Office website and download the free installer for your operating system.
2. Install the suite: Run the installation file and follow the on-screen prompts to set up the software on your device in minutes.
3. Open existing Office files: Launch WPS Office and directly open your existing Word, Excel, or PowerPoint files with perfect formatting preservation.

Fully compatible with Microsoft Office formats including DOCX, XLSX, and PPTX.Free and lightweight alternative to subscription-based desktop office applications.Familiar user interface that requires zero learning curve for seamless employee onboarding.Excellent tool for IT administrators to manage migration checklists, DNS configurations, and project spreadsheets.

microsoft office alternative - wps office

Frequently Asked Questions

What happens if I click 'Complete' on the migration batch before changing the MX records?

If you complete the batch before updating the MX records, the final synchronization will finish, but new emails will continue routing to the old Google Workspace mailboxes. Because the sync process has already completed, those new emails will not be migrated to Microsoft 365, resulting in potential data loss.

How long should I wait for DNS propagation before finalizing the migration?

The wait time depends on the Time to Live (TTL) value of your previous DNS records. If you lowered the TTL to 5 minutes beforehand, you might only need to wait an hour. If the TTL was set to default (often 24-48 hours), you should monitor mail flow carefully and wait at least 24 hours to ensure all external mail servers have the updated routing path.

Do I need to update SPF and DKIM records at the same time as the MX record?

Yes. When you point your MX records to Microsoft 365, your users will also start sending outbound emails from Microsoft 365. Updating your SPF and DKIM records simultaneously ensures that outbound emails sent from your new environment are properly authenticated and are not marked as spam by recipients.

Can I leave my Google Workspace account active after the migration?

You can leave Google Workspace active temporarily as a fallback while DNS propagates. However, once the cutover is complete, mail flow is verified, and you no longer need access to the old G Suite data, it is recommended to decommission the source system to avoid ongoing subscription costs.

Migration & Recovery