Egnyte
Connect an existing Egnyte account through its FTPS or SFTP service when Files.com needs to collect or deliver its files. These are protocol-based connections, rather than a native Egnyte API connector, so Egnyte's protocol restrictions remain part of the workflow.
A recurring Sync is our recommended arrangement for these endpoints. For downstream processing, collect files into Files.com storage first so the next stage can operate independently of Egnyte's connection limits.
Connecting to Egnyte
Enable the FTP or SFTP protocols in your Egnyte configuration settings before connecting. Egnyte limits FTP and SFTP access to its Admin and Power User account types. Its protocol requirements allow password authentication, rather than SSH-key authentication.
When configuring the Remote Server, use the hostname format ftp-yourdomain.egnyte.com, where yourdomain is your Egnyte domain name. Enter the username in the format username@domainname, such as jsmith@acme. Egnyte rejects usernames that do not include the domain name.
Use an encrypted connection and match its protocol and port to the service enabled in Egnyte. The account's remote permissions determine which folders and operations the connection can use. Files.com folder permissions separately control access through a mount.
Egnyte documents a limit of seven simultaneous FTP uploads. Its transfer limits and endpoint performance can slow or interrupt recurring file transfers. When configuring the FTP or SFTP Remote Server connection, set Max connections to 1 to reduce concurrent requests to Egnyte. Increase it cautiously only after transfers run reliably; we have seen problems even at 2 connections.
Recurring Transfers
Use a recurring Sync to move or copy files between Egnyte and Files.com. Each run compares source and destination and transfers files that are missing or differ in size. If the provider interrupts a transfer or temporarily limits the connection, a later run can detect files that still need to transfer. This recurring comparison makes Sync a better fit for these endpoint limitations.
We do not recommend running Automations directly against the Egnyte connection. For workflows that process incoming files, Sync them into Files.com storage first, then run Automations on those local files. This keeps subsequent processing from depending on the provider's connection availability and transfer speed.
Bulk Data Migration From Egnyte
Egnyte applies limits to FTP, FTPS, and SFTP that make extracting data far slower than ingesting it.
To migrate large quantities of data from Egnyte to Files.com, do not use FTP, FTPS, or SFTP.
We recommend the Egnyte desktop app to download the data, followed by our CLI app to upload it to Files.com. This adds a local copy, but lets the bulk collection use Egnyte's desktop access instead of its limited FTP/SFTP service.