On-premise to cloud migration,
without opening a port.

Servers and applications migrate on their own program. The files are the part that finishes this month.

The file server in the closet, the NAS under a desk, the SMB share everyone maps on their first day: Mover moves them into any cloud through an Agent that runs inside your network and connects outbound. No inbound firewall rule, no VPN, no staging box. A free dry run counts the bytes first, the bulk pass runs while people keep working, and incremental runs make the cutover a non-event.

Run a Free Dry RunSee The Agent
$0.15/GBat scale — no subscription, no minimums
0inbound ports opened
3operating systems the Agent runs on
20+cloud destinations

A file server into SharePoint.

The most common on-premises migration there is: department shares becoming document libraries as part of a Microsoft 365 move. The folder tree arrives intact, the filters leave the archive behind, and the cutover happens when the delta is small.
SharePoint as the destination; the Agent as the source.

A NAS into object storage.

Years of archives, backups, and compliance records on a Synology or QNAP that has to be retired. Cold data lands in S3, Wasabi, or Backblaze B2 at a per-gigabyte price the appliance never matched, with no egress fee for leaving your own hardware.
Decommission the box after the last incremental run.

A firewalled source into anything.

Plant-floor servers, branch-office shares, a system of record nobody is allowed to expose. The Agent runs where the data is and connects out, so the source stays exactly as unreachable from the internet as it is today.
One outbound connection. No DMZ, no reverse proxy, no port forwarding.

How the migration runs.

Six steps from the first install to powering the server down. The cloud migration guide covers the decisions around them; this is the on-premises path through it.

Install the Agent inside the network.

The Files.com Agent is a single binary for Windows, Linux, or macOS that runs as a service on a host that can reach the data: the file server itself, or any machine with the share mounted. No Java, no Docker, no middleware.

It connects outbound. Nothing opens inbound.

The Agent makes one outbound connection to Mover. No inbound firewall rule, no port forwarding, no VPN, no DMZ box. The source stays as invisible from the internet as it is today.

Point it at the paths that move.

Scope the Agent to the directories being migrated. Anything the host can read is a valid source: local disk, SMB and CIFS shares, NFS exports, mapped network drives, a Synology, QNAP, or NetApp mounted on the host.

Dry run first, for free.

Mover walks the share, counts files, sums bytes, and prices the exact usage pack before anything moves. A file server that has grown for fifteen years is full of surprises, and the dry run finds them while changing your mind is still free.

Move in parallel while people keep working.

Multi-threaded transfers from the Agent to the destination, retries on transient failures that never bill, and a run log with the disposition of every file. The first pass moves the bulk with the server still in service.

Incremental runs, then the cutover.

A difference-aware incremental run copies what changed since the bulk pass. Repeat until the delta is minutes of work, switch people to the destination, run one last pass, and the old server can be powered down.

On-premises to cloud questions.

Reaching a server behind the firewall, which sources and destinations work, how long it takes, and what it costs.

Moving data that lives on hardware you run, a Windows or Linux file server, a NAS appliance, an SMB or NFS share, into a cloud service. For servers and applications that is an infrastructure program. For the files, it is a data migration: read the share, move the files and the folder structure to the cloud destination, catch up the changes, cut over. Mover does the second kind.

Through the Files.com Agent, a small service you install on a host inside the network. It reads the paths you scope it to and makes a single outbound connection to Mover. Nothing is opened inbound, no VPN is set up, and the server is never exposed to the internet.

Anything a Windows, Linux, or macOS host can read: local disk, SMB and CIFS shares, NFS exports, and mapped drives, which covers Windows file servers, Linux servers, and NAS appliances from Synology, QNAP, NetApp, and the rest. If the host can open the folder, the Agent can migrate it.

Any of the 20+ connections: Amazon S3 and every S3-compatible store, Azure Blob and Azure Files, Google Cloud Storage, Wasabi, Backblaze B2, SharePoint, OneDrive, Google Drive, Dropbox, Box, and an SFTP server. A file server that becomes SharePoint document libraries is the most common move; a NAS that becomes cold object storage is the second.

It depends on the bytes and on the uplink out of your building, which is usually the slower side and sets the pace. The dry run gives the byte count up front. The bulk pass runs in the background over days for a multi-terabyte server; the incremental runs that follow are short, and the cutover itself is minutes.

No. The bulk pass runs while the server stays in service. Incremental runs copy the changes made since, and the switch-over happens when the delta is small enough to finish between two meetings. Downtime is a choice, not a requirement.

A one-time usage pack from $0.15 per GB at scale, priced exactly by the dry run, with no subscription and no minimum. There is no egress fee leaving your own hardware, which is one reason on-premises to cloud is the cheapest migration to run.

The folder tree arrives as it left, and include and exclude rules let you reshape it on the way: leave the archive folder behind, drop the temp directories, move one department’s share into one library. Permissions on the destination follow the destination’s model, so plan the sharing structure on the dry run rather than after.

Yes. The Agent gives read or write access to the paths it is scoped to, so a NAS can be the destination for a cloud backup or a compliance archive, and the same dry run, filters, and incremental runs apply.

Source-side post-migration cleanup removes what moved, the old share is retired, and the hardware is decommissioned. If the business needs the on-premises data to stay reachable alongside the cloud, that is an ongoing hybrid workflow rather than a migration, which is what Files.com runs.

Move the files; the server never leaves.

Install the Agent, point it at the share, and run a free dry run. Mover counts the files, sums the bytes, and prices the exact pack. The migration starts when you say so, and the server stays where it is until the last file has moved.

Run a Free Dry RunView Documentation