Skip to main content

Migrating Google Workspace Users to Microsoft 365 Users

This article provides instructions on configuring a migration batch for migrating users from Google Workspace to Microsoft 365. The setup process outlined here focuses on migrating Mail, Contacts, Calendars, Documents and Tasks.

Before proceeding, ensure you have completed the steps in the Migration Guide to set up your migration project and added users to your migration batch.


1. Adding Entities to Migrate

When preparing to migrate users to corresponding accounts at the destination, follow the format below:

  • *Export Type: User
  • *Export Name: Source primary email address
  • *Import Type: User
  • *Import Name: Destination primary email address
  • Given Name: User's first name at the destination (leave blank if the user already exists at the destination)
  • Family Name: User's surname at the destination (leave blank if the user already exists at the destination)
  • Documents Path: ID of the users MyDrive folder to migrate from at the source (optional; leave blank if migrating from the root of the source user's MyDrive)
  • Documents Destination Path: Path of the folder to migrate to at the destination (optional; leave blank if migrating to the root of the destination user's MyDrive)

*Mandatory Field

Further instructions on adding entities to your batch can be found here: Adding Items to a migration batch

For each entity added, you can select the specific data types you wish to migrate. Ensure the 'Migrate' checkbox is enabled for all entities you intend to include in the migration run.


2. Configuration Settings

General Settings

In the General Settings section, ensure all domain mappings are configured correctly to facilitate replacing the source domain with the destination domain during the migration.

You can also apply date range filters for various data types to migrate information within a specific timeframe. Specify the date ranges you wish to include.

Source Settings

For a standard user-to-user migration, it is recommended to keep the source settings as default. However, depending on your specific requirements, you might need to modify certain settings. Detailed information about each setting can be found in the article linked below:
Google Workspace - Source Settings

Destination Settings

For a standard user migration, most settings can be left at their default values. However, you may want to consider the following options:

  • SharePoint Online -> Migrate previous document versions: Enable this option to migrate previous major versions of documents in the migrating document libraries. Enabling this feature allows you to select the number of versions to migrate but will significantly increase migration run times.

  • SharePoint Online -> Maximum number of previous document versions: Select the number of versions you plan to migrate.

  • User -> Create users: Enable this option if you want the migration tool to automatically create users at the destination.

Depending on your specific migration scenario, you may need to adjust additional settings. The article below provides a detailed overview of all available destination settings for Microsoft 365:

Microsoft 365 - Destination Settings

Advanced Settings

For a straightforward user-to-user migration, most advanced settings can remain at their default values. However, consider the following:

  • Address Replacement: It is highly recommended to upload an address replacement CSV that maps source users to their corresponding destination users. This ensures permissions are correctly migrated. For more information, please refer to the Address Replacements article.

Additional settings are outlined here: Advanced Settings


 

3. The Migration Process

For a complete, in-depth guide that covers project planning, user communication, and detailed pre- and post-migration checklists, please review our comprehensive recommended strategy article:

CloudM's Recommended Migration Strategy

Was this article helpful?
1 out of 1 found this helpful