Amazon S3 to Wasabi,
without the egress invoice.
The cost-arbitrage move. Wasabi storage is roughly a fifth the price of S3 standard and Wasabi doesn't charge egress — for archival and infrequent-access workloads the math gets compelling fast.
Mover handles S3 → Wasabi end to end. Authorize an S3 access key, authorize a Wasabi access key, see the price before a single byte moves. The dry run is free and includes the AWS egress estimate so the math is honest before you commit.
From
Amazon S3
To
Wasabi
Why teams move from S3 to Wasabi.
Most S3 → Wasabi migrations are about price. Storage at a fifth the rate, zero egress fees, S3-API compatibility — for archival, backup, and infrequent-access workloads the savings often pay for the migration in the first month.
Storage at roughly a fifth the per-TB cost
Wasabi's headline rate is a flat per-TB-per-month number well below S3 standard. For multi-TB archival or backup workloads the recurring savings dwarf the one-time migration cost — often inside the first month or two.
No egress fees
Wasabi doesn't charge for data egress within fair-use limits. Workloads that read storage frequently — distribution, downstream processing, media delivery — stop bleeding budget on the per-GB read tax that S3 imposes.
S3-API compatible
Wasabi speaks the S3 API. Applications, backup tools, and scripts that already talk to S3 mostly point at a new endpoint and keep working. The migration is the bulk of the work; the integration retrofit is small.
Predictable monthly bill
Wasabi's pricing is per-TB-per-month flat. No request fees, no tiering surprises, no class-transition charges. The bill is the same every month for the same data — which makes finance happy in a way S3 invoices rarely do.
4 steps to Go.
From credential to first byte in a handful of clicks. The dry-run is free, every time, and shows the exact cost before you commit a byte.
Connect Amazon S3.
Provide an IAM access key with read on the source bucket. Mover supports scoped, least-privilege credentials and stores keys in an encrypted credential store.
Connect Wasabi.
Provide a Wasabi access key with write access to the destination bucket. Wasabi keys work the same way S3 keys do — Mover authenticates against the Wasabi endpoint for the right region.
Run a free dry run.
Mover walks the S3 source, sums bytes, and produces an exact-cost estimate that includes Mover fees and the AWS egress cost. The dry run is free, every time.
Launch the migration.
Live progress, multipart parallelism, automatic retries on transient failures, structured audit log of every object moved.
The pricing math, honestly.
S3 charges egress (typically $0.09/GB at standard rates). Wasabi charges nothing for ingress. The line items are Mover (as low as $0.15/GB on a 10 TB pack) and AWS egress. The dry run shows both numbers at the dollar before you commit.
10 TB S3 → Wasabi migration
AWS egress varies by region and committed-use discounts. The dry run shows the exact AWS-side cost for your data.
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.
Frequently asked.
Most teams launch their first migration in under 15 minutes. The dry run is free, every time.
Run a free dry run. Connect Amazon S3 and Wasabi, and Mover walks the source, counts every file, sums the bytes, and returns the exact file count and price before you commit. Buy the matching usage pack, launch, and Mover handles the transfer — re-running later moves only what changed or failed.
Depends on the workload, but for archival and infrequent-access data the storage delta is large enough that one-to-two months of saved storage usually covers the migration. Hot data with heavy egress benefits even faster because Wasabi doesn't charge for reads.
Mover migrates the current version of each object by default. Versioned migrations — pulling every historical version — are supported on request; this multiplies the byte count, so the dry run is the right place to confirm what you actually want to move.
Object metadata (Content-Type, custom headers) is preserved. Wasabi has a single storage class — no Glacier-style tiers — so the destination treats every object uniformly. If your S3 estate uses Glacier or Deep Archive, those objects need to be restored to standard before Mover can read them.
The dry run estimates AWS egress at standard rates. Committed-use discounts or a direct-connect arrangement lower the actual invoice. For very large migrations (~100 TB+), AWS Snowball is an option — though for most migrations under that size, network transfer through Mover is cheaper and faster end to end.
Yes. Filters on the S3 side narrow the source to specific prefixes, date ranges, or object-name patterns. Useful for staged cutovers where you move one workload at a time and validate before the next.
Move S3 to Wasabi and cut storage cost.
Connect both sides, run a free dry run, see the exact cost — including AWS egress. Launch when you are ready.