S3-Compatible Storage migrations,
without scripts.
Mover is the data-migration tool from Files.com. One-time moves between 20+ providers — no subscriptions, no surprises, no scripts.
Connect any S3-compatible service to Mover. DigitalOcean Spaces, Linode Object Storage, Vultr, Scaleway, IBM Cloud, Oracle Cloud, Hetzner, Storj, Tigris, self-hosted MinIO or Ceph — if it speaks the S3 API, Mover can migrate to or from it.
S3-CompatibleThe provider-agnostic view
Why S3-compatible migrations happen
The S3 API has become the lingua franca of object storage — DigitalOcean Spaces, MinIO, Scaleway, NextCloud, dozens more. Migrations happen in every direction. Hundreds later, the reasons still cluster: match the storage to the compute, or move to where the storage gets cheaper.
Match your storage to the rest of your stack
Customers consolidate onto DigitalOcean Spaces alongside DO Droplets. Onto Linode Object Storage alongside Linode compute. Onto a regional provider in a country the hyperscalers underserve. The pattern: storage gets cheaper and integration improves when it lives next to the compute.
Self-host with MinIO or Ceph
Teams running their own object store — MinIO clusters, Ceph deployments, TrueNAS or Synology with S3 endpoints — use Mover to fill it from cloud sources or to drain it to the cloud.
Use a regional or sovereign provider
EU-only providers (Scaleway, Hetzner, OVH), sector-specific clouds, or sovereign object storage offerings. Data residency requirements often push customers to providers the named hyperscalers don't reach.
Consolidate onto a hyperscaler
Moving primary storage to S3, Azure Blob, or GCS as your stack standardizes on one ecosystem.
Move from self-hosted to managed
Retiring an on-prem MinIO or Ceph cluster — the maintenance overhead stopped being worth it.
Cross-provider reorg
Splitting buckets across accounts, regions, or providers as the team's needs evolve.
Common pairings
Pair S3-Compatible with any cloud.
S3-Compatible 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 connects to Various the standard way. Provide the credential, nothing more — generate a scoped token if you want minimum-privilege.
S3 access key + secret + endpoint URL
The standard configuration. Mover needs three pieces of information for any S3-compatible service: the access key, the secret key, and the endpoint URL of the service. Region may be required depending on the provider.
The price
The pricing math, honestly.
Mover charges as low as $0.15 / GB when purchasing a 10 TB pack. Your Various-side cost depends on direction. No invoice math, no surprises — the dry-run shows the exact number before you commit.
Provider side
on most providers
Mover
When purchasing a 10 TB pack
Inbound is free on most S3-compatible providers. Storage rates vary widely — from around $5/TB/month on discount providers to $20+/TB on managed-cloud offerings. Check your provider's pricing page.
Provider side
see your provider's pricing
Mover
When purchasing a 10 TB pack
Egress fees vary by provider. Some discount providers (Wasabi, Backblaze, R2) charge zero egress; others charge hyperscaler-equivalent rates. Confirm your specific provider's egress policy before sizing the migration.
Pricing example
10 TB migration to or from an S3-compatible provider
The exact dry-run estimate is the number to trust — it includes both line items, run against your actual data.
Many of the discount-storage stories on Mover — Wasabi, Backblaze, R2, Filebase — are S3-compatible providers with their own pages because their pricing is interesting enough to highlight specifically. If your current provider has its own page on Mover, start there. This page is for everything else.
Getting started
5 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.
Gather your provider's credentials.
Access key, secret key, endpoint URL, and region if your provider requires one. All four are visible in your provider's console or admin UI.
Connect in Mover.
Paste the four fields. Mover validates the credential and lists the 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 Mover-side cost estimate.
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.
Any of them. If a service exposes a standard S3 API, Mover can connect. Examples include DigitalOcean Spaces, Linode Object Storage, Vultr Object Storage, Scaleway Object Storage, Hetzner Object Storage, OVH Object Storage, IBM Cloud Object Storage, Oracle Cloud Object Storage, Tigris, Storj, and self-hosted MinIO or Ceph deployments. The named Mover pages (S3, Wasabi, Backblaze, R2, Filebase) get their own pages because their pricing or feature story is worth highlighting; everything else uses this configuration.
Start the move. finish.
Run a free dry run on your S3-Compatible Storage data. See the exact size, file count, and price before you commit a single GB.