This guide provides a comprehensive overview of the configuration steps and best practices for migrating users from Microsoft 365 to Google Workspace using CloudM Migrate. The process outlined here supports the migration of Mail, Contacts, Calendars, Documents, Tasks, and private chats.
Before proceeding, ensure you have completed the initial project setup as detailed in our comprehensive Migration Guide.
1. Adding Items to a Migration Batch
When adding users to your migration batch, you must manually specify the source and destination details.
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.
The following fields are optional and are only required if you are using CloudM Migrate to automatically create the user at the destination:
Given Name: The user's first name at the destination.
Family Name: The user's surname at the destination.
Note: For a standard user migration, leave the Documents Path and Documents Destination Path fields blank to migrate from and to the root of the user's Drive. Specifying a Documents Path will allow you to migrate a specific Document Library. Leaving this blank will migrate the default "Documents" library (recommended).
You must enable the Migrate checkbox for all entities you intend to include in the migration run. Further instructions on adding entities to your batch can be found in the Adding Items to a Migration Batch article.
2. Configuration Settings
While most settings can remain at their default values for a standard migration, review the following sections to customize your migration.
General Settings
Domain Mappings: Ensure all domain mappings are correctly configured to facilitate the replacement of the source domain with the destination domain during the migration.
Date Range Filters: To migrate information within a specific timeframe, you can apply date range filters for various data types.
Source Settings
Teams Chat API Licensing Model: If you are migrating Conversations (Private Chats), you must specify a licensing model. As this feature uses a metered API, a payment model must be specified. If you select 'None,' the migration will run in the default evaluation mode. For more information, refer to the Microsoft Teams API licensing model.
Export Chat Message Type: Set this to "Email" if you plan to migrate private chats for users.
Destination Settings
Create Users: Enable this option if you want the migration tool to automatically create the users at the destination. Note: It is generally recommended to create users manually or via PowerShell to ensure licensing and OneDrive are correctly provisioned before migration.
Private Chat Top-Level Folder: Specify the name of the top-level folder where all user conversations will be displayed in the mailbox.
3. The Migration Process
For a complete guide that covers project planning, communication, and a detailed phased migration workflow (including initial bulk migrations and subsequent delta passes), please review our comprehensive recommended strategy article: