#Create a Migration Policy

A Microsoft 365 Groups migration policy allows you to define the migration scope of group objects, the conflict resolutions, whether to replace source email addresses/meeting links with destination, how to map users, and how to manage the sensitivity labels of files/emails/Groups for Microsoft 365 Groups migrations.

#Migration to Microsoft 365 Groups

For Microsoft 365 Groups to Microsoft 365 Groups migration, configure a To Microsoft 365 Groups migration policy by completing the following steps:

1. Click Policies under Settings in the left pane.

2. Click Migration policies to access the Migration policies page.

3. Click the Microsoft 365 Groups tab and click To Microsoft 365 Groups.

4. Click Create migration policy. The Create migration policy panel appears.

5. Enter a name and an optional description for the policy, and then click Next.

6. In the What do you want to migrate? Section, configure filters to define the objects you want to migrate:

   • Group – Select Planner and/or Membership if you want to migrate the planner data and/or Group members. With the Membership option selected, you can continue selecting to migrate guest users.

     Guest users are added via the Microsoft 365 admin center, and can be added as group members.

     

   • SharePoint team site – Choose whether to migrate the following objects of source team sites.

     • All data in SharePoint team site – Select this checkbox to migrate all data of source team sites.

     • Only the default Documents library – Select this check to migrate only the default Documents libraries in team sites of Teams and private channels.

   • Group mailbox – Select the Mailbox checkbox to migrate the mailbox items of source Group mailboxes.

7. Migration policy for team site and group mailbox – Select a policy type according to your requirements.

   • Simple policy – This option allows you to customize how to migrate Group data. However, the migration scope of SharePoint and Exchange data cannot be customized.

     Note that SharePoint and Exchange data will be migrated based on the default settings that are pre-configured when you first create a corresponding policy without any changes. Refer to the following screenshots for details.

     

     SharePoint data that will be migrated.

     

     Exchange data that will be migrated.

   • Use custom SharePoint Online and Exchange Online migration policies – If you want to also customize how to migrate SharePoint and Exchange data, select this option to configure and use SharePoint and Exchange migration policies.

     With this option, you can ignore step 8 and the mail/file configurations in step 10, including Replace email addresses of senders/recipientsbased on user mappings, Replace meeting links with the destination information, and options of managing the sensitivity labels of files/emails during the migration.

     Note that if you have configured the filter policy in the SharePoint migration policy and will run the full migration job in Groups migrations with the SharePoint migration policy, do not change the filters in subsequent incremental jobs.

8. In the Conflict resolution section, configure the following conflict resolutions when the source object conflicts with an existing one in the destination**.**

   • SharePoint team site (includes: sites and lists/libraries) – Refer to the following detailed information on each conflict resolution for source team sites and the lists/libraries within.

Resolution	Conflict	No Conflict
Skip	Ignore the conflicting object and do nothing in the destination.	A new object will be created.
Merge	Merge the source and destination objects.	A new object will be created.

Resolution	Conflict	No Conflict
Skip	Ignore the conflicting file and do nothing in the destination.	A new file will be created.
Overwrite	Delete the conflicting file in the destination first and overwrite it with the source file.	A new file will be created.
Overwrite by last modified time	The conflicting file with the latest modified time will be preserved in the destination.	A new file will be created.

Resolution	Conflict	No Conflict
Skip	Ignore the conflicting item and do nothing in the destination.	A new item will be created.
Overwrite	Delete the conflicting item in the destination first and overwrite it with the source item.	A new item will be created.

1. Click Next after you finish configuring the conflict resolutions.

2. In the Additional options & mappings step, configure the following settings for the migration.

   • Replace email addresses of senders/recipients based on user mappings – Select this checkbox if you want to replace the source email addresses of email senders/recipients with the destination ones. To make this setting available in the migration, you must configure user mappings for the source email addresses.

   • Replace meeting links with the destination information – With this checkbox selected, the Teams meeting links in emails will be replaced with the destination information and correctly linked to the meeting when users click them. If it is not selected, the meeting links can be kept but cannot be directed to the meeting. To make this setting available in the migration, you must configure user mappings for the source meeting organizers. When you select this option, there are some notes that need your attention, refer to the Notes When Replacing Meeting Links section in for details.

   • Sync privacy settings of Teams/Groups created by Fly – Select this option to synchronize the updated privacy settings of source Groups to destination Groups.

   • Note that this only applies to destination Groups created by Fly after August 10, 2025.

   • To manage the sensitivity labels of files/emails during the migration, select an option below:

     Note that if the source does not have the Microsoft Information Protection (MIP) service implemented or source files/emails do not have any sensitivity labels applied, select the first option for your migration to ensure a successful job.

     • No label insource, or migratefiles/emails with source label to destination (if file/email has label encryption, it will be inaccessible in the destination) – Select this option if there is no sensitivity label applied on source files/emails, or you want to keep the source sensitivity labels of the files/emails to the destination.

       After the migration, the migrated files/emails that have label encryption may not be accessed in the destination.

     • If a label exists, remove it during the migration (source label remains, it is removed from the file/email in the destination) – Select this option if you want to remove the source sensitivity labels from the files/emails.

       After the migration, the migrated files/emails do not have any sensitivity labels and can be accessed in the destination.

     • Apply same label in the destination (same label must exist in the destination) – This option removes the source sensitivity labels from the migrated files/emails during the migration, and applies existing destination sensitivity labels with the same display name to the migrated files/emails in the destination. The source sensitivity labels applied to source files/emails will not be removed from the source tenant.

     • Apply labels in the destination based on label mappings (labels must exist in both source and destination) – With this option, you can configure sensitivity label mappings to replace the source sensitivity labels applied to the migrated files/emails with existing destination sensitivity labels.

       According to the label mappings, Fly will remove the source sensitivity labels from the migrated files/emails during the migration, and apply the destination sensitivity labels to the migrated files/emails in the destination. The source sensitivity labels applied to source files/emails will not be removed from the source tenant.

       Click the Add () button to Create Sensitivity Label Mappings to map the source and destination labels based on their display names. You can also select a previously created label mapping from the drop-down list to use it (Clicking View details can view and edit the detailed information of the selected label mapping.).

   • To manage the sensitivity labels of Groups during the migration, select an option below:

     Note that to manage the sensitivity labels, we recommend you provide both the service account and app profile in the destination connection.

     If you only provide a service account or app profile, data in SharePoint sites must be migrated together with Groups. Additionally, if the destination Groups already exist before the migration, make sure the conflict resolution for SharePoint team site is Merge.

     Note that if the source does not have the Microsoft Information Protection (MIP) service implemented or source Groups do not have any sensitivity labels configured in the Sensitivity setting, select the first option for your migration to ensure a successful job.

     • No label in source, or do not copy source label onGroup to destination– Select this option to not keep the source sensitivity labels to the destination Groups.

     • Apply same label in the destination (identical label must exist in the destination) – Select this option to not keep the source sensitivity labels, and apply existing destination sensitivity labels of the same display name to the destination Groups.

     • Apply labels in the destination based on label mappings (labels must exist in both source and destination) – Select this option if you want to configure sensitivity label mappings to map the source sensitivity labels to existing destination labels based on their display names. You can click the Add () button to Create Sensitivity Label Mappings to map the source and destination labels based on their display names.

       If the source Groups are applied with the source labels configured in the mapping, the Sensitivity setting value of their destination sites will be updated to the mapped destination labels.

   • Information rights management – Select the Remove source IRM restrictions from files checkbox if you want to remove the source IRM restrictions during the migration. If you deselect this checkbox, the source IRM restrictions will be kept to the destination, and the migrated files may be inaccessible in the destination.

   • User mapping – With a user mapping, you can map a source user to a destination one. You can also map a domain in the source to a destination domain. Users, securities, and user-related metadata can be migrated based on user mappings. Click Add () button to the right of the field to create a new one. Refer to the Create User Mappings section to view how to create a user mapping.

     You can also select a previously created user mapping from the drop-down list and click View details to view the detailed information of the selected user mapping. You can enter the keyword of a user mapping in the Search user mapping text box and press Enter on the keyboard to search the user mapping.

     Note that for the users that have not been configured in user mappings, you can choose to map the users based on User principal name prefix, Display name, and/or Email address prefix. (Email address prefix is only supported for users of team sites.) Refer to the table below for property examples:

Property	User Principal Name	User Principal Name Prefix	Display Name	Email Address	Email Address Prefix
Property Example	JohnSimon@onmicrosoft.com	JohnSimon@	JohnSimon	JohnSimon@onmicrosoft.com	JohnSimon@

3. Click Next after you finish configuring the options and mappings.

4. Configure the Notifications setting to send migration email notifications to specific recipients after the migration.

   • Send project level notifications (all mappings within a project) – The migration email notifications are based on the project level, which summarizes the project name and the mapping count of each migration status.

     • Recurrence – Enter a positive integer to define the recurrence days for the notifications.

     • Start date and time – Select a start date and time to send the first notification. The later notifications will be sent at the selected time based on the recurrence.

       If you want to configure the end date and time of the notifications, you can select the Configure end date and time checkbox and select a date and time.

     • Send migration email notifications to – Define the recipients who will receive the notifications.

     • Email template – Create an email template for the notifications by clicking the Add () button. Refer to Manage Email Settings for details on how to create an email template. You can also select an existing email template from the drop-down list.

   • Send individual mapping level notifications – The migration email notifications are based on the mapping level, which summarizes the migration status, the project name, the source and destination email addresses, the migration start and finish time, and the migration person.

     • Define the notification scope for mappings – Select For failed mappings only to send notifications for the failed mappings only, or select For all mappings to send notifications for all mappings.

     • Send migration email notifications to – Define the recipients who will receive the notifications.

       • Person running the migration – The person who runs the migration will receive the notifications.

       • Additional recipients – Enter the email addresses of other recipients. Separate multiple email addresses with a semicolon (;).

     • Email template – Create an email template for the email notifications by clicking the Add () button. Refer to Manage Email Settings for details on how to create an email template. You can also select an existing email template from the drop-down list.

5. Click Save to save the migration policy. After creating the migration policy, you can click Set as default to set the policy as the default policy for migrations.

On the Migration policies page, you can manage existing policies.

#Migration to Google Groups

For Microsoft 365 Groups to Google Groups migration, configure a To Google Groups migration policy by completing the following steps:

1. Click Policies under Settings in the left pane.

2. Click Migration policies to access the Migration policies page.

3. Click the Microsoft 365 Groups tab and click To Google Groups.

4. Click Create migration policy. The Create migration policy panel appears.

5. Enter a name and an optional description for the policy, and then click Next.

6. In the What do you want to migrate? Section, configure filters to define the objects you want to migrate:

   • Group – Select Membership if you want to migrate Group members. With the Membership option selected, you can continue selecting to migrate guest users.

     Guest users are added via the Microsoft 365 admin center, and can be added as group members.

     

   • SharePoint team site – Choose whether to migrate the following objects of source team sites.

     • All data in SharePoint team site – Select this checkbox to migrate all data of source team sites.

     • Only the default Documents library – Select this check to migrate only the default Documents libraries in team sites of Teams and private channels.

   • Group mailbox – Select the Mailbox checkbox to migrate the mailbox items of source Group mailboxes.

7. Migration policy for team site and group mailbox – Select a policy type according to your requirements.

   • Simple policy – This option allows you to customize how to migrate Group data. However, the migration scope of SharePoint and Exchange data cannot be customized.

     Note that SharePoint and Exchange data will be migrated based on the default settings that are pre-configured when you first create a corresponding policy without any changes. Refer to the following screenshots for details.

     

     SharePoint data that will be migrated.

     

     Exchange data that will be migrated.

   • Use custom SharePoint Online and ExchangeOnline migration policies – If you want to also customize how to migrate SharePoint and Exchange data, select this option to configure and use SharePoint Online and Exchange Online migration policies.

     With this option, you can ignore step 8 and the mail/file configurations in step 10, including Replace email addresses of senders/recipientsbased on user mappings, Replace meeting links with the destination information, and options of managing the sensitivity labels of files/emails during the migration.

     Note that if you have configured the filter policy in the SharePoint migration policy and will run the full migration job in Groups migrations with the SharePoint migration policy, do not change the filters in subsequent incremental jobs.

8. In the Conflict resolution section, configure the following conflict resolutions when the source object conflicts with an existing one in the destination**.**

   • SharePoint team site (includes: sites and lists/libraries) – Refer to the following detailed information on each conflict resolution for source team sites and the lists/libraries within.

Resolution	Conflict	No Conflict
Skip	Ignore the conflicting object and do nothing in the destination.	A new object will be created.
Merge	Merge the source and destination objects.	A new object will be created.

Resolution	Conflict	No Conflict
Skip	Ignore the conflicting file and do nothing in the destination.	A new file will be created.
Overwrite	Delete the conflicting file in the destination first and overwrite it with the source file.	A new file will be created.
Overwrite by last modified time	The conflicting file with the latest modified time will be preserved in the destination.	A new file will be created.

9. Click Next after you finish configuring the conflict resolutions.

10. In the Additional options & mappings step, configure the following settings for the migration.

    • Replace email addresses of senders/recipients based on user mappings – Select this checkbox if you want to replace the source email addresses of email senders/recipients with the destination ones. To make this setting available in the migration, you must configure user mappings for the source email addresses.

    • User mapping – With a user mapping, you can map a source user to a destination one. You can also map a domain in the source to a destination domain. Users, securities, and user-related metadata can be migrated based on user mappings. Click Add () button to the right of the field to create a new one. Refer to the Create User Mappings section to view how to create a user mapping.

      You can also select a previously created user mapping from the drop-down list and click View details to view the detailed information of the selected user mapping. You can enter the keyword of a user mapping in the Search user mapping text box and press Enter on the keyboard to search the user mapping.

      Note that for the users that have not been configured in user mappings, you can choose to map the users based on User principal name prefix, Display name, and/or Email address prefix. (Email address prefix is only supported for users of team sites.) Refer to the table below for property examples:

Property	User Principal Name	User Principal Name Prefix	Display Name	Email Address	Email Address Prefix
Property Example	JohnSimon@onmicrosoft.com	JohnSimon@	JohnSimon	JohnSimon@onmicrosoft.com	JohnSimon@

11. Click Next after you finish configuring the options and mappings.

12. Configure the Notifications setting to send migration email notifications to specific recipients after the migration.

    • Send project level notifications (all mappings within a project) – The migration email notifications are based on the project level, which summarizes the project name and the mapping count of each migration status.

      • Recurrence – Enter a positive integer to define the recurrence days for the notifications.

      • Start date and time – Select a start date and time to send the first notification. The later notifications will be sent at the selected time based on the recurrence.

        If you want to configure the end date and time of the notifications, you can select the Configure end date and time checkbox and select a date and time.

      • Send migration email notifications to – Define the recipients who will receive the notifications.

      • Email template – Create an email template for the notifications by clicking the Add () button. Refer to Manage Email Settings for details on how to create an email template. You can also select an existing email template from the drop-down list.

    • Send individual mapping level notifications – The migration email notifications are based on the mapping level, which summarizes the migration status, the project name, the source and destination email addresses, the migration start and finish time, and the migration person.

      • Define the notification scope for mappings – Select For failed mappings only to send notifications for the failed mappings only, or select For all mappings to send notifications for all mappings.

      • Send migration email notifications to – Define the recipients who will receive the notifications.

        • Person running the migration – The person who runs the migration will receive the notifications.

        • Additional recipients – Enter the email addresses of other recipients. Separate multiple email addresses with a semicolon (;).

      • Email template – Create an email template for the email notifications by clicking the Add () button. Refer to Manage Email Settings for details on how to create an email template. You can also select an existing email template from the drop-down list.

13. Click Save to save the migration policy. After creating the migration policy, you can click Set as default to set the policy as the default policy for migrations.

On the Migration policies page, you can manage existing policies.

#Create Sensitivity Label Mappings

Complete the following settings on the mapping page:

1. Enter a name and an optional description for the mapping.

2. Select the Auto map checkbox to automatically map the label based on the label name if the source label is not configured in label mappings.

3. In the Label mapping section, enter the display names of the source and destination sensitivity labels in the Source label and Destination label text boxes. If the source or destination sensitivity label is a sub label, enter the display name of the sensitivity label in the format of parent sensitivity label name/sensitivity label name.

   Click Add to add a new mapping.

   To delete sensitivity label mappings, select the corresponding checkboxes and click Delete.

4. Click Save to save the settings for this mapping.