#Create a Migration Policy

A Gmail migration policy allows you to define the migration scope of objects, conflict resolution, user mapping, and how to map users/groups, and advanced options for Gmail Migration.

Refer to the following steps to configure a migration policy for Gmail Migration:

1. Click Policies under Settings in the left pane.

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

3. Click the Gmail 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.

   • Select how to migrate Gmail labels – Select an option to migrate Gmail labels.

     • Migrate labels as folders – Source mails with multiple labels will be migrated to different folders based on the labels, which would result in duplicate mails in the destination. This option will keep the source folder structure.

     • Migrate labels as categories – Source mails with multiple labels will be migrated to the destination built-in folder, which has the same name as the source folder in the corresponding language.

       Note the following:

       • If you select this option, you cannot define the folders to include or exclude, and the Synchronize deletion feature is not supported.

       • If you want to migrate any label changes in incremental migration jobs, make sure you have enabled the IsCheckLabelChange customized feature. For details, refer to Customized Features for Gmail Migration.

   • Folders – You can define the mail 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 (;).

     • Exclude – Enter the folder names you want to filter out in the migration in the text box. Separate multiple folder names with a semicolon (;).

   • Mail time range – You can select the On or after and/or On or before checkboxes and select a sent time to only migrate mails in the specified time range.

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

1. Click Next to continue.

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

   • Synchronize deletion – With this checkbox selected, if source mails/events/tasks/contacts/custom contact labels are deleted after a migration, destination migrated data can also be deleted in subsequent incremental migrations.

   • Replace email addresses of senders/recipients based on user mappings – Select this checkbox if you want to replace the source email addresses of mail 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 mails received before the specific date to the archive mailbox – Select this checkbox and a sent date to migrate any source mails before that date to the destination archive mailbox. Make sure Archiving is enabled for the destination mailbox in the Exchange Admin center.

     *Note: This setting is unavailable for destination Microsoft 365 Group mailboxes.

   • Migrate source data to a specified destination folder – Select this checkbox and enter a folder name to migrate all data in folders of email type in the source mailbox to the specified destination folder, including the archive folder, subfolders, deleted data, etc.

3. In the Mappings section, configure the user mappings for the migration. With a 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 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 to use it (Clicking View details can view and edit 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.

4. In the Customized features section, you can add customized features by entering the corresponding customized feature strings. Click Add customized feature, and then enter a customized feature string to configure a customized feature. Refer to Customized Features for Gmail Migration for details.

5. Click Next to continue.

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

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

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