Google Workspace Migration

How to Migrate Google Workspace Mailboxes to Microsoft 365

Maira Mehtab Sep 22, 2026 869 views

Question details

The user needs to migrate mailboxes from Google Workspace to existing Microsoft 365 accounts, while supporting username changes and configuring role-based addresses like manager@ and office@.

Product: Microsoft 365
Device & OS: not provided
Scenario: Performing an organizational email migration from Google Workspace to Microsoft 365, including the handling of custom usernames and shared roles.
Observed behavior: The goal is to seamlessly transfer email data, ensure users can log in with one address while sending/receiving with another, and ensure role-based emails function properly in Outlook and Teams.

Before you start

Ensure you have global administrator credentials for both Google Workspace and Microsoft 365, and verify that your target domains are successfully added and verified in the Microsoft 365 admin center.

Solution 1Recommended

Migrate Mailboxes via Exchange Admin Center

Use the standard Microsoft 365 migration tools and a properly formatted CSV file to route Google Workspace emails to existing Microsoft 365 destination accounts.

The most reliable method to migrate Google Workspace mailboxes to Microsoft 365 is by utilizing the built-in migration batch tool in the Exchange Admin Center. By carefully preparing a mapping CSV, you can dictate exactly which Google source email maps to which Microsoft destination email, even if the primary names differ.

Create Destination Users

Log into the Microsoft 365 Admin Center, create the destination user accounts, and assign the necessary Exchange Online licenses to each user.

Prepare the Migration CSV

Create a CSV file that maps the source Google Workspace email addresses to the newly created destination Microsoft 365 email addresses. This allows you to handle username changes efficiently during the migration.

Create a Migration Batch

Open the Exchange Admin Center, navigate to 'Migration', and create a new Google Workspace migration batch. Upload your prepared CSV file and follow the wizard to initiate the sync.

Verify and Complete

Monitor the batch progress. Once synced, test sign-in, sending, receiving, and Outlook/Teams behavior before finalizing and completing the migration batch.

Solution 2

Configure Role-Based Addresses and Primary Emails

Address specific identity requirements by using PowerShell for primary email changes and Shared Mailboxes for role-based addresses.

Free Microsoft Office alternative

Enhance Your Workflow with WPS Office

While managing complex enterprise email migrations, equip your team with a lightweight and powerful document processing suite. WPS Office is a highly compatible, cost-effective alternative to Microsoft Office that easily handles Word, Excel, and PowerPoint files without the heavy subscription fees.

Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx)Lightweight installation and lightning-fast launch timesFamiliar tabbed interface requiring zero learning curve for new usersBuilt-in PDF editing and format conversion toolsFree to use with seamless cross-platform syncing

microsoft office alternative - wps office

Frequently Asked Questions

Can I migrate Google Workspace mailboxes into pre-existing Microsoft 365 accounts?

Yes. You can migrate Google Workspace data into existing Microsoft 365 accounts by specifying the existing Microsoft 365 email addresses as the destination in your migration CSV file during the Exchange Admin Center batch setup.

Why are my email aliases not working properly in Outlook and Teams?

Standard email aliases are designed primarily for receiving mail. When multiple users need to send from a specific address (like a role-based email), aliases can be unreliable in clients like Outlook and Teams. It is recommended to use Shared Mailboxes instead.

How do I handle role-based email addresses like office@ or manager@?

The best practice in Microsoft 365 is to configure role-based addresses as Shared Mailboxes. You can then grant specific users 'Send As' and 'Read and Manage' permissions, allowing multiple people to monitor and reply from the same address without requiring additional licenses.

How can I change a user's primary email address without altering their login username?

You can achieve this by using Exchange Online PowerShell. Run the command 'Set-Mailbox current@domain.com -WindowsEmailAddress new@domain.com'. This updates the primary routing address while keeping the original User Principal Name (UPN) intact.

Migration & Recovery