#Create a Migration Policy

An Exchange Online Public Folder migration policy allows you to define the migration scope of objects, conflict resolution, user mapping, and advanced options for Exchange Online Public Folder Migration.

Refer to the following steps to configure a migration policy for Exchange Online Public Folder Migration:

1. Click Policies under Settings in the left pane.

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

3. Click the Exchange Online Public Folder 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:

   • Objects – Select the source objects you want to migrate.

   • Folders – You can define the folders you want to include or exclude in the migrations.

     • All – All source folders will be migrated.

     • Include – Enter the folder names you want to migrate in the text box. Separate multiple folder names with a semicolon (;). You can select to migrate only the specified folders or include all their subfolders as well.

     • Exclude – Enter the folder names you want to filter out in the migration in the text box. Separate multiple folder names with a semicolon (;). These folders, along with their subfolders and all contained items, will not be migrated.

   • Email time range – You can select the On or after and/or On or before checkboxes and select a sent time to only migrate items of email type in the specified time range. The item type depends on the folder where the item is stored.

7. In the Conflict resolution section, configure the conflict resolution when the source item conflicts with an existing one in the destination. Refer to the following detailed information on each conflict resolution.

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

2. In the Additional options & mappings step, you can configure the following settings for migrations.

   • Synchronize deletion – With this checkbox selected, if source emails/tasks/contacts/contacts lists/journals/notes are deleted after a migration, destination migrated data can also be deleted in subsequent incremental migrations.

   • *Note: Deletion synchronization for calendar items including recurring occurrences and birthday items is always enforced, regardless of whether this checkbox is selected.

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

   • Migrate emails before the specific date to the archive mailbox – Select this checkbox and a sent date to migrate any source emails before that date to the destination archive mailbox. Make sure Archiving is enabled for the destination mailbox in the Exchange Admin center.

   • 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 will not direct users 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 Support Lists for Exchange Online Public Folder Migration for details.

   • Select how to manage sensitivity labels of emails – Select a method to define how to manage sensitivity labels applied on emails in the migration:

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

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

       After the migration, the migrated emails may not be accessed in the destination.

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

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

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

   • User mapping – With user mapping, you can map a source user/group to a destination one. You can also map a domain in the source to a destination domain. Click the Add button to the right of the field to create a new one. Refer to Create User Mappings 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.

3. Click Next after you finish configuring the options, mappings, and customized feature strings.

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.

       • Destination end users – The destination end users in the migration 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.

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