> For the complete documentation index, see [llms.txt](https://moverdocs.files.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moverdocs.files.com/connections/file-servers-and-protocols.md).

# File Servers and Protocols

Mover can connect to file servers directly over a supported protocol or through the Files.com Agent. The right method depends primarily on whether Mover can reach the server over the public internet.

Use a direct [FTP/FTPS](/connections/file-servers-and-protocols/ftp-ftps.md), [SFTP](/connections/file-servers-and-protocols/sftp.md), or [WebDAV](/connections/file-servers-and-protocols/webdav.md) connection when the server has a publicly resolvable address and its firewall permits the required traffic. Prefer an encrypted protocol and keep server identity verification enabled.

FTP and SFTP connections expose a *Max Connections* setting for servers that need a lower connection count.

Use [Azure Files](/connections/file-servers-and-protocols/azure-files.md) for a Microsoft Azure file share.

Use the [Files.com Agent](/connections/file-servers-and-protocols/files-com-agent.md) for local disks, network-attached storage, or other storage on a private network. The Agent makes an outbound connection, so it does not require an inbound firewall rule.

Install it on a host that can reach the migration data and choose a root folder that limits what the connection can access.

The server or host filesystem determines case sensitivity and can impose additional filename, path-length, locking, and permission behavior. Review [File and Folder Compatibility](/migration-behavior/file-and-folder-compatibility.md) and run a dry run before the live transfer.