Moving native Files.com files into a Remote Server Mount changes which system holds the working contents. The destination uses the remote connection's permissions, naming rules, capacity, and recovery settings. This can place files on infrastructure your applications already use while retaining a Files.com access path.

Create the mount at an empty local folder first. It cannot be placed over the existing content to convert that content into remote storage. Then choose a copy or move according to whether the source must remain and whether existing links and folder configuration should follow the files.

High Volume Copies or Moves

Choose the transfer method for the source location, whether the work is recurring, and the result you need at the destination. A file arriving on remote storage is separate from a receiving application consuming it.

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. A Sync compares locations and transfers files that its selection rules identify as needing delivery. It can run in one direction or in both directions; recurring collection does not require a two-way Sync.

A recurring transfer that writes the same filename every run will eventually land on a file already at the destination. An Automation leaves that file alone until you turn on overwriting for the v1 action or v2 node. Once overwriting is on, the Automation deletes the existing file before writing the new one, so the account Files.com uses on the remote needs delete rights in the destination folder. A Sync normally writes over the existing file instead. It can fit a partner that grants write access without delete, but servers that refuse in-place replacement still need delete-and-recreate handling. Test replacement separately from a new-file upload.

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 using Buffered Uploads, Files.com receives the file before forwarding it to the remote in the background. Client upload completion confirms receipt by Files.com, rather than arrival at the destination. Check onward delivery and the destination files before removing a source copy or handing the location to a consuming application. Provider limits and required processing still apply.

When you run a direct Move, Files.com automatically updates Share Links, Permissions, Styles, Notifications, and Folder Settings (including Inboxes) to point at the new destination. This applies whether you start the Move in the web app or through the REST API, an SDK, or the CLI. You do not have to update these references manually.

A Copy does not redirect these existing links, permissions, or settings to the new destination. To preserve the existing configuration, use a direct 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, only settings compatible with mounts are retained at the destination. Archive Removed Files and Storage Location (Region) apply only to native storage and cannot be configured on or within a mount. A folder containing a Remote Server Mount cannot move inside another mount, because mounts cannot be nested. The Folder Settings lifecycle explains the storage boundary.

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