Audience
Any user of the Migration App.
Sections
Getting Started
The Agent
The Migration Dashboard
Creating a Migration Job
What Gets Migrated
True-Ups or Syncing
Sanitizing
Permissions
Speed, Bandwidth, and Throughput
Advanced Options and Advanced Mode
Troubleshooting
General Questions
Getting Started
How to get Migration App?
Admins of any Platform Plan domain can enable Migration App through self-service. By clicking on the application picker menu and selecting Migration from the drop-down, the Migration Landing Page will be displayed. If the Migration App is already enabled for the domain, two blue On-Premises Migration buttons will appear. Clicking either button provides access to the Migration Dashboard. If it is not yet enabled, a button labeled Request enablement for my domain will be visible. After completing a simple wizard, all Admins for the domain will see the blue On-Premises Migration buttons on the Landing Page.
What types of domains can use Migration App?
There are various types of Egnyte domains, but Migration App cannot be enabled for all types.
- Trial domains: In general, Migration App should not be used by Trial Domains. Trial domains are ineligible due to the storage limitations imposed by the trial program. If a Trial domain is limited to the standard 20GB storage, any migration job that exceeds this amount will fail. 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 myfiles.companyname.com which is essentially an alias for the standard Egnyte domain companyname.egnyte.com. To use Migration App must be enabled on the standard domain and all migrations should be run from there.
- FedRAMP Alias domains: Yes. Example: fedramp[mydomain].egnyte.com
- Egnytegov.com domains: Yes. These are supported and the customers can migrate to fedramp domains (*.egnytegov.com)
How do I find Migration App once my domain has been granted access?
Admins can find Migration under the application picker menu. Select that to view the Migration Landing Page. If the domain has access to Migration App, users will see two blue buttons labeled On-Prem Migration. Click either button to reach the Migration Dashboard.
Although only Admins can access Migration App by default, Power Users may also be granted access by exception. See Enabling Power Users to use Migration App.
Once enabled, does Migration App remain enabled?
Yes.
Is there anything special I need to do if I was originally using the CMM Agent CLI tool, but now want to use Migration App?
Yes, check out this Helpdesk article for an important prerequisite.
What are the firewall requirements for Migration App?
See Firewall Requirements for Migration App.
For more detailed setup information for Migration App, see the Product Guide.
What do I need to know before I use Migration App?
Refer to the Overview of Migration App article for all the necessary information to ensure successful use of the Migration App.
Back to Top...
The Agent
How can I find my Agent ID?
See this Helpdesk article FAQs About the Migration Agent
Is it required to provide Windows Login credentials to set up the Agent?
Migration App requires information to identify both the Source and the Destination. The Windows Login defines the Source, requiring 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 username.
Is the Agent Setup form case-sensitive?
Yes and no. Egnyte username is not case-sensitive. But Windows AD usernames are case-sensitive.
What can a user do if their Agent becomes disconnected from the Cloud?
Refer to this Helpdesk article Troubleshoot the Migration App Agent.
Does it matter what version of Migration App Agent a user has?
There is no need to be concerned about the version being run, as the Agent autonomously updates whenever a new version is available. Updates will be postponed until all active migration jobs are completed.
In some cases, a manual update of the Agent may be necessary. If this occurs, it is important to ensure that no Migration job commands are running. Once the Agent updates, existing migration jobs can continue as before
How can a user tell what version of Agent is running?
Navigate to the Migration Dashboard and click on any Agent in the left column. It will expand to provide more details, including the version number.
Can a user update the Migration App Agent when a migration job is running?
No. It is essential to ensure that no jobs are running before updating the Agent. For more information, see this Helpdesk article.
The user had to change their Windows password, and now the Agent is running but doesn't seem to have access to any network shares. What can be done?
When the password for the Windows user associated with the Agent is changed, it needs to be updated in the Agent settings. Follow the steps explained in Ensuring Windows Host Machine And Source Are On The Same AD Domain to change the password and restart the Agent.
Can a user install more than one Agent on their Windows host machine?
No. There is typically no need for more than one Agent per Source, as a single Source can handle the creation of multiple migration jobs. However, it is recommended to limit the number of concurrent migration jobs to 3-4. For more complex migration projects, additional Sources can be managed through the Migration Dashboard, with each Source requiring a separate Windows host and its own Agent installation.
Back to Top...
The Migration Dashboard
Why can't users see other user's migration jobs on the Migration Dashboard?
By design, Migration App aligns each migration job with the individual user who created it. As a result, a user can only see the migration Agents and Jobs they have created. For more complicated migration projects, many customers choose to create a single shared "Migration User," such as "Migration-Admin@domain.egnyte.com." This allows multiple admins to log in with these credentials to share a single Migration Dashboard for visibility into all migration activities.
However, If visibility into migration activities by other Admins is required, the Migration Jobs Listing can be downloaded from the Migration Dashboard. This will provide information about every Agent and every Migration Job active for the domain. See Viewing the Migration Jobs Listing.
In addition, shared migration jobs created by admins are accessible to all the other admins in the same domain. Learn more about the feature here.
How can a user clean up their dashboard and remove Agents and Jobs that are no longer needed?
Refer to this Helpdesk article.
When would a user see more than one Agent on their dashboard?
While the Migrations Dashboard supports multiple Agents, only one Agent can be installed per Windows host machine. In most cases, a single Agent will be activated. Multiple Agents would be visible only if migrations are being run from different Windows host machines, such as in scenarios involving separate physical office locations. Each host would have its own Agent to manage migrations from various locations to the Egnyte domain. For each Agent, multiple migration jobs can be created. Although it is recommended to run no more than 3-4 jobs concurrently, there is no limit to the number of jobs that can be created for logical data migration.
How a can user know what an Error or Status Code means?
See this Helpdesk article Migration App Status and Error Codes for a complete listing. This can be helpful in troubleshooting and technical support.
Where can a user find Migration Reports?
On the Details page 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 the Egnyte file server, where the report will be posted. From there, right-click on the CSV file to download it and open it in Excel.
A Migration Jobs Listing for the domain can also be downloaded from the upper right corner of the Migration Dashboard. This will include migration jobs created by all users.
Back to Top...
Creating a Migration Job
Can a user create a migration job where the Source is a mapped drive letter?
Yes. A job can be created with the source is as a mapped drive letter, an absolute path, or a UNC path. To determine a UNC path:
- Hold down the Windows key + R, type cmd and click OK.
- In the command window type net use then hit Enter/Return.
- Make a note of the required path, then type Exit, then hit Enter/Return.
Can a user create a migration job where the source data is on Azure Cloud?
Yes. it would need a Windows VM on Azure, and the data should be accessible as a mount point on that Windows VM. There can be some connectivity issues with this type of implementation, so Egnyte recommends creating smaller migration jobs and doing an initial proof of concept. There can be some connectivity issues with this type of implementation, so Egnyte recommends creating smaller migration jobs and doing an initial proof of concept.
How is the Destination specified when creating a migration job?
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.
For more information, see Creating a New Migration Job.
What steps should be taken if the error 'Unable to validate source path' appears after creating a migration job?
This occurs if the correct permissions for either the Source or the Destination aren’t in place. The user needs to authenticate the Agent as a User who has AD permissions to read from the Source, and must also be an Egnyte Admin to access the Destination.
Are there any special considerations for a Windows workstation mapped to a Mac for source data?
Yes. It has been observed that this approach is successful when the Mac is assigned a drive letter on a network, provided that Mac OS has been updated to at least High Sierra 10.13.
Can a user migrate data from an external drive (flash drive or USB drive) connected to their network, even if they don’t have enough space on the local machine to download the data there first?
Yes. If the user can map a data source to a letter drive on their AD network and view it from the Windows host machine where the Agent is installed, they can migrate it using Migration App.
Back to Top...
What Gets Migrated
Are there any limits to the size of migration jobs with Migration App?
Yes. See Maximum Migration Job Size for detailed information.
Does the Migration App migrate empty folders?
Yes! By default, users are offered the option to migrate empty folders with every Data Migration and True-Up command. However, they can also specify their preferences using Advanced Options. More information is available in this Helpdesk article.
What is meant by "Excluded files" and "Unsupported files and folders"?
See Understanding the Scan Results for more information.
Is Migration App case-sensitive?
Yes. See this article about canonically equivalent files for more information.
Migration App failed to migrate some folders in the job. Why would that be?
There can be multiple reasons for folders not migrating.
If folders are empty and the user 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.
There are also limitations to what Migration App can migrate. More information may be found in this Helpdesk article Understanding the Scan Results.
One edge case is when a user has 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.
Migration App failed to migrate some files. Why is that?
One common reason for files failing to migrate is that they may be currently in use. That's why Egnyte recommends 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.
More information may be found in the Helpdesk article Understanding the Scan Results.
If there are folders with more than 50K immediate children, can they still be migrated? Is 50K a hard limit or just a suggested limit for performance reasons?
A maximum of 50K immediate child objects is a fixed limit of the Egnyte platform, not of Migration App. The user will need to break their folders down into smaller subsets to use Egnyte.
See Best Practices for Creating an Egnyte Folder Structure.
Can Migration App migrate additional content into folders on an Egnyte domain that already contains data?
Yes, it is one of the excellent use cases for Migration App. To do this without duplicating data, the user needs to create individual migration jobs for each top-level folder under Shared or Private. They also need to enable Confluence Mode for these jobs, which will automatically set Sync Deletes to No/Never. This will ensure no data is inadvertently deleted. However, the user can change it to Yes/Always if needed.
Can I Migration App be used to migrate from a Flash drive?
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 users should still be able to create and operate jobs sourcing the connected drive.
What happens if there are files on the source with a future timestamp?
Egnyte allows its users to decide how future timestamps will behave during migration. The users can either exclude files with future timestamps or modify the timestamps on the source files to the present.
Back to Top...
True-Ups or Syncing
Is a True-Up the same thing as a Sync?
Yes.
How to run a True-Up? What’s the difference between Migrating Data and running a True-Up?
See Understanding Data Migration and True-Ups.
If a user runs a True-up, does it create duplicates of what was already copied previously?
No. Running a True-Up simply updates the Destination to match the current state of the Source.
What happens if a True-Up is run but a user has updated a file on Egnyte?
Egnyte generally discourages data changes until the entire Migration is completed. But if a user does change a file on Egnyte and a True-Up is run on the data, Migration App will just create a new version of the file. Here’s how it works.
- Migration Job “ABC” migrates File X to Egnyte on August 1.
- A user changes File X on Egnyte on August 2.
- On August 3, a True-up of Migration Job “ABC" runs. Migration App will recognize that File X is different. So it will again copy the August 1 version of the file, but this will appear as a new version of File X on Egnyte. This means the user will be able to access both versions on Egnyte.
What causes a True-Up to pause with a message asking to Confirm Sync Deletions?
During True-Ups, Migration App is designed to mirror the source and destination. So if any files or folders have been deleted from the source, they should also be deleted from the destination. However, this may not be intentional and can create a lot of confusion. To help achieve the desired outcome, there are multiple ways to opt out of Syncing Deletes. Even so, data deletion can come up unexpectedly. So if “excessive” deletions are identified during a scan for a True-Up, the job is paused, a warning message is displayed on the UI and an email is sent to the Migration Operator. This gives the opportunity to review what’s slated for deletion and decide on the best plan of action. Learn more about Confirming Syncing Deletes During True-Up.
What if a user wants to change the limits for Confirming Sync Deletes?
Egnyte has domains set to a default limit of 50 files and 50GB of data. So if a True-Up scan determines more than 50 files OR 50GB of data will be deleted, the Confirmation message is triggered. However, the user can opt to change the threshold for their domain by submitting a request to support@egnyte.com
Back to Top...
Sanitizing
How to run the Sanitize command?
Sanitize is not a standalone (atomic) command. It is an optional component of the meta commands Migrate Data and True-Up Data. By default, when data migration command is initiated, users are provided with a modal where they can select whether to sanitize on the Source or On-the-Fly. More information may be found in the Helpdesk article Understanding Sanitization Options in Migration App.
Does Migration App change long file path names when the Sanitize command is run?
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.
What does the Sanitize function do?
Sanitizing changes any unsupported characters in filenames to an underscore. This can be done in one of two ways:
- Sanitizing on the Source, where the unsupported characters are changed on the Source before migrating.
- Sanitizing On-the-Fly, where the characters are changed during migration and nothing is changed on the Source.
For more information about this, see Helpdesk article.
Back to Top...
Permissions
How does Migration App migrate permissions?
See Simulating and Migrating Permissions in Migration App.
How long does it take to migrate permissions?
It can take a fair amount of time to migrate permissions. They are applied at approximately one folder per second.
How do NTFS permissions translate to Egnyte permissions?
See Simulating and Migrating Permissions in Migration App.
Can a user modify how permissions are mapped with Migration App?
No, not currently, although this is on our roadmap.
Does Migration App migrate permissions at both the folder level and the file level?
Not exactly. Migration App migrates permissions for folders. The files contained therein inherit the parent folder's permissions.
Are there any limitations for Migration App to migrate permissions?
Yes. All Users and Groups must already exist on Egnyte in order for permissions to migrate successfully. If any Users or Groups are missing, the Migration Report will provide insights into that.
What happens if a user runs a permissions migration, but a needed User or Group has not yet been created on Egnyte?
The Migration Report provides a worksheet for both Missing Users and Missing Groups. After creating those Users and Groups on Egnyte, the user may run Permissions Migration again. See Simulating and Migrating Permissions in Migration App.
Can users “sync” or True-Up permissions with Migration App?
Not exactly. In Migration App, Permissions Migration is an all-or-nothing command. So running it multiple times just replaces whatever was created previously. Egnyte recommends running Permissions migration at the very end of a migration job, right before cutting over all the users from using the Source to using Egnyte.
Why doesn't Migration App provide any progress information in the Status Bar while permissions are migrating?
Permissions migration involves three distinct steps, and each step takes some time. During the first and second steps no information is communicated through the Migration Dashboard to the user because it is all happening at a database level. Only once the permissions are being applied to the files on Egnyte does the progress bar show any movement.
If a user migrates content into Shared, but it has different permissions on the Source than those set on the Destination (Egnyte), which permissions prevail?
This is controlled by the Egnyte cloud platform at the domain level. It defaults to "keep source permissions" but can be changed in Settings.
How does a Permissions Migration Simulation work?
It can be seen as a dry-run to help identify any gaps where users or groups still need to be created on Egnyte for the permissions migration to succeed. See Simulating and Migrating Permissions in Migration App.
Back to Top...
Speed, Bandwidth, and Throughput
How can a user estimate how long a migration job will take?
The user can first check out the speed test for their domain. Go to https://<domainname>.egnyte.com/speed-test/ (replacing <domainname> with the name of the Egnyte domain).
There are a lot of factors at play, but this will provide a baseline. If the user is reading from a network share, that will also impact their upload speed. For more information, see How Long Will it Take to Upload, Backup, or Download my Files?
Why does the estimated time to complete a migration job keep changing on the dashboard?
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.
How many migrations can run concurrently from the same Agent?
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 the host machine CPU/memory, users may run three or four concurrent migration jobs. Egnyte does not 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.
Is there a minimum bandwidth requirement for the Migration App?
No, migration jobs will see higher throughput with more bandwidth. But high latency/low bandwidth is one of the use cases for Migration App. These jobs will take more time.
What to do about improving upload speeds for migration jobs? Is it possible to specify additional threads for the Migration App to increase the throughput?
Yes. To do this, the user must first have Advanced Mode enabled for their domain.They can then use the Throughput or Threads features in Advanced Options, located on the Migration Details page.
Back to Top...
Advanced Options and Advanced Mode
What is the difference between Advanced Mode and Advanced Options?
Advanced Options are a set of feature controls available for all migration jobs. To access them go to the Migration Details page and click on the arrow next to Advanced Options in the left column.
Advanced Mode, however, is a setting that can be enabled for a domain that will give the Migration Operator several additional, more technical controls. We recommend this be used only by seasoned users of Migration App. See Advanced Mode in Migration App.
What can users control with Advanced Options?
Advanced Options provides controls for the following functionality:
- Sanitizing
- Migrating Empty Folders
- Changing the Skip Scan Period
- Excluding File Types
- Confluence Mode
- Scheduling Migration Jobs
- Symbolic Links
- Opt Out of Syncing Deletes
- Log Management
What is Advanced Mode?
Advanced Mode is a setting that allows the Migration Operator to undertake several 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. Advanced Mode features are very technical and can have a major impact on the host machine and migration job. Accordingly, we only recommend Advanced Mode for the most experienced Migration Operators. See Advanced Mode in Migration App.
How do I get Advanced Mode enabled for my domain?
Submit a ticket to support@egnyte.com requesting enablement.
What features are available with Advanced Mode?
Advanced Mode enables the following features:
- Increasing the threads (transfers and checkers) for a job to improve performance.
- Controlling bandwidth throughput for a job..
- Customizing the Agent Configuration
- Using Exclusion Rules - See Advanced Mode in Migration App.
How can users change the threads for improved performance?
This requires Advanced Mode to be enabled for the domain. See Advanced Mode in Migration App.
How to change the bandwidth throughput for reduced strain on my network?
This requires Advanced Mode be enabled for the domain. See Advanced Mode in Migration App.
How to modify the Agent Configuration file?
This requires Advanced Mode be enabled for the domain. See Advanced Mode in Migration App.How to control advanced exclusion rules?
This requires Advanced Mode be enabled for the domain. See Advanced Mode in Migration App.
Back to Top...
Troubleshooting
What if the credentials to register the Agent won't allow me to access the network share Source?
The user 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.
What if a migration job hangs?
Check out this Helpdesk article What if a Migration Job Hangs?
What if the Agent Registration hangs?
See this Helpdesk article Troubleshooting the Migration App Agent
What if I’m unable to execute any commands?
Refer to this Helpdesk article What if I Am Unable to Execute Any Commands in Migration App?
How can a user verify that all their data is migrated successfully?
There are a couple of ways to verify this: The Job Report and the Job Logs.
The Migration Job Report
- From the Migration Dashboard click the three dots next to the migration job and select Download the Job Report. Alternatively, from the Details page, click Download the Job Report in the upper right corner. Either link will take the user to the folder for the migration job on their Egnyte domain inside the Migrations folder under Shared. Download the report to open and view it in Excel.
- From the Job Report, the user can view a list of items that were not migrated by selecting the Exceptions register. This will list all files and folders that were not migrated and the reason they were excluded. On the Data Migration register or True-Up register, the user will find any files that failed to migrate due to an error. Everything else should have migrated successfully.
If the Job Report doesn’t provide a satisfactory explanation or if the user want to validate checksums, they can also drill down into the Job Logs.
The Job Logs
Locate a zip file from the same Migrations folder on the user's Egnyte domain where the Job Report was found. Download and click to expand it. Inside, there is a folder labeled status. The user should look for a file within this folder named success_[JOB ID]. This file includes the following information for every item in the migration job:
- Source Path
- Destination Path
- Operation
- Request ID
- Timestamp for the Operation
- Source Checksum
- Destination Checksum
To learn more about Migration App logs, read the article.
How can a user know why a file or folder was deleted during a True-Up?
The user can confirm this from the Job Logs that are stored on the local machine where they have the Migration App Agent installed.
Depending on how the user logged into Agent, they will find the logs in one of two places.
If logged in as the Local System, go to:
C:\Windows\System32\config\systemprofile\AppData\Local\egnyte-agent
If logged in as the Local User, go to:
C:\Users\[username]\AppData\Local\egnyte-agent\
Open the egnyte-agent folder and access the folder for each migration job labeled with the Migration ID.
Click to open the scan folder. For every command executed for this job, the user will see multiple CSV files. Every file is appended with “_[JOB ID]_[time/date stamp]_[Agent version].”
- cmmagent file – Created whenever a scan is run. May be eliminated in the future as it does not provide any additional information.
- scan file – Also generated for every command. It provides a complete list of all files and folders, including their path name. If IsDir is TRUE, the object is a folder. Each line item includes file size and last modified time.
- empty_folder file – This file is only created when the user opts in to migrate empty folders as part of the command. It lists all empty folders identified on the source.
- diff- file – This file is only generated as part of a True-Up. It provides a list of all files to be deleted, and why.
- diff+ file – Also only generated as part of a True-Up. It provides a list of all files to be added.
The diff- file will provide specific information about each file and folder that was deleted during True-Up. If the user does not want to Sync Deletes, they can disable that feature in Advanced Options. To learn more about Migration App logs, read the article.
What if a user can't open the migration report because it is corrupted?
While this is not a common occurrence, Excel files can become corrupted. See this article on how/why an Excel file might be corrupted, and some ways to fix them. In most cases, after fixing the file, the user should be able to reopen it normally.
Back to Top...
General Questions
Can any Egnyte User use Migration App?
By default, only Administrators can use Migration App. Power Users can be granted access by exception, but this has several prerequisites. See Enabling Power Users to use Migration App.
Can Migration App be limited to be available to only certain Admin users on a domain?
No. Currently, Migration App is enabled for the entire domain. All Admins can see Migration App, and if they make an exception for Power Users, all Power Users can see Migration App.
Can any Administrator monitor migration jobs created by another Administrator?
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. However, any user can download the Migration Jobs List which details all jobs created by all users.
If a user need to stop a migration for some reason, can they restart it later?
A Yes. Users can stop and restart a migration job at any time. However, any time they want to 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. Alternatively, they may wish to consider Controlling Bandwidth for their migration job, which is a feature that requires Advanced Mode be enabled for the domain.
If a user needs to restart a migration job, what do they need to do?
Return to the Migration Dashboard, click on Details for the migration job, and then click Migrate Data (or True-Up Data). It can take a while for the system to determine where it left off, but it will not duplicate content and it will proceed to completion.
Where can users find their migration job logs?
It depends on how they’re logged into the Agent.
If logged in as the Local System:
C:\Windows\System32\config\systemprofile\AppData\Local\egnyte-agent\[migration-id]
If logged in as the Local User:
C:\Users\[username]\AppData\Local\egnyte-agent\[migration-id]
Is there a way to view checksums for the migrated files?
Yes. They are included in the migration job log files. Find the logs for a migration ID (see previous question), then unzip the folder. Open the folder named status. Open the latest CSV file starting with success_[migration ID] to see the source and destination checksums for all files migrated.
What if I have a feature request?
For any feature suggestions or requests, feel free to submit them here, and mention Migration App in the text.
For more complex requests that would benefit from providing screenshots or other attachments, submit them to support@egnyte.com. Be sure to include Migration App in the email title. Our Support team will push the comments to the Product team for consideration.
Under what scenarios can the token expire and what is the impact associated with token expiration?
Token can expire in the following scenarios:
- Password is changed.
- Account is deactivated or deleted.
- Token is older than 60 days.
If the token expires, the migration job will come to a halt, preventing any further progress.
Is there a way to get a quick question answered?
Yes, submit a support ticket to support@egnyte.com.