# Elasticsearch v5.5.3 to v7.17.7

**URL:** <https://discuss.elastic.co/t/elasticsearch-v5-5-3-to-v7-17-7/382028>\
**Category:** Elasticsearch\
**Created:** [September 17, 2025, 6:16pm UTC](https://discuss.elastic.co/t/elasticsearch-v5-5-3-to-v7-17-7/382028 "2025-09-17T18:16:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gord1](https://avatars.discourse-cdn.com/v4/letter/g/e68b1a/32.png) [@Gord1](https://discuss.elastic.co/u/Gord1)\
**Post date:** [September 17, 2025, 6:16pm UTC](https://discuss.elastic.co/t/elasticsearch-v5-5-3-to-v7-17-7/382028/1 "2025-09-17T18:16:27Z")

</div>

Hello,  
I am new to Elasticsearch and need to perform an upgrade from v5.5.3 to v7.17.7.  
I want to upgrade directly from v5.5.3 to v7.17.7 in a windows cluster.  
Another team in out environment were not able to do the rolling upgrades and so upgraded directly to 7.17.7, re-indexed the DB and were successful.  
I need to take the same approach but am confused with the breaking changes and .yml file change documentation.  
Is anyone able to summarize what needs to be updated with the .yml file and any other changes?  
Any help is greatly appreciated.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [September 18, 2025, 11:45am UTC](https://discuss.elastic.co/t/elasticsearch-v5-5-3-to-v7-17-7/382028/2 "2025-09-18T11:45:35Z")

</div>

Welcome!

> [@Gord1](#):
>
> Another team in out environment were not able to do the rolling upgrades and so upgraded directly to 7.17.7, re-indexed the DB and were successful.

Yeah. I think that's the best idea when it's possible for such upgrades...

> [@Gord1](#):
>
> I am new to Elasticsearch and need to perform an upgrade from v5.5.3 to v7.17.7.

I'd directly jump to v9.1.3. 7.17.7 is not even the last bugfix version of 7.17... Which is [7.17.29](https://www.elastic.co/downloads/past-releases/elasticsearch-7-17-29).

So I'd:

- start a brand new fresh cluster with 9.1.3
- create the right mappings for your use case. Note that the mapping from 5.x can't be applied directly AFAICT
- reindex from your source database

**I DO NOT** recommend switching to 7.17.7.

If you want to simply try that and check that the process will go smoothly, you can:

- Use [cloud.elastic.co](http://cloud.elastic.co) and choose either Serverless (SaaS) or Hosted (PaaS) deployment. Serverless is much easier of course.
- Use [start-local](https://github.com/elastic/start-local) which is easy as running:

```auto
curl -fsSL https://elastic.co/start-local | sh

```

It just requires on Windows machine to install [Windows Subsystem for Linux (WSL)](https://learn.microsoft.com/en-us/windows/wsl/install) + Docker.

I hope this could help.

---

<div class="post-metadata">

**Author:** ![Gord1](https://avatars.discourse-cdn.com/v4/letter/g/e68b1a/32.png) [@Gord1](https://discuss.elastic.co/u/Gord1)\
**Post date:** [September 19, 2025, 3:04pm UTC](https://discuss.elastic.co/t/elasticsearch-v5-5-3-to-v7-17-7/382028/3 "2025-09-19T15:04:19Z")

</div>

Thanks for the insight.