Moving Existing Files and Folders to Remote Server Mount

Because Remote Server Mount is constantly getting better and better with support for new remote types, we find that many Files.com customers seek to move high volumes of files from Files.com's internal storage to a Remote Server Mount.

As such, we've put together the following guidelines for moving things to a Remote Server Mount.

First, we recommend always using our Web Interface to perform moves. The web interface will show the progress of cross-remote moves via a status bar in the upper left. If you use some other client, such an FTP client, you will not get real-time status of the move.

Secondly, if the files being moved number in the thousands, or are more than a few levels deep, we recommend breaking up the move into smaller moves. You can do this by creating the top level of target folders inside your mounted folder as new folders, then move the files and folders they are to contain in batches. Again, do this via the web interface, using the Move command.

The services we allow you to integrate with all respond differently to high volume transfers, and managing with smaller batches helps ensure that your Files.com site does not overwhelm the remote service.

Whenever you run a Move via the web UI, we will automatically update Share Links, Permissions, Styles, Notifications, and Folder Settings (including Inboxes) to the new destination.

This happens automatically and you do not have to make any changes for these things continue to function normally.

However, this only occurs when you do a direct move. If you Copy a folder from one location to another, no metadata or settings will be transferred during the copy.

This is why we recommend doing everything using a Move, rather than a Copy followed by a Delete.

Moving a folder that has Folder Settings configured for it into a Remote Mount will only retain compatible Folder Settings.

Folders with incompatible Folder Settings, such as File expiration, GPG encryption/decryption, and Remote Server Mount will not be moved to the Remote Mount destination.