This article provides instructions on configuring a migration batch for migrating resources from Google Workspace to Microsoft 365. The setup process outlined here focuses on migrating calendar items.
Before proceeding, ensure you have completed the steps in the Google Workspace to Microsoft 365 Migration Guide to set up your migration project and added resources to your migration batch.
Adding Items to Migrate
When preparing to migrate resources to corresponding accounts at the destination, follow the format below:
- Export Type: Resource
- Export Name: Source resource email address
- Import Type: Resource
- Import Name: Destination resource email address
- Given Name: Not required
- Family Name: Not required
- Documents Path: Not required
- Documents Destination Path: Not required
For each resource entry, you can only migrate calendar items. Make sure the calendar option and the 'Migrate' option is enabled for all resources included in the migration.
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 resource-to-resource migration, it is recommended to keep most of the source settings at their default values. Detailed information about each setting can be found in the article linked below:
Google Workspace - Source Settings
Destination Settings
For a standard resource-to-resource migration, it is recommended to keep most of the destination settings at their default values.
The article below provides a detailed overview of all available destination settings for Microsoft 365:
Microsoft 365 - Destination Settings
Advanced Settings
For a straightforward resource-to-resource 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 resources, users and groups to their corresponding destination resources. For more information, please refer to the Address Replacements article.
Additional settings are outlined here: Advanced Settings
Migration Process
The migration process will vary depending on your project's specific approach. Generally, it is advisable to start with a bulk migration and perform delta migrations closer to the final migration cutover date.