# Can I still jump from 7.17 to the new 8.8? **URL:** \ **Category:** Elasticsearch\ **Created:** [May 29, 2023, 7:55pm UTC](https://discuss.elastic.co/t/can-i-still-jump-from-7-17-to-the-new-8-8/334616 "2023-05-29T19:55:12Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![GenSSC](https://avatars.discourse-cdn.com/v4/letter/g/258eb7/32.png) [@GenSSC](https://discuss.elastic.co/u/GenSSC)\ **Post date:** [May 29, 2023, 7:55pm UTC](https://discuss.elastic.co/t/can-i-still-jump-from-7-17-to-the-new-8-8/334616/1 "2023-05-29T19:55:12Z")
I'm at 7.16 right now. I know I need to update to 7.17 first, but I am wondering if right after that I can go directly to 8.8? I know I could jump to 8.7 from 7.17. Just wondering if it's still the case. ---
**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:** [May 29, 2023, 8:00pm UTC](https://discuss.elastic.co/t/can-i-still-jump-from-7-17-to-the-new-8-8/334616/2 "2023-05-29T20:00:56Z")
Yes, you can. Check the [documentation](https://www.elastic.co/guide/en/elastic-stack/8.8/upgrading-elastic-stack.html#prepare-to-upgrade). You need to upgrade to the last release of `7.17` and then you can upgrade to the last release of `8.X`. ---
**Author:** ![cheiligers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheiligers/32/73114_2.png) [@cheiligers](https://discuss.elastic.co/u/cheiligers)\ **Post date:** [May 30, 2023, 7:58pm UTC](https://discuss.elastic.co/t/can-i-still-jump-from-7-17-to-the-new-8-8/334616/3 "2023-05-30T19:58:03Z")
In my opinion, a direct jump from 7.17 to 8.8.- can be risky but it is supported For Kibana 8.7 -\> 8.8 Kibana upgrade splits the main `.kibana_*` indices into several dedicated system indices and you can get failed migrations because of that. See [Kibana 8.8.0 | Kibana Guide [8.8] | Elastic](https://www.elastic.co/guide/en/kibana/current/release-notes-8.8.0.html) for more info on other changes specifically relating to Kibana. ---
**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:** [May 30, 2023, 9:31pm UTC](https://discuss.elastic.co/t/can-i-still-jump-from-7-17-to-the-new-8-8/334616/4 "2023-05-30T21:31:42Z")
> [@cheiligers](#): > > For Kibana **8.7 -\> 8.8** Kibana upgrade splits the main `.kibana_*` indices into several dedicated system indices and you can get failed migrations because of that. Just curious, Is there any github issue about it? I'm currently on `8.5.1` and waiting for `8.8.1` to upgrade (I always skip the `.0` releases) and I looked at every breaking changing between `8.5.1` and `8.8.0` and didn't find anything about it. Or you mean that Kibana 7.17 -\> 8.8? ---
**Author:** ![cheiligers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheiligers/32/73114_2.png) [@cheiligers](https://discuss.elastic.co/u/cheiligers)\ **Post date:** [May 31, 2023, 12:23am UTC](https://discuss.elastic.co/t/can-i-still-jump-from-7-17-to-the-new-8-8/334616/5 "2023-05-31T00:23:18Z")
@leandrojmp you're already on a 8.x version and shouldn't have major issues going to 8.8. I'm specifically pointing out 7.17 -\> 8.8 because it's a huge jump (in Kibana terms) and the likelihood of having migrations issues is compounded by the additional 8.7 -\> 8.7 change. ---
**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:** [May 31, 2023, 4:02am UTC](https://discuss.elastic.co/t/can-i-still-jump-from-7-17-to-the-new-8-8/334616/6 "2023-05-31T04:02:56Z")
> A direct jump from 7.17 to 8.8.- is NOT recommended for Kibana. In the [Kibana upgrade documentation](https://www.elastic.co/guide/en/kibana/current/upgrade.html), we are not saying such a thing: > To upgrade from 7.16.0 or earlier to 8.8.0, **you must first upgrade to 7.17** , which enables you to use the **Upgrade Assistant** to [prepare for the upgrade](https://www.elastic.co/guide/en/elastic-stack/8.8/upgrading-elastic-stack.html#prepare-to-upgrade). Before you upgrade, you must resolve all critical issues identified by the **Upgrade Assistant**. If it's not recommended (which I think never happened in the past and I don't think that Elastic Cloud discourages users to migrate from 7.17 to 8.8), we should update the documentation IMHO. ---
**Author:** ![GenSSC](https://avatars.discourse-cdn.com/v4/letter/g/258eb7/32.png) [@GenSSC](https://discuss.elastic.co/u/GenSSC)\ **Post date:** [May 31, 2023, 12:56pm UTC](https://discuss.elastic.co/t/can-i-still-jump-from-7-17-to-the-new-8-8/334616/7 "2023-05-31T12:56:20Z")
@dadoonet If you don't have critical issues but you have warnings, is that a deal breaker for an upgrade? ---
**Author:** ![cheiligers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheiligers/32/73114_2.png) [@cheiligers](https://discuss.elastic.co/u/cheiligers)\ **Post date:** [May 31, 2023, 3:15pm UTC](https://discuss.elastic.co/t/can-i-still-jump-from-7-17-to-the-new-8-8/334616/8 "2023-05-31T15:15:25Z")
You're 100% correct. My recommendation is my opinion, not the "official" Elastic one. We're allowed to have our own opinions, based on past experience and I'll leave it at that. ---
**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:** [May 31, 2023, 7:16pm UTC](https://discuss.elastic.co/t/can-i-still-jump-from-7-17-to-the-new-8-8/334616/9 "2023-05-31T19:16:57Z")
Well. I'd carefully look at the warnings. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 28, 2023, 7:17pm UTC](https://discuss.elastic.co/t/can-i-still-jump-from-7-17-to-the-new-8-8/334616/10 "2023-06-28T19:17:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.