Files.com Agent

The Files.com Agent connects Mover to servers that aren't directly accessible over the public internet, including on-premises file servers. With the Files.com Agent, you can migrate files to and from a host's local disks and drives, and from network-attached storage the host can reach over CIFS, SMB, or NFS.

Connections

Adding an Agent connection has three parts: save the connection in Mover, download its configuration file, and install the Agent as a service on the host system.

New Agent Connection

Create a new connection and choose Files.com Agent as its type.

Provide a Connection Label so you can identify the connection in a list. This matters most when you have more than one connection of the same type, since the label is what tells them apart.

Agent Configuration

Choose the Agent Permissions that Mover should have on the host system. Select Read and Write when the Agent will be a migration destination. Select Read Only when it will only be a source.

Set Agent Root Folder to an existing path on the host system. The connection can access only files and folders within this root.

Save the Connection to continue.

Configuration File

Edit the Agent connection in Mover and select Download Configuration File. The file contains the connection credentials and Agent settings, including logging and automatic updates.

Agent Installation

Download the Agent executable from the official download page. Choose the build for the host operating system and architecture, save it with the configuration file, and install the Agent as a system service on Windows, macOS, or Linux.

Connection Status

After you install and start the Agent service, check the connection in Mover. A Connected status means the connection is ready to use.

If the status is Waiting for connection, verify that the Agent service is running on the host.

Case Sensitivity

Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, MyFile.txt and myfile.txt can be two different files. A case-insensitive system treats those names as the same file.

Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.

Check the documentation on your host system to determine if you need to account for case sensitivity differences.