This article provides detailed instructions on configuring a migration batch to move users and their data between two Microsoft 365 tenants. The process covers migrating Mail, Contacts, Calendars, Documents (OneDrive), Tasks, Notes, and Teams Private Chats.
Before you start, make sure you have already set up your migration project and created a user batch as outlined in our Migration 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).
- Documents Path: Specify a Document Library name. Otherwise, leave this blank to migrate the default "Documents" library (recommended).
- Documents Destination Path: Specify a folder name within the destination user's OneDrive to migrate to. (Optional: leave blank to migrate to the root of their destination OneDrive).
*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, pay attention to the following:
- SharePoint Online > Default document library name: This setting must match the name of the document library used by OneDrive in your source tenant. For example, English tenants use "Documents", but other languages will use a different name (e.g., "Dokumente" for German).
-
Microsoft Teams/Groups > Teams chat API licensing model: This is a required setting if you are migrating Conversations (Private Chats).
- Note: Migrating private chats uses a metered Microsoft API that may incur costs from Microsoft. You must specify a payment model. If you select 'None', the migration will run in the default evaluation mode. More information is available here.
If you would like to modify any additional source settings, please review the below article.
Microsoft 365 - Source Settings
Destination Platform Settings
Adjust the following settings based on your migration requirements:
- User > Create users: Enable this option if the user accounts do not yet exist in the destination tenant. CloudM Migrate will create them automatically during the migration process.
-
SharePoint Online > Migrate previous document versions: Enable this to migrate the version history of documents stored in OneDrive.
- Warning: While useful, enabling this feature can significantly increase the total migration time. You can specify the number of versions to migrate.
- SharePoint Online > Include document metadata: Enable this to migrate standard and custom document metadata, including fields for text, boolean values, numbers, and dates/times.
- Microsoft Teams/Groups > Rehydrate Teams Private Chats: If migrating private chats, enable this setting to restore the most recent messages (up to 10) directly into the users' Microsoft Teams client. Older messages are archived into the user's mailbox.
If you would like to modify any additional destination settings, please review the below article.
Microsoft 365 - Destination Settings
Advanced Settings
While most advanced settings can be left at their defaults, the following is highly recommended for any M365 to M365 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.
- Email > Private chat top-level folder: When migrating Conversations (Private Chats), this setting defines the name of the folder created in each user's mailbox where the archived chat history will be stored.
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: