# Migrate Elastic indexes betwewn v6 and v8 **URL:** \ **Category:** Elasticsearch\ **Created:** [May 8, 2025, 12:10pm UTC](https://discuss.elastic.co/t/migrate-elastic-indexes-betwewn-v6-and-v8/377943 "2025-05-08T12:10:26Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![miguel4](https://avatars.discourse-cdn.com/v4/letter/m/ee59a6/32.png) [@miguel4](https://discuss.elastic.co/u/miguel4)\ **Post date:** [May 8, 2025, 12:10pm UTC](https://discuss.elastic.co/t/migrate-elastic-indexes-betwewn-v6-and-v8/377943/1 "2025-05-08T12:10:26Z")
Hello, I currently have a Stack ELK with version 6.x of Elastic whose data we want I have to migrate to v8.x. I want to migrate only the indexes. With dumps I have seen that it is impossible to do it directly without going through v7. What would be the best way to do it? I had thought of creating a logstash pipeline between the two Elastic clusters, is this feasible in these versions? Thank you very much. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [May 8, 2025, 12:17pm UTC](https://discuss.elastic.co/t/migrate-elastic-indexes-betwewn-v6-and-v8/377943/2 "2025-05-08T12:17:11Z")
Have you looked into [reindexing the data from the remote cluster using the reindex API](https://www.elastic.co/guide/en/elasticsearch/reference/8.18/docs-reindex.html#reindex-from-remote)? ---
**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\ **Post date:** [May 8, 2025, 12:21pm UTC](https://discuss.elastic.co/t/migrate-elastic-indexes-betwewn-v6-and-v8/377943/3 "2025-05-08T12:21:39Z")
> [@miguel4](#): > > I want to migrate only the indexes Is this now effectively a static data set, i.e. the indices are what they are, and not changing. There is no further ingest on the 6.x cluster ? ---
**Author:** ![miguel4](https://avatars.discourse-cdn.com/v4/letter/m/ee59a6/32.png) [@miguel4](https://discuss.elastic.co/u/miguel4)\ **Post date:** [May 8, 2025, 1:55pm UTC](https://discuss.elastic.co/t/migrate-elastic-indexes-betwewn-v6-and-v8/377943/4 "2025-05-08T13:55:23Z")
yes, they are static data. ---
**Author:** ![miguel4](https://avatars.discourse-cdn.com/v4/letter/m/ee59a6/32.png) [@miguel4](https://discuss.elastic.co/u/miguel4)\ **Post date:** [May 8, 2025, 1:56pm UTC](https://discuss.elastic.co/t/migrate-elastic-indexes-betwewn-v6-and-v8/377943/5 "2025-05-08T13:56:14Z")
I did not know this solution, it looks good, thank you very much! ---
**Author:** ![miguel4](https://avatars.discourse-cdn.com/v4/letter/m/ee59a6/32.png) [@miguel4](https://discuss.elastic.co/u/miguel4)\ **Post date:** [May 13, 2025, 11:02am UTC](https://discuss.elastic.co/t/migrate-elastic-indexes-betwewn-v6-and-v8/377943/6 "2025-05-13T11:02:16Z")
I would like to add more information for completeness and ask for guidance on using the reindexing API. The source elastic is on on-premise machines (v6) but the target elastic is on kubernetes(v8). Is there any way to easily configure SSL for this scenario? Any additional advice? ---
**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\ **Post date:** [May 13, 2025, 12:23pm UTC](https://discuss.elastic.co/t/migrate-elastic-indexes-betwewn-v6-and-v8/377943/7 "2025-05-13T12:23:26Z")
security risks/decisions are yours, but I used reindex.ssl.verification\_mode: none in my elasticsearch.yml on the destination side when faced with a similar issue, noting also the reindex.remote.whitelist setting needed set. And I didn't got v6--\>v8, in fact went v9--\>v8, and nothing left my home LAN. YMMV.