Any user of the 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. 


Planning a migration is a daunting task. In this article, we'll talk you through it, based on the best practices we've identified for the process. 

Before You Begin

  1. Run a speed test by going to https://<yourdomain> This checks for the available bandwidth from the on-premises server to the cloud. This doesn't guarantee throughput speeds, but it will at least give you a baseline. For more information on speed, see the Helpdesk article How Long Will it Take to Upload, Backup, or Download my Files?
  2. Ensure that Users and Groups are created in the Egnyte Cloud for your domain. For more information, please refer to the Helpdesk article for Importing Users and Groups.
  3. Login with an Admin account for the destination domain. 
  4. Review the Migration App Product Guide and the Migration App FAQs to gain a basic understanding of the tool.
  5. Communicate with your Users to help them understand the migration process. They can continue using the data on the Source for standard day-to-day file system activity. But it's critical that no large data sets be moved, renamed, or deleted during data migration. This type of activity can seriously endanger the success of your migration and the integrity of the final data set.

Taking a Phased Approach

We recommend that customers take a phased approach when planning their migrations using the Migration App. 

Phase 1:

Seed the data from the Source. This is the initial Data Migration to copy data to Egnyte and will take the most time. It will also give you visibility into whether you need to address any unsupported filenames or pathnames that are too long. Don’t worry about users making normal everyday changes to the source data; they can continue working with their content and you'll be able to true it up in a later phase. Be sure to communicate the concerns in point 5 above.

Important Notes about Case-Sensitivity:

  1. We recommend you instruct users not to change the case of file or folder names on the source once the migration has begun. The Egnyte platform is not case-sensitive, so it sees LEGAL and Legal as the same file name. But the utility at the heart of the Migration App is case-sensitive, so it sees LEGAL and Legal as two different file names. The result is the potential to completely lose your data during Phase 3 (True-Ups.)
  2. If you have enabled Canonical Support on your directories, we strongly recommend that you disable it. This is not compatible with the Egnyte CFS (Cloud File System.) 


Phase 2:

Sanitize the data (optional but recommended.) This changes the file names on the Source if they are incompatible with Egnyte’s naming conventions.

If you don’t want to change file names on the Source, do not run Sanitize. But be advised that if you don't run Sanitize, those offending files and folders will NOT be migrated and you will have to handle them manually.

It's important to be cognizant of how this may impact your users. We recommend you review the Helpdesk article Understanding the Sanitize Command in Migration App before proceeding.


Phase 3:

Run True-Ups. After a few days, rerun the same Migration job to True-Up or Sync your data. This simply entails returning to your Migration Dashboard, navigating to the Migration Job in question, and now selecting True-Up Data from the migration actions menu. This will take much less time than the first Data Migration, as it will mirror the Source and only migrate new or changed files (sometimes called the "deltas"). It will also give you an estimate for how much data changes at the Source over the course of a day or a week, and therefore how long to plan for the final True-Up and Cutover.

Important Note about Syncing Deletes:
Migration App
syncs deleted data by default. This means that if a file exists on Egnyte but no longer exists on the Source, running a True-Up will delete the file on Egnyte

During a True-Up, the following steps are performed:

  • Scan the Source
  • Scan the Destination
  • Compare the Source and Destination to prepare to mirror the two
  • Migrate the new data
  • Delete the files that are no longer on the Source.

You can run True-Ups as many times as you like before you finally Cutover.


Phase 4:

Migrate Permissions (this is optional.) Keep in mind that permissions migration with Migration App doesn't recognize permissions that were previously migrated. So it's a fresh migration, whether or not you've migrated permissions previously, and it commonly takes quite a while. That's why we recommend doing it as the final step in your migration project. You may want to review the Helpdesk article Permission Translation with Migration App before proceeding.


Phase 5:

Schedule Cutover. The final phase is the “Cutover." Most customers plan it over a weekend and ask users to stop using the Source data while they run the final Sync. This means running the same Migration Job True-Up one final time. Once it has been completed, you can have all users start using Egnyte and disable the Source.


Planning for the Cutover

Let's say you have 900GB of total data at your source. It's reasonable to assume only a small percentage will change over the course of a business day – for this example, we'll estimate it at 5% or 45GB. So if the initial Data Seeding (Phase 1) took 18 hours to migrate, you can assume that the True-Up would take about an hour. To test this, you go ahead and run a True-Up after a day, then again after a 3- or 5-day interval. This will start to give you a picture of how much time it will take to migrate the deltas when you plan your final Cutover. 

Before you schedule the Cutover, remember you need to communicate with all content users well in advance. In addition, for this migration to be successful, users must stop using the source data permanently and switch over to the Egnyte data only after you have completed the final True-Up and Permissions Migration.


Questions? Feature Requests? Other Feedback?

If you have feature suggestions or requests, feel free to submit them here, and make sure you mention Migration App in the text.

For more complex requests that would benefit from providing screenshots or other attachments, you may submit them to Be sure to include Migration App in the email title. Our Support team will push your comments to the Product team for consideration.