This article provides instructions on configuring a migration batch for moving users between Microsoft 365 tenants. The setup process outlined here focuses on migrating Mail, Contacts, Calendars, Documents, Tasks, Notes, and Conversations (Private Chats).
Before proceeding, ensure you have completed the steps in the Microsoft 365 to Microsoft 365 Migration Guide to set up your migration project and added users to your migration batch.
Adding Items 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: OneDrive folder name to migrate from at the source (optional; leave blank if migrating from the root of the user's OneDrive)
- Documents Destination Path: OneDrive folder name to migrate to at the destination (optional; leave blank if migrating to the root of the destination user's OneDrive)
For each user entry, select the specific items you wish to migrate. Make sure the 'Migrate' option is enabled for all users 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 user-to-user migration, it is recommended to keep most of the source settings at their default values. However, some settings may need adjustment:
-
SharePoint Online -> Default document library name: Modify this setting to match the language used in your source tenant.
-
Microsoft Teams/Groups -> Teams chat API licensing model: If migrating Conversations (Private Chats), select the appropriate licensing model. As this function uses a metered API, a payment model must be specified. If 'None' is selected, the default evaluation mode will be applied. More information is available here.
Destination Settings
Depending on your migration plan, you may need to modify several settings in this section:
-
SharePoint Online -> Migrate previous document versions: Enable this option to migrate previous versions of documents in users' OneDrive. Enabling this feature allows you to select the number of versions to migrate but will significantly increase migration run times.
-
SharePoint Online -> Include document metadata: Enable this to migrate both standard and custom document metadata, including text, boolean, number, and datetime fields.
-
User -> Create users: Enable this option if you want the migration tool to automatically create users at the destination.
-
Microsoft Teams/Groups -> Rehydrate Teams Private Chats: If migrating Conversations (Private Chats), enable this setting to rehydrate the last 10 messages into the users' Private Chats within Microsoft Teams at the destination. Older messages will be migrated as emails, stored in folders named after the users involved in the private chat.
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.
-
Email -> Private chat top-level folder: Specify the name of the top-level folder in the mailbox where all user conversations will be displayed if migrating Conversations (Private Chats).
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.