Google Workspace Migration

Plan Domains and Subdomains for Google Workspace to Microsoft 365 Migration

Emma BrownEmma Brown Nov 3, 2026 869 views

Question details

The user needs to plan a migration from Google Workspace to Microsoft 365 where the primary domain and alias domain configurations differ between the two platforms.

How to Plan Domains and Subdomains for Google Workspace to Microsoft 365 Migration
Product
Microsoft 365
Device & OS
not provided
Scenario
Setting up domains for an email migration from Google Workspace (primary: abc.co, alias: abc.com) to Microsoft 365 (primary: abc.com).
Observed behavior
The user is preparing migration batches and needs to know how to map the domains correctly, while observing that large mailboxes may become suspended during the transfer.
Before you start

Ensure you have global administrator access to both your Google Workspace admin console and Microsoft 365 admin center, and that all necessary domains are verified in Microsoft 365.

Solution 1Recommended

Configure Mismatched Primary and Alias Domains for Migration

Set up your target domains and aliases in Microsoft 365 before initiating migration batches to ensure proper routing of migrating emails.

When migrating from Google Workspace to Microsoft 365, the domains do not need to match exactly in their primary status, as long as both domains are verified and correctly assigned to the target user accounts in Microsoft 365.

1
Verify domains in Microsoft 365

Log into the Microsoft 365 admin center, navigate to Settings > Domains, and add both the old primary domain (e.g., abc.co) and the new primary domain (e.g., abc.com).

2
Set the primary domain

In the Domains section, select your intended primary domain (abc.com) and click 'Set as default'. This ensures all new outbound mail uses this domain.

3
Configure user aliases

Go to Users > Active users. For each migrating user, ensure the old Google Workspace primary domain (abc.co) is added as an email alias (proxyAddress) so they continue receiving emails sent to their old address.

4
Initiate migration batches

Open the Exchange admin center, navigate to Migration, and create a new migration batch following the Google Workspace migration wizard. Map the source emails to the new Microsoft 365 primary target emails.

Configure Mismatched Primary and Alias Domains for Migration
Monitor Large Mailboxes: Keep a close eye on the migration batch status. Exceptionally large mailboxes (e.g., 70 GB+) may become suspended before reaching 100% completion due to throttling limits. You may need to manually resume them in the Exchange admin center.
Free Microsoft Office alternative

Maintain Productivity During Your Cloud Migration

While planning and executing your domain migration to Microsoft 365, ensure your team experiences zero downtime with their daily document workflows. WPS Office offers a free, highly compatible desktop alternative that works flawlessly offline and online.

Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Allows continuous offline document editing during cloud server migrations.Lightweight, fast installation with a familiar, easy-to-use interface.Free to use, reducing overhead costs during your IT transition.
microsoft office alternative - wps office

Frequently Asked Questions

Can I migrate emails if the primary domains do not match exactly?

Yes. As long as the target domains are verified in Microsoft 365 and you correctly map the destination mailboxes via user aliases or routing addresses, the migration batch will transfer the data successfully.

Why did my large mailbox get suspended during migration?

Large mailboxes often encounter throttling limits or connection timeouts during the migration process. If a mailbox becomes suspended, you can check the error details in the Exchange admin center and manually click 'Resume' to continue the sync.

How do I ensure no emails are lost during the domain switch?

Before updating your MX records to point to Microsoft 365, ensure all users are fully provisioned with their primary addresses and aliases (including the old Google Workspace domains). Once the initial migration sync is complete, update the MX records and perform a final delta sync.