#Customized Features for Google Drive Migration

Fly provides a customized feature for Google Drive Migration. Refer to the following information to use the feature:

• EnsureUserWithLoginName – Define whether to use the login name to map users/groups that are not included in user mappings when all user property options are disabled in the migration policy. By default, Fly will use the login name to map these users/groups to ensure they can be successfully migrated.

  If you do not want to use the login name to map these users/groups, you can add the EnsureUserWithLoginName=false string to disable the feature.

• IsCheckPermissionChange – This defines whether to keep the destination folder permissions the same as the source after the incremental migration jobs with the Merge folder level conflict resolution.

  By default, Fly will merge source permission changes and destination existing permissions for folders in the incremental migration job. If you want the destination folders to have the same permissions as the source, you can add the IsCheckPermissionChange=true string. Fly will overwrite the destination permissions with latest source permissions.

  To merge source and destination permissions, you can change the string value to false or remove the feature string to disable this feature.