Migrating from MinIO
When MinIO's open edition was stripped back, the migration path stayed open. Move to KerPlace over the S3 API — source online until cutover.
A transfer over the S3 API
KerPlace speaks the same S3 API and the same administrative protocol (madmin) as MinIO, so migration is a transfer to a fresh KerPlace over the API — not a rewrite, and not a disk-level conversion. Your source stays online until you cut over, and your tooling, SDKs and launch commands carry across; the MinIO-compatible launch form means existing start scripts often need no change.
What transfers
- Buckets and objects, faithfully, including content-type and metadata.
- Version history — each object’s versions are preserved, not flattened.
- Access — users and policies are carried across so least-privilege survives the move.
- Bucket settings such as versioning.
As objects land in KerPlace they are encrypted at rest with post-quantum cryptography — the migration is also an upgrade in protection.
How
A migration tool walks the source MinIO and reproduces it on KerPlace (buckets, then configuration and identities, then data and versions, then a verification pass). It is designed to be safe to re-run and supports a dry run first.
Plan the cutover like any storage migration: migrate, verify, then repoint clients to the KerPlace endpoint.
Full detail, source & scripts in the repository → https://github.com/agalletero/kerplace/blob/main/docs/MIGRATION.md