Home›Services›MinIO migration

Move off MinIO to S3 storage that is still maintained

The open-source MinIO project is no longer maintained. Your backups, artefacts and application data may still sit on it. We pick the replacement that fits your size, copy the data with checks, and switch your applications to the new endpoint.

from $6,000 · fixed price Measured first, then fixed price and dates Data verified object by object
The problem

The open-source MinIO repository is archived and no longer maintained.1

What we do

Pick SeaweedFS, Garage or Ceph for your size, copy and verify the data, switch clients.

The result

Maintained S3 storage you control, with a tested restore.

Is this you?

What changed

From the MinIO repository on GitHub:1

The options

All three speak the S3 API. They differ in how they grow and how much running they need.

OptionUsually fitsTrade-off
SeaweedFSMany objects, small to large clusters, teams that want simple operationsFewer enterprise features than Ceph
GarageSmall, lightweight clusters, also across several sitesImplements a subset of the S3 API — we check yours against it
Ceph RGWLarge scale, or you already run Ceph for block or file storageMore moving parts; needs real Ceph skills
Stay on MinIO / AIStorYou prefer the vendor and its terms work for youLicence and price set by one company

What you get

S3 usage check

Which S3 features your applications really use — versioning, object lock, lifecycle rules, presigned URLs — tested against the chosen option before any data moves.

New storage cluster

Installed as code, with monitoring, alerts and capacity planning.

Data copied and verified

Buckets copied in the background, object counts and checksums compared, a final short sync at cut-over.

Users and policies

Access keys, bucket policies and service accounts re-created; old keys revoked at the end.

Clients switched

Applications, GitLab, Harbor, backup tools pointed to the new endpoint and tested.

Runbook

Adding capacity, replacing a disk or node, restoring a bucket, upgrading.

How it goes

The order is always the same. How long each step takes depends on your volume — the measurement in step 1 sets the price and the dates. Our free scope script gives the first numbers.

  1. Step 1 · 1–3 days

    Inventory and choice

    Buckets, sizes, clients and S3 features in use. Option chosen together; final fixed price.

  2. Step 2

    Build and test

    New cluster built; your applications tested against it with real operations.

  3. Step 3

    Copy

    Background copy with verification. Clients switched in batches, with a short final sync.

  4. Step 4

    Switch-off

    MinIO set to read-only, last clients found and fixed, then switched off.

What we need from you

  • Admin access to MinIO and a list of what writes to it.
  • Servers and disks for the new cluster (we size them in week one).
  • Owners of each client application to test their switch.
  • Network capacity for the copy — we schedule it around your peak hours.

Not included

  • Changing application code beyond endpoint and credentials.
  • Buying hardware.
  • Cleaning up data you no longer need — we report it, you decide.
from $6,000

Fixed price after the measurement in step 1. Paid by milestone.

What changes the price

  • Data volume and number of objects.
  • Number of clients to switch.
  • Features in use — versioning, object lock and replication take extra care.
  • Sites — one data centre or several.

Questions teams ask

Can we keep MinIO running a while longer?

Yes, and during the migration we do exactly that. Just don't treat it as a long-term home: without maintenance, new vulnerabilities stay open.

Is there downtime?

Usually only a short write freeze per client at the final sync. Reads can continue.

Do our applications need code changes?

Most only need a new endpoint and keys. If an app uses an S3 feature the target does not support, we find it in week one, before any data moves.

Which option do you recommend?

It depends on size and team. We give a clear recommendation after the inventory, with the reasons.

Often done together

Tell us how much data sits on MinIO

Rough size, number of buckets and what writes to them — enough for a first estimate.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Sources — public announcements, documentation and legal texts, for orientation only; not legal advice. MinIO and AIStor are trademarks of MinIO, Inc.
  1. GitHub: minio/minio repository (archived Apr 25, 2026)
Book a 30-minute call