Understanding Sanitization Options in Migration App

Audience

Any user of the Migration App.

Context

Sanitizing is the function of renaming files and folders to map to Egnyte naming conventions. After every scan of the source, the migration details page will provide details on any unsupported or conflicting file names. During sanitizing, all unsupported characters are replaced with an underscore, which will allow them to be migrated. Files that are not sanitized cannot be migrated to Egnyte.

Options Dialog Box

When the Migrate Data or True-Up Data option is selected, a modal with additional options will appear:

1. On Selecting Yes, sanitize on the source, any unsupported characters in filenames will be changed on the source to an underscore before migrating.
2. On Selecting Yes, sanitize on the fly, unsupported characters in filenames will be changed during migration and nothing will be changed on the source.
3. On Selecting No, do not sanitize, this metacommand will skip sanitizing altogether. Any unsupported files will not be migrated.

Note that regardless of whether sanitize is selected, if there are no unsupported characters in files on the source, the metacommand will skip the step altogether.

After making the selections in the modal, click Migrate Data or True-Up Data to proceed the migration job.

Sanitize Settings in Scheduler

1. Navigate to Advanced Options > Scheduler and select the toggle to On.
   
2. Select the desired sanitize option and click on Save.
   
   For other settings in the scheduler, refer to this article.  

Considerations

• If no sanitization is required on the source, the Migration App will automatically skip the step, irrespective of the selected option.
• If the original datasource is on Mac/Linux and uploaded using Windows CMM Agent, the special characters (\ , : , . , / , " , < , > , | , * , ?) will not be visible in Windows. This is a limitation in Windows OS and cannot be fixed. The end result is that the file will be visible and can be migrated, but on Egnyte it will appear with the unsupported character replaced with a random character.
• The Unicode character ('\u007F') cannot be recognized. As a result, a file with this character in the name will not be migrated and will not show up in the Migration Report because it is not recognized by Windows. Egnyte will continue to seek a root cause for this.
• If two files have identical names except the Unicode characters, then sanitizing will replace the Unicode with '_' which means both files will end up with the same name.
  • Example: on source 2 files with name:
    
    X3vKPFq␋avU2ygQT2h5UMpr
    X3vKPFq⇥avU2ygQT2h5UMpr
    
    Both then become:
    
    X3vKPFq_avU2ygQT2h5UMpr
    
    
  • If the user selects Sanitize on source, the second file will overwrite the first file, and only one file will be left to migrate.
  • However, if they choose Sanitize on-the-Fly, this results in one file with two versions of the file on the destination.

Unsupported Characters

By default, after sanitizing in Migration App, the following unsupported characters in filenames are replaced by an underscore ("_") on the Source:

Note: Space means an actual space (" ")

 

 

These limitations are not imposed by Migration App independently, but rather reflect Egnyte's overall character support and file type limitations. To find out more, see this Helpdesk Article: Unsupported Characters, and File Types.

Questions? Feature Requests? Other Feedback?

For any feature requests or suggestions, feel free to submit them on our Product Board, and be sure to mention Migration App in the text.

For more complex requests that would benefit from providing screenshots or other attachments, submit them to support@egnyte.com. Be sure to include Migration App in the email title. The Support team will push the comments to the Product team for consideration.