Welcome to
Help Desk

Product Updates
Ideas Contact Support

Filtered and Unsupported Objects with Migration App


This product is currently in Limited Availability. We invite any Customers interested in using the product to engage Egnyte Professional Services or their Customer Success Manager to have it enabled for their domain.


Any user of Migration App. 


The following outlines various reasons why Migration App may be unable to migrate various files and recommended courses of action.


File Too Large

What's causing this?

The file you're uploading exceeds the maximum allowed size for any individual file in your domain. 

How to resolve it.

  • Reduce the size of your file.
  • Have your administrator contact Egnyte to increase the maximum supported file size by upgrading your Egnyte plan

Too many files in the folder

What's causing this?

The supported maximum number of files or folders in the same folder as this file or folder has been exceeded.

How to resolve it.

  • Break down your folder into several sub-folders to prevent storing more than 50,000 files and/or 50,000 folders directly under any single folder. 

Unsupported characters in Filename or Folder name or Path/Folder name too long

What's causing this?

This file or folder was not uploaded to Egnyte since it contains some unsupported characters in its name. It might also be due to a pathname being too long. Egnyte is limited to 245 bytes (or characters) per path component (e.g., a file or folder name) and 5000 bytes (or characters) for the entire path (including the filename). Microsoft Office imposes a 215 character limit on Office files.

How to resolve it.

  • Use the Sanitize command in Migration App to rename filenames on the Source.
  • Manually remove unsupported characters from the filename on the Source to continue uploading the file. The most common examples of files with unsupported characters include those that:
    • Contain one of the characters: \  /  "   :  < >  |  *  ?  +

    • End with a period(s).

    • Begin or end with spaces in their name.

    • Have control characters in their name.

  • For pathnames that are too long, consider reorganizing the content so that there are fewer embedded folders.
  • For file names that are too long, consider renaming the files.


File or Folder excluded from upload

What's causing this?

This file or folder type is excluded from migrating into Egnyte and is unsupported. The Egnyte cloud excludes the following file & folder types:

  • Temp files or Temp folders
  • System Folders
  • Package files
  • Resource files
  • Database files

    Note: While database files can be uploaded to Egnyte, it is not recommended to store or use active database files from the Egnyte cloud.

How to resolve it:

  • Move the file outside of Egnyte to a different location on your machine since it will never be uploaded.


  • Keep the file in place: It will continue to be accessible on the machine where the skip is encountered but will not be uploaded to the cloud.   

Malware detected

What's causing this?

This file was not uploaded to Egnyte as a safety precaution as it may contain malware. 

How to resolve it:

  • Immediately move the file outside of the drive or volume created by the Desktop App and use an anti-malware solution to scan the file. If the scan does not yield any problems, email Egnyte Support at support@egnyte.com with details of the file that triggered the message.


Filename or Folder name or path too long

What's causing this?

The full path to the file or folder you are attempting to upload is over the supported maximum of 5000 bytes. This is the length of the name of the file and folder itself, in addition to the length of the names of all the parent folders.  

How to resolve it:

  • Rename the file or folder, or any of the parent folders above it, so the length of the full path is less than the supported 5000 bytes.


  • Move the file or folder to a different parent folder, so the length of the full path is less than the supported 5000 bytes.

Files and Folders with Future Timestamp

What's causing this?

If the file and folder timestamps on the Windows Server have a timestamp that is far into the future (> 1 day) compared to the current time, migration of such folders and files will fail since Egnyte cloud does not accept files or folders with "Last Modified Time" in the future. 

How to resolve it:

  • For the impacted files and folders, fix the "Created" and "Last Modified Time" to reflect the current date. 

Questions? Feature Requests? Other Feedback?

If you have 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, you may submit them to support@egnyte.com. Be sure to include Migration App in the email title. Our Support team will push your comments to the Product team for consideration.




Was this article helpful?
1 out of 4 found this helpful

For technical assistance, please contact us.