FEATURES / Migration & Sync
/// Migration & Sync
Move data between clouds. Without the downtime.
Migrate or sync between any two buckets — across accounts and clouds — with no size limit, in the background. Turbo-import into R2 with Super Slurper, cut over live with Sippy, and never buffer a byte on our servers.
Start for free/// How it works
Pick a source and a destination
Any two buckets — same account or different, same cloud or different. AWS S3, Cloudflare R2, Backblaze B2, Wasabi, MinIO, DigitalOcean Spaces, and 50+ cloud providers in all — plus any custom endpoint. Filter by key prefix to move only what you want.
Start the job and walk away
Copy once, or set up a repeating sync. The job runs in the background — checkpointed and resumable. You keep working; you don't babysit a terminal. Conflicts resolve OS-style: skip, replace, or ask.
Track it, get notified when it's done
Watch progress in the Transfers tab. Pause and resume anytime. Get a notification the moment it finishes. No size limit, no server-side buffering — bytes stream straight from source to destination.
No size limit, ever
Copy and sync route through a streaming engine (GetObject → multipart Upload), so there's no cap on object or job size. Terabytes move the same way kilobytes do — and nothing is buffered on our servers.
Across accounts and clouds
Move data between providers, between AWS accounts, or between on-prem MinIO and the cloud. One UI for every direction. Escape a provider, consolidate estates, or seed a new region without a single script.
R2 Super Slurper — turbo import
Importing into Cloudflare R2? Storafleet drives R2's native Super Slurper over the Cloudflare API — a bulk-import fast-path that's roughly 5× faster than standard streaming. Great for a one-shot 'get off AWS egress' move.
R2 Sippy — zero-downtime cutover
Sippy does copy-on-read live migration: point R2 at your old bucket and it serves reads immediately, copying each object into R2 on first access while the rest backfills. You cut over with zero downtime and no big-bang migration window.
Filters and conflict control
Target exactly the keys you want with prefix filters. On a name collision, choose skip, replace, or ask — the same intuition you'd expect from moving files on your own machine.
Background, resumable, tracked
A lease-based worker runs jobs with checkpoints, so a transfer survives interruptions and resumes where it left off. Progress and history live in the Transfers tab — not in a script's scrollback.
/// Without Storafleet
Moving data between clouds means hand-rolled scripts, egress surprises, and a downtime window you have to schedule and pray through.
- rclone / aws s3 sync scripts you have to write, monitor, and resume by hand
- Big-bang cutovers that need a maintenance window and risk broken links
- No way to move terabytes without a box to run the job on
- Cross-account and cross-provider moves each need their own tooling and credentials
- Zero visibility — progress lives in a terminal's scrollback
/// With Storafleet
A streaming migration engine with provider fast-paths. Start a job, keep working, get notified when it lands — no scripts, no downtime.
- Point-and-click copy or sync between any two buckets, any cloud provider, any account
- R2 Sippy copy-on-read = cut over with zero downtime; Super Slurper = ~5× bulk import
- No size limit and no server-side buffering — bytes stream source → destination
- Prefix filters + skip/replace/ask conflict handling, like moving files locally
- Background, checkpointed, resumable jobs tracked in a Transfers tab with completion alerts
/// When you'll use this
Escaping AWS egress with a live cutover
AWS egress is eating the budget and you want to serve assets from Cloudflare R2 (zero egress). You enable Sippy on a new R2 bucket pointed at your S3 bucket. R2 starts serving reads immediately — each object copies on first access while Super Slurper backfills the rest in the background. No maintenance window, no broken links, no script to babysit.
Key featureR2 Sippy copy-on-read + Super Slurper backfill
Consolidating buckets after an acquisition
Two companies merged; storage is scattered across three AWS accounts and a Backblaze B2 bucket. You set up copy jobs from each source into one consolidated bucket, filter by prefix to keep paths clean, and let them run overnight. In the morning the Transfers tab shows every job complete — no per-account CLI gymnastics.
Key featureCross-account, cross-provider copy with prefix filters
Nightly sync to a cheaper backup provider
You want a second copy of production data on Wasabi for cheap durability. You create a sync job from your primary bucket to Wasabi and let it run on a schedule. New and changed objects flow over automatically — a real off-site backup without standing up infrastructure or paying for a backup SaaS.
Key featureScheduled cross-provider sync
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