Files.com is built to move files and folders to Remote Server Mounts at enterprise scale. Many customers use this to migrate content from Files.com's internal storage out to their own infrastructure on a remote server integrated with Files.com. The platform handles high volumes without special configuration on your end, is designed for high-speed transfers, and adapts automatically when a destination behaves differently: throttling, slower ingestion rates, transient errors. The goal is that you focus on what to move and where, and Files.com manages the delivery.

High Volume Copies or Moves

Whether you are doing a one-time migration or an ongoing transfer, Files.com handles the operation on reliable, proven infrastructure. The right tool depends on whether the need is one-time or recurring.

One-Time Copies or Moves

For a one-time copy or move, use the Files.com web interface. Select your files, start the operation, and let it run. The web interface shows real-time progress so you can see exactly where the operation stands. Other clients, such as an FTP client, do not provide that visibility.

Recurring Copies or Moves

For copies or moves that need to happen on a schedule or triggered by file activity, use Automations. Automations run the same operation repeatedly without manual intervention. If your workflow involves keeping two locations in sync rather than a one-directional transfer, Sync is the right fit.

Copies or Moves From On-Premises Internal Storage

If the source is on-premises infrastructure rather than Files.com's internal storage, the Files.com Agent connects your internal servers to your Files.com site. Once the Agent is in place, copies and moves from your internal storage to a Remote Server Mount follow the same approaches described above.

Copies or Moves From a Local Windows or Mac Machine

If you are transferring files directly from a local Windows or Mac machine, the Desktop App or the CLI App are the most practical options. See Preferred Apps for File Transfer for guidance on choosing the right client for your workflow.

Destinations That Ingest Data More Slowly

For destinations including Box, Dropbox, Azure Files, OneDrive, SharePoint, Google Drive, and WebDAV, Buffered Uploads handles delivery automatically. Files.com receives the file, confirms the upload as complete, and then forwards it to the remote in the background at whatever rate the destination supports, with automatic retries built in. You do not need to manage the pace of the transfer yourself.

When you run a Move through the web UI, Files.com automatically updates Share Links, Permissions, Styles, Notifications, and Folder Settings (including Inboxes) to point at the new destination. You do not have to make any changes for these things to continue to function normally.

This only happens for a direct Move. A Copy from one location to another does not transfer any metadata or settings. For that reason, use Move rather than a Copy followed by a Delete.

Moving Folders That Have Folder Settings

When you move a folder that has Folder Settings configured, most settings carry over to the Remote Mount destination. The two exceptions are File Expiration and nested Remote Server Mounts, which are not compatible with Remote Server Mount and are not moved.

For a full reference on how Folder Settings behave within Remote Server Mounts, see Folder Settings Within Remote Server Mount.

Moving Existing Files and Folders to Remote Server Mount