The open-source migration engine for Elasticsearch and OpenSearch. Raw index-to-index data movement across every version combination. No vendor lock-in. Apache 2.0.
"Just stand up a new cluster and re-index everything."
Whether you're moving from Elasticsearch to OpenSearch or the other way around, you're sitting on 5-50+ TB of production data that must come with you. Compliance mandates retention. Customers depend on historical search. And no existing tool handles this migration at TB-scale without weeks of custom engineering.
multielasticdump supports --parallel across indexes, but single-index throughput is limited by the scroll API.[2] No checkpoint/resume. Fine for dev — impractical for production TB-scale.Configuration-as-code. Resume if anything fails.
Declare source, target, and runtime settings in a TOML config. Version-controllable, reviewable, repeatable.
Checkpoint/resume means if anything fails — network blip, node restart, disk full — you pick up exactly where you left off. Not from zero.
Start with the open-source core. Upgrade when you need TB-scale parallelism, compliance features, or white-label embedding.
The only migration tool built for compliance-aware data migration between Elasticsearch and OpenSearch.
Minimum log retention. Audit trails must be preserved during and after migration.
Retention policies must be enforced, documented, and verifiable by auditors.
Protected health information retention mandate. No gaps allowed.
Minimum one year, often extended. Continuous monitoring logs included.
Financial data and audit logs. The longest standard retention window.
If it speaks the Elasticsearch or OpenSearch API, Kravex can move it. Source or destination — doesn't matter.
Managed services: AWS OpenSearch Service, Elastic Cloud, Aiven, Instaclustr (NetApp), Bonsai, DigitalOcean, OVHcloud, Oracle OCI — any managed offering that exposes an ES or OpenSearch endpoint.
Self-hosted: Kubernetes via ECK or the OpenSearch K8s Operator, Docker Compose, Helm charts, bare-metal RPM/DEB installs, Ansible-provisioned VMs — however you run your clusters.
On-prem: Air-gapped data centers, private cloud, behind a VPN — Kravex is a CLI binary with a TOML config. No SaaS dependency, no phone-home, no cloud account required.
Other tools lock you into a single vendor's ecosystem. AWS Migration Assistant only targets Amazon OpenSearch Service. Elastic's reindex API requires direct cluster connectivity. Kravex works across every combination — managed to self-hosted, on-prem to cloud, or anything in between. Your infrastructure choices are yours. The migration tool shouldn't be the constraint.
Start with the open-source CLI. Upgrade when you need TB-scale performance.