# Upgrade to 9.x

**URL:** <https://discuss.elastic.co/t/upgrade-to-9-x/383126>\
**Category:** Elasticsearch\
**Created:** [October 31, 2025, 11:15am UTC](https://discuss.elastic.co/t/upgrade-to-9-x/383126 "2025-10-31T11:15:48Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![zen.xen](https://avatars.discourse-cdn.com/v4/letter/z/e495f1/32.png) [@zen.xen](https://discuss.elastic.co/u/zen.xen)\
**Post date:** [October 31, 2025, 11:15am UTC](https://discuss.elastic.co/t/upgrade-to-9-x/383126/1 "2025-10-31T11:15:48Z")

</div>

Hello,

I use ELK 8.8, 3-node cluster, I would like to upgrade to the newest version, is there an easy way to upgrade it?

Perhaps there are 2 ways to upgrade but I don’t know which one will be better:

a. build new cluster and transfer data,

b. CCR - cross-cluster replication

Could you help me with that?

---

<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:** [October 31, 2025, 1:15pm UTC](https://discuss.elastic.co/t/upgrade-to-9-x/383126/2 "2025-10-31T13:15:30Z")

</div>

There are (at least) 3 ways, just upgrade in place, which I believe is more common than new deployments or the CCR you mention.

Note to get to 9.x you need to upgrade via 8.19.x first, see [here](https://www.elastic.co/docs/deploy-manage/upgrade/prepare-to-upgrade)

You also need to check out the Upgrade Assistant in kibana, if you dont have a kibana instance please start one.

How and on what is your cluster installed? e.g. 3 VMs each running RHEL, 3 physical machines in my data centre running Windows, its part of a docker or k8s or …

btw, you’ve posted several times before, and welcome back!, including one thread where you had 8.7 on a 2-node cluster that you grew to 3 nodes for “HA”. If this is same cluster, you must have upgraded 8.7 –\> 8.8? 8.8 –\> 8.19.x is not intrinsically any different. 8.19.x –\> 9.x is not either, IMO. In all cases it’s really just “follow the steps in documentation”.

---

<div class="post-metadata">

**Author:** ![zen.xen](https://avatars.discourse-cdn.com/v4/letter/z/e495f1/32.png) [@zen.xen](https://discuss.elastic.co/u/zen.xen)\
**Post date:** [October 31, 2025, 1:48pm UTC](https://discuss.elastic.co/t/upgrade-to-9-x/383126/3 "2025-10-31T13:48:42Z")

</div>

Probably upgrade in place should be the best way.

It is not the same cluster, it is other one, maybe I will be more precise, I use bitnami ELK stack and I’d like to upgrade it and I don’t know how to do it. I try to find any info but … it is not easy.

---

<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:** [October 31, 2025, 1:57pm UTC](https://discuss.elastic.co/t/upgrade-to-9-x/383126/4 "2025-10-31T13:57:15Z")

</div>

> [@zen.xen](#):
>
> I use bitnami ELK stack

That sort of implies the answer, follow the Bitmani documentation? e.g. [here](https://docs.bitnami.com/aws/apps/elk/administration/upgrade/) , noting this documentation has a pretty recent update date?

But this forum possibly isn’t best place to ask for 3rd party packaging of Elastic products.

Good luck!

---

<div class="post-metadata">

**Author:** ![zen.xen](https://avatars.discourse-cdn.com/v4/letter/z/e495f1/32.png) [@zen.xen](https://discuss.elastic.co/u/zen.xen)\
**Post date:** [October 31, 2025, 2:10pm UTC](https://discuss.elastic.co/t/upgrade-to-9-x/383126/5 "2025-10-31T14:10:01Z")

</div>

thanks for link, maybe it will help me, if not CCR could be a good solution?

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [October 31, 2025, 2:20pm UTC](https://discuss.elastic.co/t/upgrade-to-9-x/383126/6 "2025-10-31T14:20:45Z")

</div>

> [@zen.xen](#):
>
> thanks for link, maybe it will help me, if not CCR could be a good solution?

Cross Cluster replication is a paid feature, you need a paid license for both clusters.

---

<div class="post-metadata">

**Author:** ![zen.xen](https://avatars.discourse-cdn.com/v4/letter/z/e495f1/32.png) [@zen.xen](https://discuss.elastic.co/u/zen.xen)\
**Post date:** [October 31, 2025, 2:21pm UTC](https://discuss.elastic.co/t/upgrade-to-9-x/383126/7 "2025-10-31T14:21:33Z")

</div>

ok, thanks
