Using Migration App to Sync Data to Existing Folders in Egnyte

Audience

Any user of the Migration App.

Can I use the Migration App to migrate additional content into folders on my Egnyte domain that already contains data?

Yes, you can. In fact, that's an excellent use case for the Migration App. To do this without duplicating any data, you need to schedule individual migration jobs for each existing top-level folder on your Egnyte domain. This enables the Migration App to identify the deltas in each folder.

For example, the image above shows a list of folders on a customer domain in Egnyte. To use the Migration App to sync up content with your on-premises source files, you need to create a migration job for each of the relevant folders.

So, in this case, you’d create your first migration job for the source of E:\Alexander and map that to the destination of /Shared/Alexander. This will then migrate only the changes from E:\Alexander to the destination. Then you can create migration jobs for the folders CFLADMIN, Data, Dejong and so on.

Two Key Concepts

1. It is important to be aware that Migration App syncs deletes by default. This means that if a file exists on Egnyte but no longer exists on the Source, running Migrate Data will delete the file on the destination.
   
   
2. You might think you could just run a single migration job for the Shared folder, but that won't work. You will need to create a separate migration job for each top-level folder within Shared.

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