S3SDKDashboard

Data Migration

Use the method you already work with: S3 API, SDK, or the dashboard.

Create account View docs

Pick based on data size and control.

S3SDKDashboard

migration@filebase: ~/jobs/s3-import

session live

$ filebase migrate --source s3://archive-prod/logs --verify --preserve-metadata

[12:14:03] loading manifest: logs/2026-04-14.ndjson

[12:14:04] discovered 14,382 objects across 32 multipart batches

[12:14:06] reading source bucket: archive-prod

[12:14:08] syncing object logs/2026-04-14/app-01.ndjson 4.8GB

[12:14:11] upload chunk 08/32 -> filebase-us-east-1 88%

[12:14:13] upload chunk 09/32 -> filebase-us-east-1 72%

[12:14:14] upload chunk 10/32 -> filebase-us-east-1 61%

[12:14:17] checksum verified: sha256:c71b2c9f...

[12:14:19] committing multipart upload for snapshots/us-east-1/objects-1142

[12:14:22] metadata preserved: content-type, cache-control, etag

[12:14:24] destination object indexed successfully

[12:14:25] queueing next batch from exports/customers-parquet-02

progress [##################################..............] 68%

throughput 842 MB/s objects migrated 14,382 eta 11m

status

SOURCE

s3://archive-prod/logs

DESTINATION

filebase://archive-prod

CURRENT OBJECT

snapshots/us-east-1/objects-1142

VERIFY

sha256 enabled

recent

ok app-01.ndjson

ok app-02.ndjson

ok customers-parquet-01

run customers-parquet-02

Move data the way you already work Keep your existing S3 tooling and migrate into private, content-addressed storage.

Migrate Faster

The source stays the same. What changes is how long your team waits for the move to finish.

GCS

Other providers

More waiting before cutover.

GCS

Filebase

Less waiting before cutover.

How it works

Three straightforward steps: connect your client, move your data, and confirm everything landed where it should.

Connect

Create access keys and configure your S3 client with the endpoint and AWS Signature V4.

Transfer

Use your preferred S3-compatible tool to copy, sync, or upload data into a bucket.

Confirm

Check bucket contents and object metadata to confirm everything landed correctly.

Estimate your migration cost

Simple storage pricing starts at $7.50 for 500 GB, scales at $15/TB, and keeps object egress free.

How much data are you moving?

How much data do you egress monthly?

Filebase

$15/mo

AWS S3 Standard

$106.71/mo

Azure Blob Storage

$101.69/mo

Google Cloud Storage

$143.36/mo

Stored

Monthly estimate

Amount saved

This calculator is for informational purposes only. Prices are estimated from public pricing as of April 15, 2026 and do not include taxes or other fees. Filebase storage starts at $7.50 for 500 GB, then $15/TB with free object egress. AWS uses S3 Standard storage and public internet data transfer out. Azure uses Blob Storage Hot LRS in East US with outbound bandwidth from North America. Google Cloud uses Cloud Storage Standard in Iowa (us-central1) with data transfer to worldwide destinations. Check the published pricing: AWS, Google Cloud, Azure Blob Storage and Azure Bandwidth. For the purposes of this calculator, 1 GB is 1,000,000,000 bytes.

Move from S3, R2, Google Cloud, Backblaze, Azure, or MinIO without relearning how your storage works.

Keep the familiar model, keep the existing tooling, and make the cutover feel straightforward.

Create account Check pricing

Want to estimate the storage side first? Try the object storage calculator.