FEATURES / Migrate off AWS
/// Migrate off AWS
Escape the AWS egress bill. Without the downtime.
Move from Amazon S3 to Cloudflare R2 — zero egress fees, ~⅓ cheaper storage — with a live, copy-on-read cutover. No maintenance window, no scripts, no size limit. See your savings on real data first.
Start for free/// How it works
Connect your S3 bucket and an R2 bucket
Add your existing Amazon S3 bucket and a new Cloudflare R2 destination to Storafleet. Keys or IAM-Role for S3; an API token for R2. Two minutes, no infrastructure to stand up.
Flip on Sippy — cut over live
Point R2 at your S3 bucket with Sippy. R2 starts serving reads immediately, copying each object on first access. Your app keeps working the whole time — there is no maintenance window and nothing breaks.
Super Slurper backfills the rest
While Sippy handles live traffic, R2's Super Slurper bulk-imports everything else (~5× standard streaming). When it finishes, you're fully on R2 — and your egress bill is gone.
Kill the egress bill
Cloudflare R2 charges zero egress fees. For an app that serves a lot of data, the AWS data-transfer line item is often the biggest part of the bill — and on R2 it disappears entirely.
Cheaper storage, too
R2 storage runs about a third less than S3 STANDARD per GB. Use Storafleet's cross-provider cost comparison to see your exact number — on your real data — before you commit to anything.
Zero-downtime cutover
Sippy's copy-on-read means R2 serves traffic from day one while objects migrate in the background. No big-bang migration, no scheduled outage, no frantic DNS swap at 2am.
No scripts, no size limit
No rclone jobs to babysit, no box to run them on, no per-object size cap. The transfer streams source → destination and never buffers on our servers. Track it in the Transfers tab.
Leave on your own terms
Go all the way to R2, keep a synced copy on S3, or fan out to a third provider for backup. Storafleet doesn't lock you into a destination any more than it locks you into a source.
Or migrate anywhere
Not R2? The same engine moves data to Backblaze B2, Wasabi, MinIO, or DigitalOcean Spaces — across accounts and clouds. R2 just happens to be the sharpest answer to an egress problem.
/// Without Storafleet
Leaving AWS means a scary big-bang migration, hand-rolled rclone scripts, and an egress bill that grows every month you put it off.
- S3 egress fees that scale with your success and dominate the bill
- A migration so risky it needs a scheduled maintenance window — so it never happens
- rclone / aws s3 sync scripts to write, monitor, resume, and verify by hand
- Lock-in anxiety: once you're deep in one provider, leaving feels impossible
- No way to know the real savings until after you've moved everything
/// With Storafleet
A live cutover that serves from R2 on day one, backfills in the background, and shows you the savings before you commit.
- R2 Sippy copy-on-read = serve from R2 immediately, cut over with zero downtime
- Super Slurper bulk-imports the rest at ~5× standard streaming, in the background
- Cross-provider cost comparison on your actual data — decide with numbers, not vibes
- No scripts, no size limit, nothing buffered on our servers; tracked in a Transfers tab
- Leave on your terms: full move, synced backup on S3, or fan out to another provider
/// When you'll use this
Cutting a five-figure monthly egress bill
Your product serves images and video straight from S3, and egress is now your single largest cloud line item. You run Storafleet's cost comparison on your actual bucket, see the R2 number, and pull the trigger: Sippy serves traffic from R2 immediately while Super Slurper backfills overnight. Next month's transfer bill is effectively zero — with no downtime and no rewrite.
Key featureCost comparison → R2 Sippy live cutover + Super Slurper
De-risking the migration the team kept postponing
Everyone agreed S3 egress was a problem, but a big-bang migration felt too risky to schedule. With copy-on-read, there's no big bang: you enable Sippy on a Friday afternoon, traffic shifts gradually and safely, and you watch progress in the Transfers tab. The migration that sat in the backlog for a year ships in an afternoon.
Key featureCopy-on-read migration with live progress tracking
Keeping S3 as a hot backup
You move primary serving to R2 for the egress savings but want a second copy on S3 for peace of mind. You set up a sync job back to S3 on a schedule. Now you've got R2's economics for live traffic and an always-current copy on AWS — best of both, managed from one console.
Key featureScheduled sync R2 → S3 for an off-cloud backup
Your storage estate deserves a control plane.
Join the DevOps teams and founders who run every cloud's buckets from one control plane.
Free plan · No credit card · 50+ cloud providers · Cancel any time