AvePoint Docs
Graph API
My support tickets
Graph API
My support tickets
English

Home > Perform SharePoint Online Migrations > Create a Migration Policy

Export to PDF

Create a Migration Policy

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

Migration to SharePoint Online

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

  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 or deselect the Structure and/or Content checkbox to define in bulk the SharePoint objects you want to migrate.

    • Site – Select whether you want to migrate the listed objects and configurations.

    • List – Select whether you want to migrate lists/libraries, settings, public views, and Power Apps that are used to customize list forms.

    • *Note: To migrate Power Apps for lists, make sure you purchase sufficient subscriptions of Power Platform objects (Power Apps/Power Automate flows), and the app profile and service account used in the SharePoint Online connection have sufficient permissions.

    • Content – Select whether you want to migrate the listed content.

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

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

      When migrating to a site that is connected to the Microsoft 365 Group, you can select the Map the Owners, Members, and Visitors SharePoint groups to the destination Microsoft 365 Group checkbox to map the source owners to owners and members of the destination Microsoft 365 Group and map the source members and visitors to members of the destination Microsoft 365 Group. (The setting is available when the source site is not connected to the Microsoft 365 Group.)

      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.

      Guest users.

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

    • Workflows and user alerts – Select whether you want to migrate the workflow definitions and user alerts.

      *Note: By default, user alerts will be automatically disabled during the migration to avoid interruption. You can manually Enable User Alerts for the destination SharePoint Online after the migration.

    • Filter policy – A filter policy can help you set up filter rules 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 (Search button.) button to search the filter policy.

      You can also click the Add (Button: Add button.) 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 SharePoint 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.
ResolutionConflictNo Conflict
SkipIgnore the conflicting object and do nothing in the destination.A new object will be created.
MergeMerge the source and destination objects.A new object will be created.
The conflict resolution for folders is always **Merge** when the source folder conflicts with an existing folder in the destination. - **Content** – Refer to the following detailed information on each conflict resolution for library documents and list items.
ResolutionConflictNo Conflict
SkipIgnore the conflicting content and do nothing in the destination.A new content will be created.
OverwriteDelete the conflicting content in the destination first and overwrite it with the source content.A new content will be created.
Overwrite by last modified timeThe conflicting content with the latest modified time will be preserved in the destination.A new content will be created.

  1. Click Next to continue.

  2. In the Options section, define how to manage the sensitivity labels, IRM restrictions, and the default destination user of files/sites 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 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: Add button.) 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 sites during the migration, select an option below:

      *Note: If the source does not have the Microsoft Information Protection (MIP) service implemented or source sites 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 on site to destination – Select this option if there is no sensitivity label applied on source sites, or you do not want to keep the source sensitivity labels to the destination sites.

      • Apply same label in the destination (same 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 sites.

      • Apply labels in the destination based on label mappings (labels must exist in both source and destination) – Select this option 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: Add button.) button to Create Sensitivity Label Mappings to map the source and destination labels based on their display names.

        If the source sites 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.

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

  3. 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: Add button.) 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 (Search button.) 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.

PropertyUser Principal NameUser Principal Name PrefixDisplay NameEmail AddressEmail Address Prefix
Property ExampleJohnSimon@onmicrosoft.comJohnSimon@JohnSimonJohnSimon@onmicrosoft.comJohnSimon@
- Switch on/off the button of each property to configure whether you want to map users based on that property. - Click the Up or Down button of a property to configure the sequence for mapping users. > ***Note**: If you want to disable all properties, user mappings are required. For users that are not included in user mappings, Fly will map the users based on the UPN of source users. If you want to disable this feature, you can add the **EnsureUserWithLoginName=false** string in the **Customized** **features** section. Users that are not included in user mappings will not be mapped or migrated. - **Column mapping** – Column mapping allows you to map a source SharePoint Online column to a destination SharePoint Online column. The source column name will be replaced by the configured destination column name, and you can add value mappings to map the source values to destination values for the column you want to map. Click the Add (![Button: Add button.](/en/fly-user-guide/perform-sharepoint-online-migrations/images/image478.png "Button: Add button.")) button to create a new one. Refer to the [Create Column Mappings](#missing-link) section to view how to create a column mapping. You can also select a previously created column mapping from the drop-down list to use it (Clicking **View details** can view and edit the detailed information of the selected column mapping.). - **Content type mapping** – Content type mapping allows you to map a source SharePoint Online content type to a destination SharePoint Online content type. The source content type will be replaced by the configured destination content type. Click the Add (![Button: Add button.](/en/fly-user-guide/perform-sharepoint-online-migrations/images/image479.png "Button: Add button.")) button to create a new one. Refer to the [Create Content Type Mappings](#missing-link) section to view how to create a content type mapping. You can also select a previously created content type mapping from the drop-down list to use it (Clicking **View details** can view and edit the detailed information of the selected content type mapping.).

Template mapping – Template mappings allow you to map a source template to a destination template. The source template will be replaced by the configured destination template. You can create mappings at the site level and list level. Click the Add (Button: Add button.) button to create a new one. Refer to the Create Template Mappings section to view how to create a template mapping.

You can also select a previously created template mapping from the drop-down list to use it (Clicking **View details** can view and edit the detailed information of the selected template mapping.). - **URL** **mapping** – URL mappings allow you to map a source URL added to a source object to a destination URL. The source URL will be replaced by the configured destination URL. By default, Fly automatically replaces the source URLs with destination URLs when the objects that the source URLs redirect to are in the same site collection as the source objects. When the objects that the source URLs redirect to are in different site collections or external from the source tenant, you need to configure URL mappings for the URLs to make sure the URLs work in the destination. Click the Add (![Button: Add button.](/en/fly-user-guide/perform-sharepoint-online-migrations/images/image481.png "Button: Add button.")) button to create a new one. Refer to the [Create URL Mappings](#missing-link) section to view how to create a URL mapping. You can also select a previously created URL mapping from the drop-down list to use it (Clicking **View details** can view and edit the detailed information of the selected URL mapping.).

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

  2. Click Next to continue.

  3. 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: Add button.) 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: Add button.) 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.

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

- 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 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**. 2. You can also open your target policy, and click **Make a copy** on the **Edit migration policy** page. 3. Check the settings and make updates if necessary on the **Copy migration policy** page. 4. Click **Save**.

Migration to Google Drive

For SharePoint Online 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 SharePoint Online 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 the Only migrate objects in the top-level folder checkbox to only migrate the objects in the top-level folder. The subfolders and objects under them will not be migrated.

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

      • Select the Migrate source site/library/folder permission tothe Google Drive folder checkbox to migrate site/library/folder permissions. In the destination shared drive, the migrated site/library/folder will have both permissions migrated from the source and permissions inherited from destination parent. In the destination user drive, the migrated library/folder will have permissions migrated from the source.

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

      • Select the Migrate source file/item permissions checkbox to migrate file/item permissions. In the destination shared drive, the migrated file/item will have both permissions migrated from the source and permissions inherited from destination parent. In the destination user drive, the migrated file/item will have permissions migrated from the source.

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

      • You can select the Map the Owners, Members, and Visitors SharePoint groups to map migrate the users and groups in the default SharePoint groups to the destination based on the user mappings and permission mappings configured in your migration policy.

      • 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 lists, 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 lists, 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: Add button.) 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 List, 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.

ResolutionConflictNo Conflict
MergeMerge the source and destination folders.A new folder will be created.
SkipIgnore the conflicting folder and do nothing in the destination.A new folder will be created.
Refer to the following table to view the supported **File** level conflict resolutions.
ResolutionConflictNo Conflict
SkipIgnore the conflicting file and do nothing in the destination.A new file will be created.
OverwriteDelete the conflicting file in the destination first and overwrite it with the source file.A new file will be created.
Overwrite by last modified timeThe 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, files, and list items, and how to manage the sensitivity labels of files during the migration:

    • SharePoint Online metadata and items – Custom columns and column values of folders and files, as well as list items are not supported in the destination Google Drive. To migrate the metadata of folders and files, and list items, you can select the following checkboxes to migrate the data to Google sheets.

      • Migrate metadata of folders and files in libraries to Google sheets

      • Migrate metadata of folders and items in lists 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 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.

  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: Add button.) 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.

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

      Click the Add (Button: Add button.) 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: Add button.) 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: Add button.](/en/fly-user-guide/perform-sharepoint-online-migrations/images/image488.png "Button: Add button.")) button. Refer to [Manage Email Settings](#missing-link) for details on how to create an email template. You can also select an existing email template from the drop-down list.
  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.

- 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 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 Template Mappings

Configure the following settings on the mapping page:

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

  2. In the Template mapping section, set up template mappings on site or list level.

    • In the Site template mapping tab, enter the template ID in the Sourcetemplate and Destination template text boxes. You can also click the down arrow (Button: Down arrow button.) button and select the desired template name (The corresponding template ID will be displayed after the selection.).

      Click Addto add a new mapping.

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

    • In the List Template Mapping tab, enter the template ID in the Sourcetemplate and Destination template text boxes. You can also click the down arrow (Button: Down arrow button.) button and select the desired template name (The corresponding template ID will be displayed after the selection.).

      Click Addto add a new mapping.

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

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

Create Column Mappings

Complete the following settings on the mapping page:

Enter a name and an optional description for the mapping. Enter the display name of the source column in the **Source** **column name** text box, and enter the display name of the destination column in the **Destination** **column name** text box. > ***Note**: If you do not want to migrate a column, you can enter the column name as the source and leave the destination blank. The column will be skipped in the migration. To map source and destination column values, click **Add**, and enter column values in the **Source** **column value** and **Destination** **column value** text boxes. Click **Add** to add more value mappings. To delete column value mappings, select the corresponding checkboxes and click **Delete**. Select a type from the **Column** **mapping type** drop-down list. **Map to same type** – The source and destination column types can be the same/compatible. (Note: **Compatible** means that the source and destination column types are different, and Fly will update the destination column type to the source column type.) If the column types are the same/compatible with the source and destination, the source column will overwrite the destination column. If the column types are not the same/compatible with the source and destination, a new column will be created in the destination using the source column type. Refer to the following table for the compatible column types:
Source Column TypeDestination Column Type
Single line of textSingle line of text, Multiple lines of text, Choice, Choice (allow multiple selections), Currency, Number, Date and Time
ChoiceSingle line of text, Multiple lines of text, Choice, Choice (allow multiple selections), Currency, Number, Date and Time
NumberSingle line of text, Multiple lines of text, Choice, Choice (allow multiple selections), Currency, Number, Yes/No
CurrencySingle line of text, Multiple lines of text, Choice, Choice (allow multiple selections), Currency, Number, Yes/No
Yes/NoSingle line of text, Multiple lines of text, Choice, Choice (allow multiple selections), Currency, Number, Yes/No
Date and TimeSingle line of text, Multiple lines of text, Choice, Choice (allow multiple selections), Date and Time
Choice (allow multiple selections)Single line of text, Multiple lines of text, Choice, Choice (allow multiple selections), Currency, Number, Date and Time
Managed MetadataManaged Metadata, Managed Metadata (Allow multiple values)
Managed Metadata (Allow multiple values)Managed Metadata, Managed Metadata (Allow multiple values)
LookupLookup, Lookup (Allow multiple values)
Lookup (Allow multiple values)Lookup, Lookup (Allow multiple values)
Person or GroupPerson or Group, Person or Group (allow multiple selections)
Person or Group (allow multiple selections)Person or Group, Person or Group (allow multiple selections)
**Change to** **destination type** – The source column type can be different from the destination. If the column already exists in the destination, Fly will replace the source column with the destination column and keep the destination column settings. If the column does not exist in the destination, a new column will be created in the destination with the source column type kept. To separate character strings into different columns, select the **Migrate** **source** **string separated with _ into columns** checkbox. You can enter any character into the text box to separate the columns. > ***Note**: If the source Managed Metadata, Lookup, or Choice columns allow multiple values but the destination columns do not, only the first column value will be kept during the migration and mapped to the destination column value. Click **Add** **column** **mapping** and repeat steps **2** to **4** to configure additional mappings. To delete column mappings, select the Delete (![Button: Delete button.](/en/fly-user-guide/perform-sharepoint-online-migrations/images/image491.png "Button: Delete button.")) button next to the destination column name to delete the mapping. Click **Save** to save the settings for this mapping.

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 URL Mappings

URL mappings allow you to map a source URL added to a source object to a destination URL to make sure the URL works in the destination. Refer to the following table to view the supported and unsupported URLs of source objects.

URL TypeURL TypeSupported StatusComment
Column ValueHyperlink or PictureSupported
Column ValueMediaFieldTypeSupported
Column ValueNoteSupported
Column ValueHTMLSupported
Column ValueLinkSupported
Column ValueImageSupported
Column ValueSummary LinksSupported
File ContentURL inserted in Office fileUnsupported
File ContentURL inserted in other fileUnsupported
PageURL inserted in pageSupported
PageURL inserted in web partPartially supportedThe URL Mapping function is not supported for URLs inserted to Text web parts on modern pages.
NavigationHeadingSupported
NavigationLinkSupported
WorkflowURL in workflow actionSupported
Web PartLink inserted in web partSupported

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 URL in the Source URL and Destination URL textboxes and click Add to add a new mapping. The following formats are supported for source and destination URLs.

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

      The formats in the screenshot below are supported for source and destination URLs.

      URL mapping template.

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

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

Create Sensitivity Label Mappings

Configure 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 need your attention:

- If a user is assigned with multiple permission levels or if multiple users assigned with different permission levels are mapped to the same destination user, the destination use will be assigned with the highest permission in the source. - If the source contains custom permission levels and you do not configure permission mappings for these custom permission levels, the custom permission levels will be updated to Viewer in the destination. - 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.