#Create a Migration Policy

A Microsoft Teams Chat migration policy allows you to define the migration scope of Teams chats, whether to migrate chat file attachments, the conflict resolution for chat file attachments, how to map chat users, and how to manage the sensitivity labels of chat file attachments for Microsoft Teams Chat migrations.

Refer to the following steps to configure a migration policy for Microsoft Teams Chat migrations:

1. Click Policies under Settings in the left pane.

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

3. Click the Microsoft Teams Chat tab.

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:

   • Chat scope – Define the scope of chats to be migrated.

     • Recreate chat messages in Teams – Select this option if you want to recreate the chat messages in the destination, and select an option below to define the migration scope of chat messages.

       The screenshots below show the chat messages in the source and destination.

       

       Source 1:1 chat.

       

       Destination 1:1 chat.

       

       Source IT group chat.

       

       Destination IT group chat.

       

       Source group chat without name.

       

       Destination group chat without name,

       • Migrate all chats – Migrate all chats for chat users.

       • Migrate chat on or after – By default, Fly will only migrate the chats modified within the last two months before the current date. If the default date cannot satisfy your requirements, you can specify a different date to migrate the chats after your specified date.

         *Note: After a migration job, if you extend the date filter to an earlier date, the extension will not work in the next migration job. Fly will migrate chats according to the previous date filter to secure a correct message order.

     • Archive all chat messages to HTML files to each mapped user’s OneDrive – Select this option if you want to archive chat messages as HTML files for chat users that are configured in the migration mappings.

       The screenshots below show the chat messages in the source and destination.

       

       Source 1:1 chat.

       

       Destination 1:1 chat.

       

       Source named group chat.

       

       Destination named group chat.

       

       Source unnamed group chat.

7. In the Conflict resolution section, configure the following conflict resolutions when the source chat file attachment conflicts with an existing one in the destination**.**

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.

8. Click Next after you finish configuring the conflict resolution.

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

   • Select how to manage sensitivity labels of chat file attachments – Define how to manage the sensitivity labels of chat files by selecting an option below.

     *Note: This setting is available only when you select the Migrate chat file attachments for users in the migration option in the What do you want to migrate? Section.

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

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

       After the migration, the migrated files 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 in the destination) – Select this option if you want to remove the source sensitivity labels from the files.

       After the migration, the migrated files 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 during the migration, and applies existing destination sensitivity labels with the same display name to the migrated files in the destination. The source sensitivity labels applied to source files 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 with existing destination sensitivity labels.

       According to the label mappings, Fly will remove the source sensitivity labels from the migrated files during the migration, and apply the destination sensitivity labels to the migrated files in the destination. The source sensitivity labels applied to source files 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.).

   • Stop the migration and report errors if chat user does not have OneDrive – If your source or destination chat users do not have a OneDrive site, you can select the option to stop the migration job and report errors.

     If you want to skip the verification, deselect the option. The migration job will continue, but OneDrive related data or functions will fail, such as migrating chat files and replacing chat file links.

   • Provide the final domain name of the destination tenant to replace file links in chat messages – If you have changed domains for chat users, select this checkbox to replace file links in chat messages. Otherwise, the file links in the destination chat messages may not be opened.

     Choose an option according to your requirements.

     • Enter the final destination domain name – Select this option if the destination tenant has only one domain, and enter the new destination domain in the text box. This option will apply to all chat users in the migration.

       *Note: The final domain refers to the domain used by your destination tenant that has gone live. For example, contosoA.com is used during the migration, and contosoB.onmicrosoft.com is used after the destination tenant goes live, you need to enter contosoB.onmicrosoft.com here.

     • Select a URL mapping if the destination has multiple domains – Select this option if the destination tenant has multiple domains. Then select a URL mapping with chat users’ source and destination OneDrive URLs configured. This option only applies to the chat users that are included in the URL mappings. To create a URL mapping, refer to Create URL Mappings.

   • 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: For the users that have not been configured in user mappings, you can choose to map the users based on User principal name prefix and/or Display name. Refer to the table below for property examples:

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

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

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

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

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

    • Set as default – Select a policy and click Set as default to set it as the default policy. The default policy will be automatically selected when you create projects.

    • Edit – Click the policy name link to edit the policy.

    • Delete – Select a policy and click Delete to delete it. You can also select one or multiple policies and click Delete to delete them.

    • Copy – This allows you to quickly create a new policy with similar configurations by completing the following steps:

      1. Select your target policy, and click Make a copy.

         You can also open your target policy, and click Make a copy on the Edit migration policy page.

      2. Check the settings and make updates if necessary on the Copy migration policy page.

      3. Click Save.

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

#Create URL Mappings

Configure the following settings on the mapping page:

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

2. In the URL Mappings section, you can add the URL mapping one by one or import multiple mappings in bulk.

   • Add URL mapping – Enter the full URLs of source and destination OneDrive sites in the Source URL and Destination URL textboxes.

   • Import URL mappings – Click Import. In the Import panel, you can download the template for mapping examples and configure mappings directly in the file. You can click Export in this section to export a mapping file and modify it. After the configurations, in the Import panel, import the mapping file by dragging the file or browsing the file from the local location. Click Save to save the mappings.

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

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