This article provides detailed instructions on configuring a migration batch to move users and their data between Microsoft 365 Users and Microsoft 365 Online Archive. The process covers migrating Mail 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.
Prerequisites
Destination users require archive mailboxes to be enabled: Enable archive mailboxes for Microsoft 365
Sample Migration Strategy: Splitting Mailbox Data
It is possible to migrate a subset of a user's data, typically determined by a date range, to their active Microsoft 365 user account (primary mailbox), while migrating the remaining older data directly to their Online Archive.
- Active Mailbox: Recent or frequently accessed mail is migrated to the user's primary mailbox within the new tenant.
- Online Archive: Older or less frequently accessed mail is directed to the user's Online Archive in the destination tenant, freeing up space in the primary mailbox.
This strategy is controlled by configuring specific date range filters within CloudM Migrate, allowing you to define what content goes where.
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: Not required.
- Family Name: Not required.
* 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
We recommend retaining the default source settings for all standard user-to-user migrations to ensure a smooth process. However, for more complex scenarios, advanced options provide granular control over your migration.
Microsoft 365 - Source Settings
Destination Platform Settings
We recommend retaining the default destination settings for all standard user-to-user migrations to ensure a smooth process. However, for more complex scenarios, advanced options provide granular control over your migration.
Microsoft 365 Online Archive - Destination Settings
Advanced Settings
For a standard 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.
Additional settings are outlined here: Advanced Settings
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:
CloudM's Recommended Migration Strategy