#Microsoft 365 Groups to Google Groups Migration Process

The sections below contain the general migration process for Microsoft 365 Groups to Google Groups Migration. The details outlined in this document can serve as general guidelines with some minor adjustments.

• Preparation
• Migration Execution

More steps may be needed, and some steps included in the process may be optional according to your migration requirements.

#Preparation

Before the migration, you need to identify what object types you want to migrate. See the Supported and Unsupported List.

#1. Create a service account, app profile, or delegate app with required permissions for source connection

To connect Fly to your Groups, create a service account, an app profile, or delegate app with the required permissions for the source connection.

#2. Create a custom app profile with required permissions for destination connection

To connect Fly to your Google Groups, create an app profile with the required permissions for the destination connection.

#3. Run the source tenant discovery (optional)

Before you migrate from Microsoft 365 Groups, you can run a tenant discovery of Microsoft 365 Groups to scan and report the object count, object type, object size, and other details. According to the discovery reports, you can better understand your source environment and plan for your migrations. Refer to the user guide for Tenant Discovery for details.

#4. Create users in destination tenant

User mappings are required when executing migrations. Make sure users of the following data are created in the destination tenant before the migration.

• Group Membership

• Mail: To, Cc, Bcc, Senders, etc.

• Permission

• Other data that needs users

#5. Create Groups and shared drives in destination tenant (optional)

Fly can create Groups and shared drives in the destination. If you want to migrate to existing Groups and shared drives, you can create Groups and shared drives in the destination before the migration.

#6. Create source and destination connections

Refer to Create a Connection to connect Fly to your source and destination. The source connection including both the app profile and service account is recommended. The destination connection using the Google custom app profile is recommended.

#7. Migration throughput

In Microsoft 365 Groups to Google Groups migrations, the job speed depends on the size of SharePoint team sites and the size of Group mailboxes.

SharePoint Site Migration Throughput

Generally, a reasonable SharePoint site migration speed is about 2 GB/hour/mapping. The number of mappings that run in parallel is automatically allocated based on your purchased subscription. The more subscriptions you purchase, the more mappings you can run in parallel.

Mailbox Migration Throughput

Generally, a reasonable migration speed of the mailbox is 1.5 GB/hour/mapping. The number of mappings that run in parallel is automatically allocated based on your purchased subscription. The more subscriptions you purchase, the more mappings you can run in parallel.

We can calculate how much content can be migrated with the above infrastructure.

There are many factors which may affect the migration performance:

• The above throughput number is for the full migration. Generally, it may be lower for the incremental migration since Fly needs to spend quite some time checking the migrated items’ status for the incremental migration.

• The above results are only ideal values after many tests. The migration speed of different tenants may be different. We recommend that you estimate the daily throughput in the same way as the results of the pilot job.

#8. Prepare mapping files

Configure Microsoft 365 Groups to Google Groups mapping files and user mapping files:

• Examples in the Microsoft 365 Groups to Google Groups mapping file

  

• Examples in the user mapping file

  

#9. Design the migration policy

A Microsoft 365 Groups to Google Groups migration policy allows you to define the migration scope of group objects, the conflict resolutions, whether to replace source email addresses of sender/recipients, and how to map users. Refer to Create a Migration Policy for details.

#10. Plan a pilot run

We recommend you perform a pilot run for the following purposes:

• Get familiar with the Fly interface and understand the whole migration process.

• Discover and resolve any potential issues before production migration.

• Understand the throttling situation in case content size is large, and then try to resolve with the destination.

#Migration Execution

Refer to the following sections to execute the migration.

#1. Configure projects and mappings in Fly

To configure projects and mappings, refer to the Create a Project and Create Migration Mappings for details. Use the mapping file of data to be migrated to configure the migration project.

#2. Perform regular full migrations

Before running the job, we recommend you verify the mappings to ensure that the mappings are available for migration. Refer to Pre-analyze Mappings for details.

Then you can run a full migration job to migrate the objects based on your configured migration policy. Refer to Run Migrations to Migrate Objects for details.

#3. Perform regular incremental migrations

Some issues may occur during a full migration job. Run an incremental job to handle new, updated, and failed data. Refer to Run Migrations to Migrate Objects about how to perform regular incremental migrations.

#4. Communicate with end users (optional)

Notify end users of the migration schedule. Publish a message in each source Group to inform end users that they can run incremental jobs before final validation.

#5. Perform the final incremental migration

Notify all users and make sure the source Groups do not have any new/modified objects. Then perform the final incremental migration job.

#6. Validate migration results

Note the following items during the validation period:

• Number of files

• Number of mails in Group mailbox

• No failed data in job report

#7. Perform migrations for all other waves (optional)

This step is needed only if you have separated the mappings into multiple waves.

#8. Perform the final incremental migration for other waves (optional)

You can perform the final incremental migration to make sure all source data are migrated to the destination if needed.

#9. Perform the final validation

During the final validation, you should validate members of the destination Google Groups.