#Create a Migration Policy

A Google Drive migration policy allows you to configure the conflict resolution, filter policy, user mapping, permission mapping, illegal character mapping, and other options for Google Drive Migration.

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

1. Click Policies under Settings in the left pane.

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

3. Click the Google Drive 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:

   • 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 the Migrate source folder permissions checkbox to migrate folder permissions. If the source folder inherits permissions from its parent, the migrated folder in the destination will also inherit permissions from the parent. If the source folder has unique permissions, the source permissions will be migrated, and the migrated folder in the destination will not inherit permissions from its parent.

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

       • Select Enable the top-level folder to inherit permissions of the parent node indestination checkbox if you want the migrated top-level folder in the destination to inherit permissions from the parent.

         If you do not select this checkbox, the source permissions will be migrated, and the migrated top-level folder in the destination will not 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 also inherit permissions from the parent. If the source file has unique permissions, the source permissions will be migrated, and the migrated file in the destination will not inherit permissions from its parent.

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

   • 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 File level. Refer to Google Drive Filter Policies for examples of filter policies that users can configure.

     • Migrate versions – Select the checkbox to migrate file versions in the migration.

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

       • Latest versions – Select this option to migrate latest versions and enter a number 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 Options section, configure the following settings:

   • Migrate real file name as destination file name – Google has both a file name and a version name for files. Select this option to use the source file name as the destination file name. If you do not select this option, Fly will migrate the current version name of the source file as the file name.

   • Move up folders and files – Select this option to move up a folder/file if its URL length in the destination exceeds the limit allowed by SharePoint Online or configured in the Maximum length of the SharePoint URL option. If you do not select the option and a folder/file’s URL length exceeds the limit, the folder/file will not be migrated.

     **Shared with you** – If you have selected to migrate folder/file permissions, you can select this option to display folders or files in users’ **Shared with** **you** list in their OneDrive. **Character Limits** – Select this option to configure character length limits for the SharePoint URL, file name, and folder name of migrated files and folders in the destination.

     • Maximum length of the folder name – Select the option, and enter an integer between 1 and 400 in the text box. If the folder name exceeds the limit you set, the extra characters will be pruned from the end of the folder name. If folders, after being pruned, share the same name, only one folder will be migrated to the destination. Files in these source folders will all be migrated to this pruned folder. If some of these files share the same name, the files will be migrated by adding a suffix (_1, _2, …, increasing in numerical value).

     • Maximum length of the file name – Select the option, and enter an integer between 1 and 400 in the text box. If the file name exceeds the limit you set, the extra characters will be pruned from the end of the file name. If files, after being pruned, share the same name, the files will be migrated by adding a suffix (_1, _2, …, increasing in numerical value).

     • Maximum length of the SharePoint URL – Select the option, and enter an integer between 1 and 400 in the text box. The length of the SharePoint URL is calculated from the first character of the managed path.

       *Note: If you do not configure the character limits, the maximum length of the SharePoint URL in the destination will be 400.

       If you have selected the Move up folders and files option, when the folder or file’s URL exceeds the limit, the folder or file will move to upper-level folders until the URL character length does not exceed the limit.

   • Use this user to replace the metadata of users that do not exist in the destination – Select this option to define a default user to replace the metadata of users that do not exist in the destination, and enter the email address of the default user in the text box.

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 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: To migrate Google groups to SharePoint groups, you can only map the groups with user mappings. For the migration of other users/groups, you can also choose to map the users/groups 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

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

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 Permission Mapping

Complete the following settings on the mapping page:

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

2. In the Permission mapping section, choose the default SharePoint/OneDrive permission levels or previously created SharePoint/OneDrive permission levels for each source permission.

   If the existing SharePoint/OneDrive permission levels cannot satisfy your requirements, you can create a new permission level by completing the following steps:

   1. Click Create SharePoint/OneDrive permission level.

   2. On the Create SharePoint/OneDrive permission level page, enter a name and an optional description for the permission level.

   3. Select the List permissions, Site permissions, and/or Personal permissions checkboxes, and select your target specific permissions under that permission.

   4. Click Save to save the permission level.

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

#Create Illegal Character Mapping

Complete the following settings on the mapping page:

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

2. To modify an illegal character mapping character, click the text box in the Replace with column and enter a new valid character or character string.

3. To add an illegal character mapping, click Add, and enter a character or character string in the Illegal characters and Replace with text boxes.

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

*Note: ㉑ to ㊿ characters are regarded as the same character in SharePoint Online. Therefore, we recommend you configure illegal character mappings if the file names contain these characters.

For the illegal characters/character strings that have not been configured in mappings, refer to the table below to view how Fly will replace the illegal characters.

*Note: If the source file only has an extension without the name, the file name will be migrated as (Blank). For example, .docx will be migrated as (Blank).docx.

Illegal Character/Character String	Replace with	Note
\t (Horizontal Tab)	Half-width Space	If the illegal character string is the first character, the half-width space will be deleted.
\v (Vertical Tab)	Half-width Space	If the illegal character string is the first character, the half-width space will be deleted.
\n (LF)	Half-width Space	If the illegal character string is the first character, the half-width space will be deleted.
\r (CR)	Half-width Space	If the illegal character string is the first character, the half-width space will be deleted.
\0 (Null Character)	Half-width Space	If the illegal character string is the first character, the half-width space will be deleted.
\a (Bell Character)	Half-width Space	If the illegal character string is the first character, the half-width space will be deleted.
\b (Backspace Character)	Half-width Space	If the illegal character string is the first character, the half-width space will be deleted.
\f (Form-feed)	Half-width Space	If the illegal character string is the first character, the half-width space will be deleted.
ASCII Dec Num in ([0,31], [127,159], [55296,57343], [65533,65535])	Half-width Space	If the illegal character string is the first character, the half-width space will be deleted.
"	_
*	_
:	_
<	_
>	_
?	_
/	_
**	_
**	**	_
vti	_
.LOCK	.LOCK_
CON	CON_
PRN	PRN_
AUX	AUX_
NUL	NUL_
COM0	COM0_
COM1	COM1_
COM2	COM2_
COM3	COM3_
COM4	COM4_
COM5	COM5_
COM6	COM6_
COM7	COM7_
COM8	COM8_
COM9	COM9_
DESKTOP.INI	DESKTOP.INI_
LPT0	LPT0_
LPT1	LPT1_
LPT2	LPT2_
LPT3	LPT3_
LPT4	LPT4_
LPT5	LPT5_
LPT6	LPT6_
LPT7	LPT7_
LPT8	LPT8_
LPT9	LPT9_
AUX.	_AUX. or AUX._	If the illegal character string is at the beginning, Fly will add an underscore as the prefix. If the illegal character string is at the end, Fly will add an underscore as the suffix.
COM0.	_COM0. or COM0._	If the illegal character string is at the beginning, Fly will add an underscore as the prefix. If the illegal character string is at the end, Fly will add an underscore as the suffix.
COM1.	_COM1. or COM1._	If the illegal character string is at the beginning, Fly will add an underscore as the prefix. If the illegal character string is at the end, Fly will add an underscore as the suffix.
COM2.	_COM2. or COM2._	If the illegal character string is at the beginning, Fly will add an underscore as the prefix. If the illegal character string is at the end, Fly will add an underscore as the suffix.
COM3.	_COM3. or COM3._	If the illegal character string is at the beginning, Fly will add an underscore as the prefix. If the illegal character string is at the end, Fly will add an underscore as the suffix.
COM4.	_COM4. or COM4._	If the illegal character string is at the beginning, Fly will add an underscore as the prefix. If the illegal character string is at the end, Fly will add an underscore as the suffix.
COM5.	_COM5. or COM5._	If the illegal character string is at the beginning, Fly will add an underscore as the prefix. If the illegal character string is at the end, Fly will add an underscore as the suffix.
COM6.	_COM6. or COM6._	If the illegal character string is at the beginning, Fly will add an underscore as the prefix. If the illegal character string is at the end, Fly will add an underscore as the suffix.
COM7.	_COM7. or COM7._	If the illegal character string is at the beginning, Fly will add an underscore as the prefix. If the illegal character string is at the end, Fly will add an underscore as the suffix.
COM8.	_COM8. or COM8._	If the illegal character string is at the beginning, Fly will add an underscore as the prefix. If the illegal character string is at the end, Fly will add an underscore as the suffix.
COM9.	_COM9. or COM9._	If the illegal character string is at the beginning, Fly will add an underscore as the prefix. If the illegal character string is at the end, Fly will add an underscore as the suffix.
CON.	_CON. or CON._
DESKTOP.INI.	_DESKTOP.INI. or DESKTOP.INI._
.LOCK.	_.LOCK. or .LOCK._
LPT0.	_LPT0. or LPT0._
LPT1.	_LPT1. or LPT1._
LPT2.	_LPT2. or LPT2._
LPT3.	_LPT3. or LPT3._
LPT4.	_LPT4. or LPT4._
LPT5.	_LPT5. or LPT5._
LPT6.	_LPT6. or LPT6._
LPT7.	_LPT7. or LPT7._
LPT8.	_LPT8. or LPT8._
LPT9.	_LPT9. or LPT9._
NUL.	_NUL. or NUL._
PRN.	_PRN. or PRN._

*Note: If there are files sharing the same file name after the illegal character replacement, Fly will add a suffix (_1, _2, …, increasing in numerical value) before the extension of the file names.

*Note: For folders, space at the beginning or end of the folder name will be trimmed. If there are folders sharing the same folder name after the illegal character replacement, Fly will process the folders based on the Folder level conflict resolution. In either case (Skip or Merge), the subfolders and files under that skipped or merged folder will be migrated to the destination folder with the same name.