Remote Server Sync

The Files.com Remote Server Sync feature gives you the ability to push or pull files to or from remote servers.

The remote server types that we support include Cloud Storage (Akamai Linode, Amazon S3, Azure Blob Storage, Azure Files, Backblaze B2, Cloudflare R2, Filebase, Google Cloud Storage, Rackspace Cloud Files, Wasabi), Content Collaboration (CCP) and Enterprise File Sync & Share (EFSS) solutions (Box, Dropbox, Egnyte, Google Drive, OneDrive, ShareFile, SharePoint), Managed File Transfer (MFT) systems (FTP, FTPS, SFTP, WebDAV) and more.

The Remote Server can be a third party cloud, another Files.com account, an on-premise server running the Files.com On-Premise Agent, or any server accessible via FTP, SFTP, WebDAV, S3 protocol or anything else. See the rest of this documentation for a list of all the accessible remote server types.

A remote sync can be a "push", where files from your Files.com site are transferred to the remote server, a "pull", where files are transferred from the remote server to your Files.com site, or a two-way "sync", where files that are new or changed in either location are pushed and pulled to each other to maintain a synchronized state between the folder on your Files.com site and the folder on the remote server.

Use a Remote Sync to pull files from a partner's remote SFTP server. The remote files can be deleted from the remote SFTP server once they've been successfully retrieved.

Use a Remote Sync to pull files from an internal cloud storage (Amazon S3, Azure, Google) bucket so that they're available for external partners and users to download.

Use a Remote Sync to push files to a partner's remote FTP server. The local copies of the files can be deleted once they've been successfully delivered.

Use a Remote Sync to push files to an internal system, such as an ERP, WMS, TMS, or HRMS for processing.

Use a Remote Sync to bi-directionally copy files between geographic storage regions so that downloadable content is available in both regions.