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, their Partner Account Manager or their Customer Success Manager to have it enabled for their domain.


Getting Started

The Agent

The Migrations Dashboard

Creating a Migration Job

What Gets Migrated

True-Ups or Syncing



Speed, Bandwidth, and Throughput

Advanced Mode


General Questions



Getting Started


Q: What does it mean that Migration App is in Limited Availability?

A: While it has already proven effective at migrating multiple PB (Yes! Petabytes!) of data for hundreds of customers, Migration App is not yet Generally Available (GA). The Limited Availability Program allows us to enable Migration App for a subset of Egnyte Professional Services customers and other more technical customers who wish to use the product while we address scalability of the product. 


Q: What version is the Migration App Agent currently?

A: The Migration App Agent is presently on version 3.10. The Agent autonomously updates whenever a new version is available. It will wait to update until after your Agent has finished running any active Migration Jobs.

If you need to manually update your Agent, please ensure no Migration Jobs are actively running. After the Agent updates, you will be able to keep running your existing Migration Jobs as before.


Q: What types of domains can be enabled with Migration App?

A: There are various types of Egnyte domains, but Migration App cannot be enabled for all types.

  • Trial domains: In general, Migration App cannot be enabled Trial Domains. Trial domains are ineligible due to the storage limitations imposed by the trial program. One exception may be for Enterprise Trials, which eliminate the storage limitations.
  • Archive domains: Yes.
  • Vanity domains: No. An example of a vanity domain is which is essentially an alias from your standard Egnyte domain To use Migration App, you must have it enabled on your standard domain and run all your migrations there.
  • domains: Yes. Also known as FedRamp domains. Note that Egnyte is currently designated "FedRamp-Ready" and has not yet been fully FedRamp certified.

Q: How do I get to the Migration App once it has been enabled for my domain?

A: You can find Migration under the hamburger menu on your domain interface.


Q: Once enabled, does Migration remain enabled for a domain indefinitely?

A: Currently, access to the Migration App is controlled via a flag on the back end of the Egnyte platform so that it can be enabled or disabled as needed. There is no set policy for disabling Migration App, once it has been disabled. However, customers may request to have it disabled to eliminate confusion after onboarding is complete.


Q: Is there anything special I need to do to differently if I was originally using the CMM Agent CLI tool, but now want to use Migration App?

A: Yes, check out this Helpdesk article for an important prerequisite.


Q: What are the firewall requirements for Migration App?

A: If you have a firewall set up for outbound access, you will need to whitelist the following URLs before running the Migration App.

  • https://<your-domain>
  • datacenters)
  • datacenters)

For more detailed setup information for Migration App, please see the Product Guide.


Q: While installing the Agent for the first time, what if it stalls at "Power Save is Enabled"?

A: You need to disable the sleep mode entirely. Unfortunately, power settings are handled differently depending on the Windows version, so this is sometimes less than obvious. Go to your Windows search field and type Power. Open Power & Sleep settings. Every option for going to sleep, idling or turning off the machine should be set to Never.


Back to Top


The Agent


Q: How can I find my Agent ID?

A: See this Helpdesk article How do I Get the Cloud Migration Manager Agent ID?


Q: Why do I need to provide my Windows Login credentials to set up my Agent?

A: Migration App requires information to identify both the Source and the Destination. Your Windows Login defines the Source, so you need both the username and password for an identity that has access to network shares. The Destination is defined by the domain and the Admin’s user name. For more information, see this Helpdesk Article.


Q: is the Agent Setup form case-sensitive?

A: Yes and no. Egnyte user name is not case-sensitive. But Windows AD user names are case-sensitive.


Q: What do I do if my Agent becomes disconnected from the Cloud?

A: See this Helpdesk article Reconnecting the Cloud Migration Manager Agent to the Cloud.


Q: What version is the Migration App Agent currently?

A: The Migration App Agent is presently on version 3.10.0. In most cases, the Agent will autonomously update to the latest version. After any Agent update your existing Migration Jobs will continue to run as before.


Q: How can I tell what version of the Agent I have running?

A: Navigate to your the Migration Dashboard and click on the Source in question. It will expand to provide more details, including the version number.


Q: Can I update the Migration App Agent when a Migration Job is running?

A: No. You need to be sure no jobs are running before you update the Agent. For more information, see this Helpdesk article.


Q: I had to change my Windows password, and now my Agent is running but doesn't seem to have access to any network shares.

A: If you change the user password for the Windows user associated with the Agent, you will need to change it on the Agent settings as well. You can follow the steps explained in Using Migration App to Migrate Content from a Network Share to change your password and restart the Agent.


Q: Can I install more than one Agent on my Windows host machine?

A: No. There's no reason why you'd need to. One Agent is all you need for a single Source, and one Source can support the creation of multiple Migration Jobs. However, we recommend you run no more than 3-4 Migration Jobs concurrently.

For more complex migration projects, you can use your Migration Dashboard to manage additional Sources, which would require separate Windows hosts, each with a different agent installed.


Back to Top


The Migration Dashboard


Q: Why can't I see other Admins' migration jobs on the Migration Dashboard?

A: By design, Migration App aligns each migration job with the individual user who created it. As a result, you can only see the migration sources and jobs you created while logged in as a given user. For more complicated migration projects, many customers choose to create a single shared "Migration User," such as "" This allows multiple admins to log in with these credentials to share a single Migration Dashboard for visibility into all migration activities.


Q: How can I clean up my dashboard and remove some Sources and Jobs that are no longer needed?

A: See this Helpdesk article Deleting Sources and Migration Jobs from the Migration Dashboard.


Q: When would I see more than one Source on my dashboard?

A: The Migrations Dashboard allows for multiple Sources. However, only one Agent can be installed per Windows host machine, so in most cases you will only have one Source activated. The only time you would see multiple Sources would be when you are using the dashboard to run migrations from multiple Windows host machines. An example might be if you were running migrations from different physical offices. In this case, each host would have their own installed Agent running migrations from different locations to your Egnyte domain.

For each Source, you may create multiple Migration Jobs. We recommend running no more than 3-4 jobs concurrently, but you may create as many jobs as you need to migrate your data in a logical fashion.


Q: How do I know what an Error or Status Code means?

A: See this Helpdesk article Migration App Status and Error Codes for a complete listing. This can be helpful in troubleshooting and if you need to request technical support.


Q: Where can I find Migration Reports?

A: On the dashboard for any Migration Job, there’s a blue link in the upper right corner to Download report. Click on that to be redirected to the /Shared/Migrations folder on your Egnyte file server, where the report will be posted. From there, right-click on the file to download it and open it in Excel.


Back to Top


Creating a Migration Job


Q: Can I create a Migration Job where the source is a mapped drive letter?

A: Yes. You can create a job where the source is either a mapped drive letter, an absolute path or a UNC path. To determine a UNC path:

  1. Hold down the Windows key + R, type cmd and click OK.
  2. In the command window type net use then hit Enter/Return.
  3. Make a note of the required path, then type Exit, then hit Enter/Return.


Q: Can I create a Migration Job where the source data is on Azure Cloud?

A: Yes. You just need a Windows VM on Azure, and as long as the data is accessible as a mount point from that Windows VM, you'll be good to go.


Q: When I create a Migration Job, how do I specify the destination?

A: The destination needs to be a valid Egnyte folder path. The destination must be specified as /Shared/<filename> or /Private/username/<filename>. Migration App will create the folder named <filename> within the respective root folder. Folder names in the path cannot be empty, contain special characters ( * ? \ < > ), or start or end with a space, symbol or period.


Q: I just created a Migration Job but I'm getting an error “Unable to validate source path.” What do I do?

A: This occurs if the correct permissions for either the Source or the Destination aren’t in place. You need to authenticate the Agent as a User who has AD permissions to read from the Source, and you must also be an Egnyte Admin to access the Destination. 


Q: Are there any special considerations for a Windows workstation mapped to a Mac for source data?

A: Yes. We've seen this work successfully, when the Mac is assigned a drive letter on a network. This requires the Mac OS be updated to at least High Sierra 10.13.


Back to Top


What Gets Migrated


Q: Are there any limits to the size of migration jobs with Migration App?

A: We recommend a maximum of 1TB and 1 million objects per migration job. While Migration App itself doesn't impose a limit on migration jobs, it's ideal to parse jobs into smaller subsets to facilitate ingress into the Egnyte back end. Moreover, there are default limits for each domain that are quite a bit higher than 1TB/1M objects. See Maximum Migration Job Size for more information.


Q: Does the Migration App migrate empty folders?

A: Yes! By popular demand, we have released a new feature that enables "migration" of empty folders. Starting with version 3.10, you are offered the option to migrate empty folders with every Data Migration command. More information is available in this Helpdesk article.


Q: Migration App failed to migrate some folders in the job. Why would that be?

A: If folders are empty, and you didn't opt in for migrating empty folders, they will not be migrated. Another reason might be that the user who registered the Agent doesn’t have the necessary permissions to view those folders. And finally, there are limitations to what Migration App can migrate. More information may be found in this Helpdesk article Filtered and Unsupported Objects with Migration App.

Another possibility is if you have a folder on the source that contains only unsupported files. In this case, none of the files will be migrated, nor will the folder be created on the destination. And since this folder is not empty on the source, it will not be created as part of the empty folder migration step. So, in the end, this folder will always be missing in destination. There is no way presently to migrate it.


Q: Migration App failed to migrate some files. Why is that?

A: One common reason for files failing to migrate is that they may be currently in use. That's why we recommend running several True-Ups after the initial Data Migration and before the final Cutover. Remember that for the final cutover, all users must be "hands-off" the original source until cutting over to Egnyte.


Q: If there are folders with more than 50K children, can they still be migrated? Is 50K a hard limit or just a suggested limit for performance reasons?

A: A maximum of 50K immediate child objects is a fixed limit of the Egnyte platform, not of Migration App. You will need to break your folders down into smaller subsets to use Egnyte.


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

A: Yes, you can. In fact, that's an excellent use case for Migration App. See the Helpdesk article Using Migration App to Sync Data to Existing Folders in Egnyte.


Q: Can I use Migration App to migrate from a Flash drive?

A: Yes. A flash drive (USB drive) works the same way as any local drive. It can be a bit slower when compared to an internal SSD, but you should still be able to create and operate jobs sourcing the connected drive. 


Back to Top


True-Ups or Syncing


Q: How do I run a True-Up?

A: The first time you Migrate Data using a Migration Job, the app copies all the content from the source to the destination. The next time you return to that same migration job you will be prompted to run a True-Up.


Q: What's the difference between Migrating Data and running a True-Up?

A: The first time you Migrate Data is the only time you'll see the command "Migrate Data." After that, all subsequent runs will be True-Ups. And they do behave differently. Migrate Data simply checks to see if the content is on the destination, and if not, it will migrate it. However, a True-Up seeks to mirror the Source and the Destination. It does so through a multi-step process:

  1. It first scans the source.
  2. It then scans the destination.
  3. Next, it compares the source and the destination to build a table of Deltas - anything that's new, deleted, or has been changed on the source.
  4. Next, it migrates the Deltas to the destination.
  5. Next, it deletes any files on the destination that no longer exist on the source. 
  6. Then, if you have opted in for Empty Folders on the Data Migration Options dialog box:
    1. it deletes all empty folders on the destination.
    2. It creates empty folders on the destination that exist on the source.

Note that only in Step 4 does the details dashboard provide an estimated time of completion. This may be confusing, since the command can be running for an extended period of time without showing any progress. 


Q: If I run a True-up, does it create duplicates of what was already copied previously?

A: The True-Up command does not per-se create duplicates. But there are some considerations to keep in mind. Let’s look at a couple of different scenarios when running True-ups:

  • If a file is exactly the same at both the Source and the Destination, Migration App checks the size and mtime (mtime is a file attribute that records the time and date a file was last modified) of the file at Destination and does not re-send.
  • However, if a user renames or moves a folder to a different location on the Source, Migration App creates the new folder at the Destination and does not delete the old folder. That's when you get into a duplication scenario.
  • Alternatively, if a user deletes a folder on the Source that has already been migrated, the next time Migration App runs, it will delete that folder on the Destination. That’s because the Migration App is mirroring the two locations.



Back to Top




Q: How do I run the Sanitize command?

A: Sanitization is no longer a standalone (atomic) command. It is now an optional component of Data Migration. Clicking on Migrate Data brings up a modal where you select whether or not you want to sanitize the source.


Q: Does Migration App change long file path names when we run the Sanitize command?

A: No, it does not change file names or path names that are too long. These files and pathnames are merely flagged during Scan and can’t be migrated unless the user makes the necessary changes on the source. For more information about Egnyte path limits, see the Helpdesk article Unsupported Characters and File Types.


Q: What does the sanitization function do?

A: Opting in for sanitization changes any unsupported characters in filenames on the Source to an underscore. Once sanitization is complete, Migration App proceeds to migrate those files.

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

For more information about substitutions for unsupported characters, see this Helpdesk article Understanding the Sanitize Command in Migration App.


Back to Top




Q: How does Migration App migrate permissions?

A: Permissions migration involves three steps.

  1. Extracting the permissions from the source
  2. Mapping them to what they should look like at the Egnyte side
  3. Applying the permissions to the files on Egnyte


Q: How long does it take to migrate permissions?

A: It can take a fair amount of time to migrate permissions. They are applied at approximately one per second. 


Q: How does Migration App map permissions?

A: See this Helpdesk article Permission Translation with Migration App.


Q: Can I modify how permissions are mapped with Migration App?

A: No, not currently, although this is on our roadmap.


Q: Does Migration App migrate permissions at both the folder level and the file level?

A: Not exactly. Migration App migrates permissions for folders. The files contained therein inherit the parent folder's permissions.


Q: Are there any limitations for Migration App to migrate permissions?

A: Only that the Users and Groups must already exist on Egnyte.


Q: What happens if I migrate permissions but a User or Group has not been created on Egnyte?

A: The Migration Report provides a worksheet for both Missing Users and Missing Groups. Once you have created those Users and Groups on Egnyte, you may run Permissions Migration again. See this Helpdesk article Permission Translation with Migration App.


Q: Can I “sync” or True-Up permissions with Migration App?

A: No. In Migration App, Permissions Migration is an all-or-nothing command. We recommend you run Permissions migration at the very end of a Migration Job, right before you cut over all your users from using the Source to using Egnyte. If you run it multiple times, it will simply execute a full operation multiple times.


Q: What is the estimated speed for permissions to be applied in Migration App?

A: Once permissions are scanned and extracted from the source and mapped to Egnyte (the first two steps), they are then applied at a rate of one folder per second, regardless of the number of permissions aligned with each folder.


Q: Why doesn't Migration App provide any progress information in the Status Bar while permissions are migrating?

A: Permissions migration involves three distinct steps, and each step takes some time. In the current version, during the first and second steps no information is communicated through the Migration Dashboard to the user. Only once the permissions are being applied to the files on Egnyte (Step Three) does the progress bar show any movement. 


Q: If I migrate content into Shared, but it has different permissions on the Source than those set on the Destination (Egnyte), which permissions prevail?

A: This is controlled by the Egnyte CFS (Cloud File System) at the domain level. It defaults to "keep source permissions" but can be changed in Settings.


Back to Top


Speed, Bandwidth, and Throughput


Q: How can I estimate how long a Migration Job will take?

A: You can first check out the speed test for your domain. Go to https://<domainname> (replacing <domainname> with your domain).

Keep in mind there are a lot of factors at play, but this will at least give you a baseline. If you’re reading from a network share, that will also impact your upload speed. For more information, see How Long Will it Take to Upload, Backup, or Download my Files?


Q: Why does the estimated time to complete a migration job keep changing on the dashboard?

A: For every file, Migration App does a metadata operation on the background, so the ETA is a function of the number of objects in the migration (folders and files combined.) For a total payload of similar size, if it comprises lots of small files, it takes longer than if the migration comprised a few larger files. As a given Migration job works through the files, the estimated time will continue to change based on the size of the current files being moved.


Q: How many migrations can run concurrently from the same Agent?

A: This depends on the capacity of the host machine where the Agent is running. Each migration job takes around 250 MB of memory. Depending on your host machine CPU/memory, you may run three or four concurrent migration jobs. We don’t recommend running more than four jobs at one time. The limitation here is not the Migration App itself but rather the Egnyte system back end.


Q. Is there a minimum bandwidth requirement for the Migration App?

A: No. Migration Jobs will see higher throughput the more bandwidth you have. But high latency/low bandwidth is one of the use cases for Migration App. These jobs will take more time.


Q: What to do about improving upload speeds for migration jobs? Is it possible to set a number of threads for the Migration App to increase the throughput?

A: Yes. This is a feature of Advanced Mode


Back to Top


Advanced Mode


Q: What is Advanced Mode?

A: Advanced Mode is a setting that allows the Migration Operator to undertake a variety of more complex actions in Migration App. It is not enabled by default, so it must be first enabled for the domain, and then more options become available. Most Advanced Mode options are managed through modifying the JSON configuration file for an Agent. Accordingly, we don't recommend Advanced Mode be used by any but the most experienced Migration Operators.


Q: How do I get Advanced Mode enabled for my domain?

A: Submit a ticket to requesting enablement.


Q: What advanced features are available with Advanced Mode?

A: Advanced Mode enables the following features:

  1. Increasing the threads for a job to improve performance.
  2. Enabling migration of Symbolic Links.
  3. More features to come.

Q: How do you change the threads for improved performance?

A: This Helpdesk article explains the process.


Q: How do you use the Confluence feature?

A: This Helpdesk article provides context and instruction for use of the Confluence feature to enable migration from multiple sources to a common destination.


Q: How do you migrate Symbolic Links?

A: This Helpdesk article walks you through the process of following and migrating Symbolic Links.


Back to Top




Q: What if the credentials to register the Agent won't allow me to access the network share source server?

A: You must ensure the Windows host machine is on the same AD domain as the network share resources. Check out this Helpdesk article Ensuring Windows Host Machine and Source Are on the Same AD Domain.


Q: What if a Migration Job hangs?

A: Check out this Helpdesk article What if a Migration Job Hangs?


Q: What if the Agent Registration hangs?

A: Check out this Helpdesk article What if Agent Registration is Hanging?


Q: What if I’m unable to execute any commands?

A: Check out this Helpdesk article What if I Am Unable to Execute Any Commands in Migration App?


Back to Top


General Questions


Q: Can any Egnyte User use Migration App?

A: No, only Administrators should use the Migration App. Power Users can view the Migration Dashboard but cannot successfully run jobs without a workaround. Ask your CSM or Professional Services Agent for assistance if you wish to designate specific Power Users to use Migration App.


Q: Can Migration App be limited to be available to only certain Admin users on a domain?

A: No. Currently, Migration App is enabled for all Administrators on a given domain.


Q: Can any Administrator monitor migration jobs created by another Administrator?

A: No. Migration jobs are tied to the User/Domain. This becomes the key to each job and therefore only a given User can see their own Agents and Migration Jobs in the dashboard.


Q: If I need to stop a migration for some reason, can I restart it later? I don’t want to be using all the bandwidth during the day when it may impact other users doing their work.

A Yes. You can stop and restart a Migration Job at any time. However, any time you restart a Migration Job, it needs to do a complete scan of both the source and the destination. This allows it to identify what, if any, data has already been migrated. Actual movement of the data begins where it left off previously.


Q: If I need to restart a migration job, what do I need to do?

A: Return to the Migration Dashboard, click on Details for the migration job, and then click Migrate Data again. It will pick up where it left off.


Q: Where can I find my migration job logs?

A: It depends on how you’re logged into the Agent.
If you’re logged in as the Local System:


If you are logged in as the Local User:



Q: What if I have a feature request?

A: 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 screen shots 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.


Q: Is there a way to get a quick question answered?

A: You can always submit a support ticket to