Destinations and testing connections
FileAgent moves files between local folders, SMB shares, FTP, SFTP, Amazon S3, and Azure Blob. Any one can be a source or a destination — store credentials once and test before you rely on them.
Last updated September 17, 2026
#Supported systems
Any supported system can be a source or a destination, and you can combine them freely — for example SMB → S3, SFTP → local, or local → Azure Blob.
| Connector | Use it for | Plans |
|---|---|---|
| Local storage | Any folder the host can reach, including mounted drives. | All plans |
| SMB shares | Windows file shares and NAS devices. | All plans |
| FTP | Classic FTP endpoints, including legacy systems. | Pro and higher |
| SFTP | SSH file transfer — the common partner-exchange protocol. | Pro and higher |
| Amazon S3 | S3 buckets and prefixes (and S3-compatible storage). | Business and higher |
| Azure Blob | Azure Storage containers. | Business and higher |
| Email (File to Email) | Destination only: sends the transferred files as attachments through your SMTP server, up to 20 MB per message (larger batches send a size warning instead). | Pro and higher |
A connector's plan applies in every position: a job, archive, Scheduled Purge target, or connection test that uses a connector your plan doesn't include is blocked, whether it's the source or the destination. Sync/Mirror needs a file or bucket destination, so it can't deliver to Email.
#Credentials connect you to remote systems
Every remote system needs a stored credential — a connection profile (host/account/secret) managed under Credentials and referenced by jobs. Local folders don't need one. Storing credentials separately means rotating a password is a one-place change, not an edit to every job. Stored credentials are limited to 2 credentials on Free, unlimited credentials on Pro, unlimited credentials on Business, unlimited credentials on Enterprise; credential management is an administrator function.
- Stored credential
- A saved set of connection secrets, such as for SMB, FTP, SFTP, AWS S3, or Azure Blob, used by jobs, archives, and backups.
#Add and test a connection
- Go to Credentials → New credential and choose the connector type.
- Give it a clear name, like
Vendor SFTP — Acme. - Enter the connection details for that type (see the per-connector pages).
- Choose Test connection — fix any failure now, not at 2 AM.
- Save. The credential is immediately available to jobs.
#Get permissions right
Confirm the account has the access each job needs:
- Read/list on the source.
- Write on the destination.
- Delete on the relevant side for Move and Sync/Mirror and for Scheduled Purge.
Grant the least access that does the job — details per connector below, and in Credential best practices.