logo
search
Google Workspace Migration

Migrate from Google Workspace to Microsoft 365 Without Moving Domain

Maira MehtabMaira Mehtab Sep 22, 2026 869 views

Question details

The user needs to migrate their workspace from Google to Microsoft 365 without transferring their primary domain before the migration is complete.

Product
Microsoft 365
Device & OS
not provided
Scenario
Migrating email and calendar data from Google Workspace to Microsoft 365 while ensuring current mail delivery remains uninterrupted.
Observed behavior
A primary domain does not need to be transferred to Microsoft beforehand; verification uses a DNS TXT record while mail delivery stays with Google until the cutover.
Before you start

Ensure you have global administrator access to both your Microsoft 365 admin center and your domain's DNS hosting provider before starting the migration.

Solution 1Recommended

Verify Domain via TXT Record and Migrate Data

Add your domain to Microsoft 365 and verify it using a TXT record, allowing you to migrate data without altering your current Google Workspace mail flow.

During a workspace migration, your primary domain does not need to be fully transferred to Microsoft immediately. You can verify ownership through a DNS TXT record, which keeps your mail delivery active on Google Workspace until you are completely ready for the final cutover.

1
Add Domain to Microsoft 365

Log in to the Microsoft 365 admin center, navigate to Settings > Domains, and click on 'Add domain'. Enter your primary domain name.

2
Verify via TXT Record

Select the option to verify your domain using a TXT record. Log in to your DNS host and add the provided TXT record to verify ownership without changing your MX records.

3
Migrate Workspace Data

Configure your users and migration prerequisites in the Microsoft 365 Exchange admin center, then execute the migration batch for mail and calendar data.

4
Perform Final Cutover

Only update your MX records and Autodiscover CNAME records (e.g., autodiscover.outlook.com) during the final cutover phase once all data is successfully migrated.

Important DNS Warning: Do not change the autodiscover CNAME to autodiscover.outlook.com until your migration plan requires it. Premature DNS changes can severely disrupt your existing Google Workspace environment.
Free Microsoft Office alternative

Use WPS Office as Your Lightweight Productivity Solution

While migrating your backend infrastructure to Microsoft 365, you might seek a lightweight, cost-effective desktop client for your users. WPS Office is a highly compatible, free Microsoft Office alternative that handles Word, Excel, and PowerPoint files natively, making it a perfect addition to your newly migrated ecosystem.

  1. 1. Download WPS Office: Visit the official WPS website to download and install the free WPS Office suite on your local device.
  2. 2. Open Office Documents: Launch WPS Office and directly open your existing Microsoft Word, Excel, or PowerPoint files natively without needing any format conversion.
  3. 3. Save and Sync: Edit your documents and save them in standard Microsoft Office formats to ensure seamless compatibility and sharing across your organization.
Free, lightweight, and fast deployment across enterprise environments.Highly compatible with Microsoft Office formats including DOCX, XLSX, and PPTX.Familiar user interface ensuring seamless migration and zero learning curve for users.Built-in PDF editing tools for comprehensive document management.
microsoft office alternative - wps office

Frequently Asked Questions

Can I receive emails in Microsoft 365 while migrating from Google Workspace?

No, mail delivery remains with Google Workspace until you update your domain's MX records to point to Microsoft 365 during the final migration cutover.

What happens if I update the Autodiscover record too early?

Changing the Autodiscover CNAME record before completing the migration can disrupt your existing Google Workspace environment, potentially preventing users from accessing their current mailboxes.

Do I need to transfer my domain registrar to Microsoft?

No, you do not need to transfer your domain registrar. You only need to verify domain ownership in Microsoft 365 by adding a temporary TXT record to your current DNS host.