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. 


Symbolic links are objects within an integrated file system that contain a path to another object. A symbolic link (sometimes called a soft link), is similar to a shortcut in that it's a path name contained in a file. By default, Migration App recognizes but does not follow or migrate the content in symbolic links. Using an Advanced Mode option, you may change this to enable following and migrating content from symbolic links.

How to Identify if Symbolic Links Exist

After completing your first scan or initial Data Migration, download the Migration Report for the job.

In the first register Migration Summary, scroll to the right to the column titled Symbolic Links Present?


There are several possible entries for this column:

  • No: No symbolic links were found in the source data.
  • Yes but ignored: This is the default behavior. Migration App has identified that symbolic links are present, but will not  migrate the data.
  • Yes and followed: This will only appear when the Symbolic Links feature has been enabled.

If you wish to migrate the data associated with these links, see the following instructions.

Migrating Symbolic Links

Enabling Advanced Mode

First, you need to have Advanced Mode enabled for your domain. To do this, submit a ticket to to request it.  

Activating Symbolic Links for a Job

Once enabled, you now need to activate this feature for the job using the JSON configuration file. 

  1. From the Migration Dashboard, navigate to Settings.

  2. Click on the Source (Agent) related to the job in question.

  3. Click on Download Default Configuration File.

  4. Open the JSON file (using Notepad++ or Atom or another editor of your preference).  The default configuration file will look like this:


  5. Edit the file as follows:
  • Add "configName": NAME above line 2, replacing NAME with a name of your choice
  • add individual job sections for all jobs associated with this Agent
  • include the name and id for each job
  • add "symlink" : true in the migration job section for the those you want to apply the feature to (use "symlink" : false for those you don't)
  • include the transfers and checkers for each job
	"configName": "MyConfig",
	"name": "Dell Latitude",
	"id": "YaaZCTmVGzIrm3bFbBba",
	"config": {
		"transfers": 4,
		"checkers": 8
	"migrations": [{
			"name": "HRdata1",
			"id": "Mhk9ItgRmitPZeykPjFN",
			"config": {
				"transfers": 4,
				"checkers": 8,
				"symlink": true
			"name": "HRdata2",
			"id": "Wpmo6loFyIXccsAYVa8h",
			"config": {
				"transfers": 4,
				"checkers": 8,
				"symlink": false


6.  Save the configuration file and return to Settings to upload it to the Agent.

7.  Once uploaded, you will see a success message at the top, and the Custom Config will change to the name you provided.

8.  Prior to uploading the file, you may want to check the JSON syntax using any of the free online tools available, such as This can be useful if the Custom Configuration File upload fails with the #600 error (incorrect syntax).

9.  Return to the Migration Dashboard and select Details to view that migration job. You can now see that the job reflects the same Custom Config name, and you may proceed to run the job.


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