Mover and rclone.
Two tools, one ecosystem.
Comparison · rclone
rclone is excellent. Files.com is a proud sponsor of the rclone project, and rclone has a native Files.com backend — you can sync to and from Files.com directly from the rclone command line. We use rclone ourselves and recommend it for the workloads it's built for. This page is about when each fits, not about beating the other one.
Where each fits
When each is the right tool.
Both are good answers to different questions. The comparison below is meant to help you pick the right one for what you're doing right now — not to argue that one beats the other.
Free, BSD-licensed, 70+ providers, full CLI control.
You're comfortable at the command line.
rclone lives in a terminal. If you'd rather write `rclone copy s3:source-bucket azure:destination-container` than click through a web UI, that's a feature, not a friction.
You want maximum flexibility.
rclone exposes chunk sizes, parallel transfers, server-side copy, bandwidth limits, encryption layers, and dozens of other knobs. If you need fine control, you get it.
You're running an ongoing scripted transfer.
rclone is great for cron jobs, scripted backups, and recurring syncs. Set it up once, schedule it, monitor via your own logging.
Your workload is single-machine.
rclone runs as a single process on one machine. For a developer or sysadmin who controls the host, that's the simplest possible deployment.
Cost matters and time doesn't.
rclone is free. If you have the bandwidth (literal and figurative) to set it up, debug it, and maintain it, the price is unbeatable.
Web dashboard, free dry-run, exportable audit log, support SLA.
You need a dashboard, not a CLI.
Multiple people will want to see the migration's progress. The IT director, the security reviewer, the finance person. None of them want to learn a CLI.
You need a dollar estimate before you commit.
rclone has `--dry-run` (lists files). Mover's dry-run returns: number of files, total size, time estimate, Mover fees, provider egress fees, all line-itemized in dollars. The buyer wants to see the bill before approving the work.
Compliance evidence matters.
SOC 2 Type II, HIPAA BAA, GDPR DPA. Per-object exportable audit log. Doing this with rclone is possible but it's an engineering project to build the logging pipeline.
You're on a deadline.
Mover has email support with SLA and engineering escalation. When something fails at 2am the night before a cutover, the path forward is a support ticket, not a forum search.
You want one tool across the team.
Multi-tenant SaaS, role-based access, shared visibility. Two engineers running two migrations don't need to coordinate via chat thread.
The ecosystem is better with rclone in it.
Files.com sponsors rclone financially because the project deserves support and because rclone's existence makes the entire cloud storage ecosystem better. We also maintain the rclone Files.com backend, which lets rclone users sync directly to and from Files.com.
So this page isn't a "Mover beats rclone" pitch. Mover and rclone serve different jobs. If both fit yours, the Files.com backend lets you use them together — developers reach for rclone on the command line, the team uses Mover for the enterprise migration with stakeholders, the data lives in Files.com either way.
The differences that matter
Where the CLI runs out of room.
rclone covers a category of users perfectly. Mover covers a different category. The arguments below are the cases where Mover is the better fit — not because rclone is bad, but because the work needs something else.
A web dashboard, not a terminal.
Reach for rclone if you live in a terminal — it's the right tool for that. Reach for Mover if multiple people will want to see the migration's progress: the IT director, the security reviewer, the finance person reading the bill. None of them want to learn a CLI.
Dollars before you commit.
rclone has --dry-run that lists files. Mover's dry-run returns the exact number of files, total size, time estimate, Mover fees, and provider egress fees — line-itemized in dollars. The buyer wants to see the bill before approving the work.
Evidence out of the box.
SOC 2 Type II, HIPAA BAA available, GDPR DPA available. Per-object exportable audit log. Doing this with rclone is possible but it's an engineering project to build the logging pipeline yourself.
Automatic retries and restartable jobs.
rclone has retry flags. Mover handles retries automatically with exponential backoff, resumes multipart uploads from the last completed part, and tracks the full migration as a single restartable job. Job state survives your laptop closing.
A workflow, not per-host config.
rclone is per-machine, per-user, with manual coordination by chat thread. Mover has multi-tenant SaaS, role-based access, and a shared dashboard. Two engineers running two migrations don't need to sync up over Slack about who's holding the config file.
A vendor on the other end of a deadline.
rclone has a great community forum and active GitHub issues. Mover has email support with response SLA and engineering escalation. When something fails at 2am the night before a cutover, the path forward is a support ticket, not a forum search.
Use both
They integrate. Many teams use both.
Developers reach for rclone day-to-day.
Ad-hoc moves, scripted syncs, scheduled backups — hitting Files.com or any of the 70+ other rclone-supported providers directly from the command line.
The same team uses Mover for the enterprise migration.
Multi-stakeholder projects with budgets and compliance review — where a dashboard, a dollar estimate up front, and an exportable audit trail matter more than command-line control.
The data lives in Files.com regardless.
Accessible from both tools because they share the same underlying storage. It's not Mover-or-rclone; it's Mover-and-rclone, each on its own job. This is a setup we see and recommend.
Common Questions
Mover and rclone, answered.
If you're already in the rclone world, the Files.com backend lets you keep going. If you're picking between the two for a specific migration, the answers below should help.
No. Mover is built on Files.com's own file sync engine — the same one running file operations for the 4,000+ organizations on Files.com. We sponsor rclone and maintain a Files.com backend for it, but the two are independent codebases.
Two tools, one ecosystem. Run the dry run.
If you're running a one-time enterprise migration with stakeholders, a free Mover dry-run shows the dollar amount in writing before you commit. If you're a developer scripting transfers, rclone is the right tool — and the Files.com backend lets you use both.