Amazon S3 migrations,
without scripts.
Mover is the data-migration tool from Files.com. One-time moves between 20+ providers — no subscriptions, no surprises, no scripts.
Migrate data to or from Amazon S3 with Mover — fast, simple, and at a fraction of what other migration tools charge.
Amazon S3What we see in the dry runs
Why S3 migrations happen
S3 is in everyone's stack. Most migrations are about adding a layer to it — backups, analytics feeds, multi-cloud reads — or eventually moving off it when the egress bill stops making sense. Hundreds of moves later, the reasons split cleanly.
Consolidating multi-cloud spend onto AWS
Teams running compute on EC2 or EKS pull data in to eliminate the cross-cloud egress they were paying on every read.
Standardizing on S3 as the cross-team durable layer
Analytics, ML, backup, and application teams all read from one S3 namespace; Mover backfills it from wherever the data lives today.
Bringing on-prem archives into durable object storage
File servers, NAS, and tape archives consolidate into S3 at a fraction of on-prem cost.
Cost arbitrage to Wasabi or Backblaze B2
Both run a fraction of S3 Standard at rest and charge zero egress fees. For workloads that read more than they write, the round-trip pays for itself in months.
Multi-cloud rebalance to Azure or GCS
Moving primary storage to align with analytics tooling, regional residency, or a strategic move off AWS.
Cross-region or cross-account S3 → S3 reorg
Account splits, region migrations, or compliance-driven reorganization.
Common pairings
Pair Amazon S3 with any cloud.
Amazon S3 migrations rarely happen in isolation. These are the providers we pair with most often — one-click setup on either side, same dry-run flow, same audit trail.
Connection
How Mover connects.
Mover supports 2 standard AWS authentication methods. Pick the one that matches how your team manages credentials.
IAM user (access key + secret)
Quickest setup; recommended for one-off migrations from accounts the user controls.
Assumed role (STS)
Recommended for cross-account migrations and for environments where rotating access keys is a hard requirement.
Egress Savings
See your twelve-month savings.
Move from a paid-egress provider to one with free egress and your monthly invoice shrinks. Plug in your data size and how much you read from storage each month — the calculator does the rest, including the one-time Mover migration cost.
Current cost on Amazon S3
per month
$348
New cost on Wasabi
per month
$35
Monthly savings
recurring
$313
One-time Mover migration
1× 5 TB + 1× 100 GB
$848
12-month savings
$3,754
Before subtracting the one-time migration cost.
Payback period
2.7 mo
$848 migration ÷ monthly savings.
Net savings, year one
$2,906
Numbers use published standard-tier rates from each provider as of May 2026. Actual invoice varies by region, committed-use discounts, and your specific contract. Mover migration cost uses the cheapest combination of prepaid usage packs that covers the data size — packs stack, so a 2 TB migration is two 1 TB packs, not one 5 TB pack. The dry run prices the migration against your actual data and shows the exact one-time Mover cost before you commit.
Getting started
4 steps to Go.
From credential to first byte in four clicks. The dry-run is free, every time, and shows the exact cost before you commit a byte.
Connect S3.
Paste an IAM access key or paste the assume-role ARN. Mover validates the credential and lists buckets it can see.
Choose source and destination buckets.
Apply filters and a date range if you want a partial migration.
Run a dry-run.
Mover walks the source bucket, counts files, sizes the transfer, and produces an exact cost estimate — Mover fees + AWS egress.
Launch.
Live progress, automatic retries on transient failures. Pause, resume, or cancel at any time.
Common Questions
Frequently asked.
Most teams launch their first migration in under 15 minutes. The dry run is free, every time.
An IAM user with access key + secret, or an assumed role (STS) for cross-account migrations. Mover provides a least-privilege IAM policy you can paste straight into the AWS console — read on the source bucket, write on the destination, and nothing else.
Start the move. finish.
Run a free dry run on your Amazon S3 data. See the exact size, file count, and price before you commit a single GB.