Migration app is the migration services hosted on Egnyte enabling users to execute migration jobs. These jobs facilitate the migration of content and permissions from the legacy on-premises systems to Egnyte. The users can easily manage these migrations from a centralized, cloud-hosted user interface.
Audience
This is intended for users who are new to Migration App.
Use Cases
Migration App helps users transfer their data from on-premises environments to Egnyte. Currently available only for Windows while support for macOS will be added soon. Here’s how it can be used:
-
Migrate data from various storage sources, including:
- Local disks
- Mapped drives
- SAN (Storage Area Network) drives
- NAS (Network-Attached Storage) drives
- AWS S3 mounted as mapped drives
- Scan source data before migration to get a clear understanding of what needs to be transferred.
- Sync changes with true-up functionality, ensuring that the latest updates from the source are reflected in the destination.
- Migrate permissions along with the data, maintaining access controls and security settings.
- Run up to five migration jobs at the same time, making it easier to move large amounts of data efficiently.
Benefits
Here are some key benefits of the Migration App in Egnyte that make data migration easier and more efficient for users:
- Simplifies Complex Migrations: Moving data from legacy systems can be a daunting task, but the Migration App provides a structured way to transfer files and permissions, reducing manual effort and potential errors.
- Saves Time with Parallel Transfers: Users can migrate multiple data sets at once (up to five concurrent jobs), making large-scale transfers faster and more efficient without disrupting daily operations.
- Ensures Data Integrity and Security: The app doesn’t just move data—it also preserves permissions, ensuring that access controls remain intact. This reduces security risks and prevents unauthorized access after migration.
- Reduces Downtime and Business Disruptions: With true-up options, users don’t have to pause their work. Any new or modified data can be updated in the destination without having to restart the entire migration process.
- Provides Visibility and Control: Users can scan their source data before migration, track progress in real time, and manage everything from the migration dashboard. This helps with better planning and troubleshooting if needed.
- Adapts to Different Storage Needs: Whether data is stored on local disks, mapped drives, SAN/NAS drives, or AWS S3, the app supports multiple environments, making it a versatile choice for different IT setups.
Known Limitations
- Migration App is currently available only for Windows environments. Support for macOS is planned for future releases.
- Default support is currently available to the customer’s Egnyte domains backed by Google Cloud Platform (GCP) and Azure. Support for other platforms, such as Amazon S3, Alibaba, and others is handled on a case-by-case basis, subject to business justification and approval.
- By default, all domains have a maximum concurrency limit of four active migration jobs. Attempting to initiate more than four concurrent jobs will result in an error message indicating that the limit has been exceeded.
- Migration App does not migrate file types that are incompatible with Egnyte, such as TMP files, active database files, and package files. Refer Unsupported Characters and File Types.
- Individual migration jobs should not exceed 10TB or 15 million objects. Any migration job that exceeds this will be interrupted. For optimal performance, Egnyte recommends keeping migration jobs within a 5TB limit.
- When migration job sharing is enabled on an Egnyte domain, jobs created by other administrators are not visible by default. To view these jobs, the currently logged-in admin must have at least one CMM agent installed and deployed—this includes agents that are currently in a disconnected state.
- As a workaround, the user can create a dummy CMM agent by following the Add Agent flow. It is not necessary to install the agent on a virtual machine.
- If the source dataset is invalid after migrating the data, running the validate command provides an incorrect missing file count in the validation report—even if the listed files are already present at the destination.
- Exclusion rules are not honoured when running the validate command. As a result, if the source contains files that were excluded during the scan, those files still appear in the validation report because exclusion rules are not considered during validation.
- Individual file size limitations for uploading data to Egnyte is controlled by Domain level Egnyte plans. By default, for the lowest level plan, Egnyte allows up to 100GB per file limit on uploads. Refer to this article for more details on the file size limits.
For details on pricing to increase limits beyond the existing plans, please contact your account manager or Egnyte Sales team.
Additional Resources
You can find all the documentation here, but the six important resources are:
- Migration App Product Guide (explains how to access the Migration Dashboard and describes all the basic functionality of the tool)
- The Migration App Egnyte University Course (provides a solid framework for using the tool)
- Prerequisites Using Migration App
- Migration App Limitations
- Firewall Requirements for Migration App
- Best Practices
- Migration App FAQs
Questions? Feature Requests? Other Feedback?
Feature suggestions or requests can be submitted here, with 'Migration App' mentioned in the text.
For complex requests that require screenshots or other attachments, submissions can be sent to support@egnyte.com. Include 'Migration App' in the email title to ensure the Support team forwards the comments to the Product team for consideration.