Cloud and data migration tools,
and which one fits your move.

Pick the tool for the thing that is moving. For files and storage, that is a self-serve service with a dry run and a published price.

There are five kinds of cloud and data migration tool, and they solve five different problems. The hyperscalers ship utilities for moving data into their own clouds. Open-source command-line tools copy between anything, for anyone who lives in a terminal. Self-serve services move files between clouds and platforms as a job you buy once. Suite-migration platforms move a whole Microsoft 365 tenant. Consultancies run infrastructure programs. Here is where each fits, and where Mover does.

$0.15/GBat scale — no subscription, no minimums
20+native connectors, plus the Agent
15 minfrom connect to first dry run
2×+Movebot’s throughput in head-to-head tests

The hyperscalers’ own utilities.

AWS DataSync, Azure AzCopy, and Google’s Storage Transfer Service are built to move data into their own clouds, and within them, and they are good at it. Moving out to a competitor is where they stop being the obvious choice: the tooling is one-directional by design, and the egress bill is not theirs to minimize.

Open-source command-line tools.

rclone copies and syncs between dozens of providers, free, scriptable, and trusted by people who live in a terminal. It is the right tool when the person running the migration is comfortable owning the command, the retries, and the log, and it connects natively to Files.com as a partner.

Self-serve migration services.

Mover, Movebot, and MultCloud move files between clouds and collaboration platforms as a job you set up in a browser and buy once. The differences are the engine, the price, and how much you know before you pay: Mover quotes the exact pack from a free dry run, publishes its per-gigabyte price, and ran more than twice Movebot’s throughput on multi-terabyte tests.

Suite-migration platforms.

BitTitan, ShareGate, and CloudM migrate whole tenants: mailboxes, users, groups, permissions, sites, and the files with them. If your project is a Microsoft 365 or Google Workspace tenant cutover, that is the category. If it is the files, it is a different job and a different tool.
Priced per user or per mailbox; bought by MSPs and IT teams running tenant migrations.

Migration consultancies.

For servers, databases, and applications moving to the cloud, a program with people in it. The files inside that program are still a tool job, and a consultancy that quotes a per-gigabyte fee to move them is reselling one of the tools above.
Engagement-priced. Right for infrastructure; expensive for data.

Where Mover fits.

Files and storage, between any two clouds or from an on-premises share, as a one-time job with the price known first. The cloud migration guide covers how the job runs.

A dry run that prices the job.

Before anything moves, Mover walks the source, counts files, sums bytes, and prices the exact usage pack. Free, every time.

Any two of 20+ clouds.

S3, Azure Blob, Google Cloud Storage, Wasabi, Backblaze B2, Dropbox, Google Drive, Box, OneDrive, SharePoint, SFTP, and on-premises file servers through the Agent. The catalog.

Parallel, direct, and logged per file.

Multi-threaded transfers provider to provider, retries that never bill, incremental runs for the cutover, and a run log that states the disposition of every file.

One fee, published.

Usage packs from $0.15 per GB at scale. No subscription, no minimum, no sales call to learn the price.

Cloud migration tool questions.

Which kind of tool for which job, what each costs, and how Mover differs from the services it is compared against.

There is no single best one, because the five kinds do different jobs. For servers, databases, and applications, the hyperscaler’s own migration services and a consultancy. For a whole Microsoft 365 tenant with mailboxes and identities, a suite-migration platform. For a bucket that can stay inside one hyperscaler, that provider’s transfer utility. For files and storage moving between clouds or platforms, a self-serve migration service like Mover, which is what this page is about.

A tool is software you run: a command-line utility, a desktop application, a web service you point at two accounts. A service is people: a consultancy or a managed-migration vendor that plans and runs the program for you. Data migrations are a tool job. Infrastructure programs are usually a service job with tools inside it.

Inside one provider, and into it, yes: AWS DataSync, Azure AzCopy, and Google’s Storage Transfer Service are built for moving data into and around their own clouds. Moving out to a competitor is where they stop being the obvious choice. Mover and AWS DataSync and Mover and AzCopy lay out when each fits.

Yes, and a good one for anyone comfortable at a command line. rclone syncs and copies between dozens of storage providers and is free and open source. It is also a Files.com partner that connects natively to the platform Mover comes from. When rclone fits and when Mover does covers the split.

All three are self-serve migration services for files between clouds. Mover runs on the Files.com sync engine, prices a one-time usage pack from $0.15 per GB with the exact pack quoted by a free dry run, and sustained more than twice Movebot’s throughput in head-to-head tests on multi-terabyte workloads. Mover and Movebot and Mover and MultCloud have the details.

Those are suite-migration platforms: they move mailboxes, users, groups, permissions, sites, and files together for a whole Microsoft 365 or Google Workspace tenant. That is a different job with a different buyer, usually an MSP running a tenant cutover. Mover moves files and storage. If your migration is a tenant, look at a suite platform; if it is the data, Mover is built for it.

Provider utilities are free to use and bill through the provider’s own metering. Open-source tools are free and cost your time. Self-serve services price per gigabyte or by plan; Mover publishes usage packs from $0.15 per GB at scale with no subscription. Suite platforms price per user or per mailbox. Consultancies price the engagement. In every case the source provider’s egress fee is a separate line, and often the larger one.

Mover, with the Files.com Agent reading the share from inside your network. The Agent connects outbound, so nothing is opened on the firewall, and the destination is any cloud on the list.

Try the tool with a dry run.

Connect the source and the destination and Mover prices the exact pack before anything moves. If the number works, the migration starts when you say so.