#Create a Migration Policy

A OneDrive migration policy allows you to define the migration scope of objects and permissions, configure the filter policy, conflict resolution, user mapping, and other settings for OneDrive Migration.

#Migration to OneDrive

For OneDrive to OneDrive Migration, configure a To OneDrive 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 OneDrive tab and click To OneDrive.

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:

   • Scope – Select to only migrate the Documents library of the OneDrive site or migrate all containers and content.

   • Team – Select whether you want to migrate the meeting recording and meeting transcript files stored in the OneDrive site.

   • Permissions – Select whether you want to migrate the direct permissions and shared links in the OneDrive site. With Shared links selected, after the migration, new shared links will be created in the destination. If the links are shared with anyone or external users, the destination OneDrive owners will receive email notifications after the migration.

     If you select to migrate the permissions of data shared with you in OneDrive, the migration performance will be affected.

     Guest users are added via the Microsoft 365 admin center, and can be added as SharePoint administrators, permission users and users related to shared links.

     

     External users can be added as permission users and users related to shared links if the two related tenants have enabled cross-tenant access for each other. You can enable the cross-tenant access by completing the following steps:

     1. Log into the Microsoft Entra ID admin center.

     2. Click External Identities.

     3. Click Cross-tenant access settings.

     4. Click Add organization under the Organization settings tab.

     5. In the Add organization panel, enter the tenant ID or domain name of the tenant for which you want to allow the member, and click Add.

        Then after about 24 hours, you can manually add the member to the target shared channel.

   • Filter policy – A filter policy can help you set up filter rules for the list, folder, item, and document level to define what objects can be included in your migrations. Select the checkbox and select a filter policy to include/exclude the defined objects for the migration. You can enter the keyword of a filter policy in the Search filter policy text box and click the Search () button to search the filter policy.

     You can also click the Add () button to create a new filter policy, enter a name and an optional description for the filter policy, and define the filter rules for each object level. Refer to SharePoint/OneDrive Filter Policies for examples of filter policies that users can configure.

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

   • Container (includes: sites and lists/libraries) – Refer to the following detailed information on each conflict resolution for sites and lists/libraries.

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 content and do nothing in the destination.	A new content will be created.
Overwrite	Delete the conflicting content in the destination first and overwrite it with the source content.	A new content will be created.
Overwrite by last modified time	The conflicting content with the latest modified time will be preserved in the destination.	A new content will be created.

8. Click Next to continue.

9. In the Options section, define how to manage the sensitivity labels, IRM restrictions, and default destination user of files during the migration:

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

     *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 migrate files 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.).

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

   • Define a default destination user – Select the Use this user to replace the metadata of users that do not exist in the destination checkbox to replace the metadata of users that do not exist in the destination with a specified user during the migration. If you deselect this checkbox, the metadata of source users will be kept.

10. In the Mappings section, configure the following mappings for the migration:

    • User mapping – 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. Users, securities, and user-related metadata can be migrated based on user mappings. 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 click the Search () button to search the user mapping.

      *Note: For the users/groups that have not been configured in user mappings, you can choose to map the users/groups based on User principal name prefix, Display name, and/or Email address prefix.

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. 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 SharePoint Online/OneDrive Migration for details.

12. Click Next to continue.

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

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

For OneDrive to Google Drive Migration, configure a To Google Drive 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 OneDrive tab and click To Google Drive.

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:

   • Scope – Select whether you want to migrate the meeting recording and meeting transcript files stored in the OneDrive site.

   • Permissions – Select whether you want to migrate permissions at each level.

     • Select the Migrate source folder permission toGoogle Drive folder checkbox to migrate folder permissions.

       • If the source folder inherits permissions from its parent, the migrated folder in the destination will have the same permissions as the source folder.

       • If the source folder has unique permissions, the source permissions will be migrated. In the destination shared drive, the migrated folder will have both permissions migrated from the source and permissions inherited from destination parent. In the destination user drive, the migrated folder will have permissions migrated from the source.

       If you do not select this checkbox, the migrated folder in the destination will inherit permissions from its parent.

     • Select the Migrate source file permissions checkbox to migrate file permissions.

       • If the source file inherits permissions from its parent, the migrated file in the destination will have the same permissions as the source file.

       • If the source file has unique permissions, the source permissions will be migrated. In the destination shared drive, the migrated file will have both permissions migrated from the source and permissions inherited from destination parent. In the destination user drive, the migrated file will have permissions migrated from the source.

       If you do not select this checkbox, the migrated file in the destination will inherit permissions from its parent.

     • Select the Migrate source shared link permissions checkbox to migrate the permissions of source shared links to the destination. If you do not migrate shared link permissions, destination migrated shared links will be unavailable. With this checkbox enabled, you can also select if you want to migrate the expiration dates of the permissions.

     • Select the Migrate external user permissions checkbox to migrate external users to the destination. If no user mapping is configured or the mapped user for an external user cannot be found at the destination, Fly will automatically create the external user in Google and restore their permissions.

   • Filter policy – A filter policy can help you set up filter rules so you can control what folders and files can be included in your migrations.

     • Configure a filter policy to include/exclude objects – Select the checkbox to configure a filter policy for folders and files.

       You can enter the keyword of a filter policy in the Search filter policy text box and press Enter on the keyboard button to search the filter policy. You can also click the Add () button to create a new filter policy, enter a name and an optional description for the filter policy, and define the filter rules for the Folder or Document level. Refer to SharePoint/OneDrive Filter Policies for examples of filter policies that users can configure.

     • Migrate versions (only support the latest 100 versions) – Select the checkbox to migrate file versions in the migration.

       *Note: The destination Google Drive supports a maximum of 100 versions.

       • All versions – Select this option to migrate all versions.

       • Latest versions – Select this option to migrate latest versions and enter a number between 1 and 100 to define the number of versions you want to migrate.

7. In the Conflict resolution section, specify the conflict resolution when the source folder or file conflicts with an existing one in the destination.

   Refer to the following table to view the supported Folder level conflict resolutions.

Resolution	Conflict	No Conflict
Merge	Merge the source and destination folders.	A new folder will be created.
Skip	Ignore the conflicting folder and do nothing in the destination.	A new folder 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.

1. Click Next to continue.

2. In the Migration to shared drives section, you can select the Automatically create shared drives when the destination drives cannot be found checkbox. With this option selected, Fly will automatically create shared drives when no shared drive or user drive with the name configured in the migration mapping can be found in the destination. If this option is not selected, the migration job will fail when the shared drive or user drive cannot be found.

3. In the Options section, define whether to migrate metadata of folders and files, and how to manage the sensitivity labels of files during the migration:

   • OneDrive metadata and items – Custom columns and column values of folders and files are not supported in the destination Google Drive. To migrate the metadata, you can select the Migrate metadata of folders and files in libraries to Google sheets checkbox to migrate the data to Google sheets.

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

     *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 in source, or migrate files 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.

4. In the Mappings section, configure the following mappings for the migration:

   • User mapping – 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. Users, securities, and user-related metadata can be migrated via user mapping. For a group mapping, only source group permissions will be migrated; the group membership will not be migrated.

     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.

     *Note: For the users/groups that have not been configured in user mappings, you can choose to map the users/groups based on User principal name prefix and/or Display name.

     • Switch on/off the button of each property to configure whether you want to map users/groups based on that property.

     • Click the Up or Down button of a property to configure the sequence for mapping users/groups.

     *Note: If you want to disable all properties, user mappings are required. For users/groups that are not included in user mappings, Fly will map the users/groups based on the login name of source users/groups. If you want to disable this feature, you can add the EnsureUserWithLoginName=false string in the Customized features section. Users/groups that are not included in user mappings will not be mapped or migrated.

   • Permission mapping – With a permission mapping, you can map source OneDrive permission to a destination Google Drive permission.

     Click the Add () button to create a new one. Refer to the Create Permission Mappings section to view how to create a permission mapping. You can also select a previously created permission mapping from the drop-down list to use it (Clicking View details can view and edit the detailed information of the selected permission mapping.). You can enter the keyword of a permission mapping in the Search permission mapping text box and press Enter on the keyboard to search the permission mapping.

5. 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 SharePoint Online/OneDrive Migration for details.

6. Click Next to continue.

7. 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 (;).

1. 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 Content Type Mappings

Configure the following settings on the mapping page:

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

2. In the Content type mapping section, enter content type names in the Source content type and Destination content type text boxes.

   Click Add to add a new mapping.

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

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

#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 Permission Mappings

Complete the following settings on the mapping page:

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

2. In the Permission mapping for user drive and Permission mapping for shared drive sections, choose a Google Drive permission for each source permission.

   If the existing SharePoint/OneDrive permissions cannot satisfy your requirements, you can create a new permission by clicking Add, entering the permission name, and choosing a Google Drive permission level for it.

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

   • There are some notes that need your attention:

   • If multiple users assigned with different permission levels are mapped to the same destination user, the destination user will be assigned with the highest permission in the source.

   • If the destination is a shared drive, and you map a permission to Edit/Manager, note the following:

     • The permission of a migrated root shared folder in the destination will be updated to Manager.

     • The permission of a subfolder migrated to a destination shared folder will be updated to Content manager.

   • If the destination is a user drive/shared drive, the owner of the user drive/shared drive will be set as the owner of all migrated items by default.