# Elasticsearch migration from 7.17 to 8.15

**URL:** <https://discuss.elastic.co/t/elasticsearch-migration-from-7-17-to-8-15/384978>\
**Category:** Elasticsearch\
**Created:** [February 9, 2026, 3:24pm UTC](https://discuss.elastic.co/t/elasticsearch-migration-from-7-17-to-8-15/384978 "2026-02-09T15:24:37Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**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:** [February 9, 2026, 5:30pm UTC](https://discuss.elastic.co/t/elasticsearch-migration-from-7-17-to-8-15/384978/5 "2026-02-09T17:30:02Z")

</div>

> [@zaeemmasood](#):
>
> We need to upgrade from ES 7.17.3 to 8.15.2

What a coincidence, someone was doing same, same versions, last week in [this](https://discuss.elastic.co/t/elasticsearch-upgrade-from-7-to-8/384901) thread

Ah, it was you 😉

It's not really considered good etiquette to open parallel threads on essentially the same topic.

> [@zaeemmasood](#):
>
> Thanks. Will go for 8.19.11 as you advised

Good decision. You were told 8.15.x was ages old on the other thread.

The other thread stalled when it was suggested you do the same 7.x --\> 8.x upgrade on a throwaway environment first. You wrote:

"It is hard to get another environment for trial/testing purposes"

I am glad you have solved this issue and are able to deploy a completely different parallel cluster!

Anyways, I agree with @leandrojmp and @DavidTurner - in your situation I think you have better chances with an upgrade which, IMhO, is significantly simpler and is likely safer too.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-migration-from-7-17-to-8-15/384978)._
