Skip to main content

Migrating Microsoft 365 Groups to Microsoft 365 Groups

This article provides detailed instructions on configuring a migration batch to migrate Microsoft 365 Groups and their data between two Microsoft 365 tenants. The process covers migrating mail, calendar and documents.

Before you start, make sure you have already set up your migration project and created a Microsoft 365 Group 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: Microsoft 365 Group

  • *Export Name: The primary email address of the source group.

  • *Import Type: Microsoft 365 Group

  • *Import Name: The primary email address of the destination group.

  • Given Name: The name of the destination group.

  • Family Name: The description of the destination group.

*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 groups 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 group-to-group migration, it is recommended to keep most of the source settings at their default values.

If you would like to modify any additional source settings, please review the below article.
Microsoft 365 - Source Settings

Destination Platform Settings

For a standard group-to-group migration, it is recommended to keep most of the destination settings at their default values.

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 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.

If you would like to modify any additional advanced settings, please review the below article.

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

Was this article helpful?
0 out of 0 found this helpful