Filebase 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 Filebase with Mover — S3-compatible object storage on decentralized backends, with geo-redundancy by default and pricing that undercuts the hyperscalers.

SourcesDestinations
Amazon S3
Amazon S3
Microsoft Azure Blob Storage
Azure Blob
Google Cloud Storage
GCS
SFTP
SFTP
Akamai Linode Object Storage
Linode
Amazon S3
Amazon S3
Azure Blob
Microsoft Azure Blob Storage
GCS
Google Cloud Storage
Files.com Agent
Files.com Agent
Linode
Akamai Linode Object Storage
FilebaseFilebase

The decentralized angle

Why customers run migrations through Filebase

Two reasons keep showing up: cheaper storage, and geo-redundancy without paying the multi-region tax. Hundreds of Filebase migrations later, those two patterns cover most of what we've executed. The IPFS-pinning crowd is a third, smaller pile.

Into Filebase

Geo-redundancy without configuring it

Filebase stores data across multiple geographically-distributed nodes by default. You don't pick a region; the system replicates for you. For customers who want multi-region durability without the multi-region price tag, this is the pitch.

S3-compatible API

Filebase speaks the S3 API. Existing applications, SDKs, backup tools, and infrastructure-as-code keep working with a credential swap.

Pricing that undercuts the hyperscalers

Filebase lists storage at well below S3 Standard. For workloads where geo-redundancy and cost matter more than hyperscale ecosystem integration, the math works.

IPFS pinning for Web3 workloads

Filebase can pin objects to IPFS as part of its standard offering. Customers building on IPFS or working with content-addressed storage get a managed path rather than running their own IPFS infrastructure.

Out of Filebase

Multi-cloud rebalance to a hyperscaler

Moving primary storage to S3, Azure Blob, or GCS to align with specific compute, analytics, or compliance requirements Filebase doesn't target.

Cross-account or cross-bucket reorg

Splitting buckets across Filebase accounts or moving between access keys.

Common pairings

Pair Filebase with any cloud.

Filebase 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 Filebase the standard way. Provide the credential, nothing more — generate a scoped token if you want minimum-privilege.

Filebase access key + secret

The standard method. Generate access keys in the Filebase console; Mover uses them exactly like S3 access keys via Filebase's S3-compatible interface.

Scope:Mover uses the credential you provide and nothing more. Scope the access key to the specific bucket you're migrating.

The price

The pricing math, honestly.

Mover charges as low as $0.15 / GB when purchasing a 10 TB pack. Your Filebase-side cost depends on direction. No invoice math, no surprises — the dry-run shows the exact number before you commit.

Migrating into Filebase

Provider side

Free

Mover

$0.15 / GB

When purchasing a 10 TB pack

Filebase inbound is free. Filebase storage on paid plans lists well below S3 Standard — check filebase.com/pricing for the current rate.

Migrating out of Filebase

Provider side

Plan allowance

included up to bandwidth cap

Mover

$0.15 / GB

When purchasing a 10 TB pack

Filebase egress is included in the plan up to the plan's bandwidth allowance. Customers running well within their allowance pay zero for migrations out. Confirm your plan's allowance against the migration size before committing.

Pricing example

10 TB migration into Filebase

The exact dry-run estimate is the number to trust — it includes both line items, run against your actual data.

Mover fees
10 TB pack
$1,499
Filebase inbound
inbound is free
$0
Total
$1,499

The customer who picks Filebase over S3 usually does so for two reasons: cheaper storage at rest, and built-in geo-redundancy across decentralized nodes. For workloads where those two together beat the convenience of a hyperscaler ecosystem, Filebase wins on cost without compromising durability.

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.

01

Connect Filebase.

Paste a Filebase access key + secret generated in the Filebase console. Mover validates the credential and lists buckets it can see.

02

Choose source and destination buckets.

Apply filters and a date range if you want a partial migration.

03

Run a dry-run.

Mover walks the source bucket, counts files, sizes the transfer, and produces an exact cost estimate.

04

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.

S3-compatible object storage that uses decentralized networks (IPFS, Sia, Storj) under the hood. From the outside it behaves like any S3-compatible service — buckets, access keys, the same API. From the inside it replicates data across distributed nodes for geo-redundancy.

Start the move. finish.

Run a free dry run on your Filebase data. See the exact size, file count, and price before you commit a single GB.