HomeOffice 365How to Migrate Google Workspace Domain to Microsoft 365 (Step-by-Step Guide)

How to Migrate Google Workspace Domain to Microsoft 365 (Step-by-Step Guide)

Migrating from Google Workspace to Microsoft 365 is a common move for organizations that want deeper integration with Microsoft tools like Outlook, Teams, SharePoint, and OneDrive. A proper migration ensures that emails, contacts, calendars, and files are transferred without data loss or downtime.

In this guide, you’ll learn how to migrate a Google Workspace domain to Microsoft 365 step-by-step.

Why Organizations Migrate from Google Workspace to Microsoft 365

Before starting the migration process, it’s helpful to understand why businesses switch platforms.

Key Reasons:

  • Better integration with Microsoft Office apps (Word, Excel, PowerPoint)
  • Advanced security and compliance features
  • Seamless collaboration through Microsoft Teams
  • Strong enterprise management tools
  • Integration with Active Directory and Windows environments

Step-by-Step Process to Migrate Google Workspace to Microsoft 365

1. Prepare Your Microsoft 365 Tenant

First, you need an active Microsoft 365 tenant.

Steps:

  1. Sign in to the Microsoft 365 Admin Center
  2. Purchase appropriate licenses (Business Standard, Business Premium, etc.)
  3. Create user accounts matching your Google Workspace users.

Tip:
Keep usernames identical to simplify mailbox mapping.

2. Verify Your Domain in Microsoft 365

Before migration, you must verify your domain ownership.

Steps:

  1. Go to Microsoft 365 Admin Center
  2. Navigate to Settings → Domains
  3. Click Add Domain
  4. Enter your domain name
  5. Add the TXT verification record to your DNS provider
  6. Verify the domain

Once verified, Microsoft confirms you control the domain.

3. Prepare Google Workspace for Migration

You need to enable migration permissions in Google Workspace.

Steps:

  1. Log in to Google Admin Console
  2. Go to Security → API Controls
  3. Enable API access
  4. Create a Google Cloud Project
  5. Enable Gmail API

Also create a service account with domain-wide delegation for mailbox access.

4. Create Migration Endpoint in Microsoft 365

Now connect Microsoft 365 to Google Workspace.

Steps:

  1. Open Exchange Admin Center
  2. Go to Migration
  3. Select Add Migration Batch
  4. Choose Google Workspace (Gmail) Migration
  5. Upload the JSON key file from Google Cloud

This allows Microsoft 365 to access Gmail mailboxes.

5. Create a User Mapping File

You must map Google accounts to Microsoft 365 accounts.

Example CSV file:

EmailAddress,UserName
user1@domain.com,user1@domain.com
user2@domain.com,user2@domain.com
user3@domain.com,user3@domain.com

Upload this file during migration batch creation.

6. Start the Migration Batch

Once everything is configured:

  1. Upload the CSV mapping file
  2. Start the migration batch
  3. Microsoft 365 begins copying emails from Gmail to Exchange Online

Migration time depends on mailbox size and number of users.

7. Update MX Records

After the migration finishes, switch email delivery to Microsoft 365.

Steps:

  1. Go to your DNS provider
  2. Replace existing Google MX records
  3. Add Microsoft 365 MX records

Example:

domain-com.mail.protection.outlook.com

Once updated, all new emails will be delivered to Microsoft 365.

8. Test and Validate Migration

After migration:

✔ Check user mailboxes
✔ Verify calendars and contacts
✔ Confirm email sending and receiving
✔ Test Outlook and mobile device access

This ensures everything works correctly.

9. Decommission Google Workspace (Optional)

Once fully migrated:

  • Backup important data
  • Cancel Google Workspace subscriptions
  • Remove old MX records

Best Practices for a Smooth Migration

Follow these tips to avoid issues:

  • Perform a pilot migration with a few users first
  • Inform users about possible email downtime
  • Backup critical data before migration
  • Schedule migration during low business hours
  • Use professional migration tools if handling large organizations

Common Migration Challenges

1. Large Mailbox Sizes

Large Gmail mailboxes can slow migration.

Solution:
Run migration batches in phases.

2. API Permission Errors

Incorrect Google API configuration can block migration.

Solution:
Verify service account and domain-wide delegation.

3. DNS Propagation Delays

MX record changes can take time.

Solution:
Lower TTL values before switching.

Final Thoughts

Migrating from Google Workspace to Microsoft 365 can significantly improve collaboration, security, and productivity if done correctly. By following the proper migration steps, testing thoroughly, and planning DNS changes carefully, organizations can ensure a smooth transition without losing critical data.

If your organization has many users or large data volumes, using a professional migration tool or expert assistance can make the process much faster and safer.

Related Posts