This article provides detailed instructions on configuring a migration batch to move users and their data from Hosted Microsoft Exchange to Google Workspace users. The process covers migrating Mail, Contacts, Calendars, and Tasks only.
Before you start, make sure you have already set up your migration project and created a user batch as outlined in our Migration Guide.
Supported Hosted Exchange Providers
Hosted Microsoft Exchange is a hosted mailbox only service for users providing mail, contacts and calendars only.
It is not to be confused with Hosted Microsoft 365, for which we recommend our Migrating Microsoft 365 Users to Google Workspace Users guide.
|
|
1. Adding entities to your batch
Before configuring settings, you must add entities to your migration batch. This defines what is being migrated and where their data will go. Use the following format for each entity you add.
- *Export Type:
User - *Export Name: The primary email address of the source user.
- *Import Type:
User - *Import Name: The primary email address of the destination user.
- Given Name: The user's first name in the destination. (This can be left blank if the user account already exists).
- Family Name: The user's last name in the destination. (This can be left blank if the user account already exists).
*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
Once users are added, you must review and configure the migration settings. These are separated into several sections.
General Settings
- Review Domain Names: Correctly configure all domain mappings. This is essential for replacing the source domain with the destination domain on email addresses and permissions during the migration.
- Date Filters: You can apply date range filters to migrate data created within a specific timeframe. If no filter is set, all items will be migrated regardless of age.
Source Platform Settings
For a standard user-to-user migration, most source settings can remain at their default values. However, if you would like to modify any additional source settings, please review the below article.
Hosted Microsoft Exchange - Source Settings
Destination Platform Settings
For a standard user-to-user migration, most destination settings can remain at their default values. If you would like to modify any additional destination settings, please review the below article.
Google Workspace - Destination Settings
Advanced Settings
While most advanced settings can be left at their defaults, the following is highly recommended for any Microsoft to Google migration:
-
Address Replacement: Uploading an Address Replacement CSV file is critical for maintaining data fidelity. This file maps all source user email addresses to their new destination addresses.
- Why is this important? This process ensures that permissions on shared files, calendar entries, and other collaborative content are correctly re-assigned to the new user accounts. Without it, users may lose access to shared data or errors may occur during the migration process.
- For more information, refer to the Address Replacements article.
If you would like to modify any additional advanced settings, please review the below article.
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: