Data migration from elasticsearch to opensearch

Versions (relevant - OpenSearch/Dashboard/Server OS/Browser):

OpenSearch 3.0.0

Describe the issue:

I deployed and configured an OpenSearch 3.0.0 cluster on a Linux VM. Now I need to migrate data from an existing ElasticSearch 8.9.0 cluster to this OpenSearch cluster. How can this be done? I initially wanted to migrate using Migration Assistant, but it only supports uploading to cloud providers (we don’t use a cloud provider). Is there no option to upload data using Migration Assistant in Minio? If Migration Assistant isn’t suitable, is it possible to successfully migrate data from ElasticSearch 8.9.0 to OpenSearch 3.0.0 using Snaphot and Restore or Rolling Upgrade?

Configuration:

Relevant Logs or Screenshots:

Hi @aleksss,

Unfortunately, neither Snapshot and Restore nor Rolling Upgrade can be used in this scenario. Migration Assistant does support this migration path, but it is typically deployed in the cloud. That said, both the source and target clusters can be on-premises, provided you have the necessary network connectivity (or at least access to a snapshot from the source and to the target when using the “bring your own snapshot” option described below).

You do have the option to deploy Migration Assistant locally. However, local deployments are limited: we don’t currently support the level of scaling you may need, and you may encounter deployment challenges that are more difficult to troubleshoot. For example, the backfill component, Reindex-from-Snapshot, can run locally with a single instance but cannot scale horizontally. By contrast, deploying in AWS allows you to use the “bring your own snapshot” option to read snapshots stored and it may be possible to read from MinIO.

Looking ahead, we are actively working on a Kubernetes release that should make these scenarios easier. While this release is not yet officially supported, the community has already begun testing it and submitting issues. You can track progress here:

If you need additional guidance, please open an issue here: GitHub Issues.