# ES 5.4 =\> 6.0 Upgrade. Watcher Issues

**URL:** https://discuss.elastic.co/t/es-5-4-6-0-upgrade-watcher-issues/108481
**Category:** Elasticsearch
**Created:** [November 21, 2017, 1:07am UTC](https://discuss.elastic.co/t/es-5-4-6-0-upgrade-watcher-issues/108481 "2017-11-21T01:07:05Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)
#### Post date: [November 24, 2017, 11:47am UTC](https://discuss.elastic.co/t/es-5-4-6-0-upgrade-watcher-issues/108481/2 "2017-11-24T11:47:37Z")

</div>

Hello,

You should have gone through 5.6 before upgrading to 6.0, at least for Kibana.  
There is an upgrade assistant in 5.6 that will run the upgrade API for you on all indices and also mention the breaking changes between the versions.  
You can still run it now, by connecting a 5.6 Kibana to your current 6.0 cluster and running the upgrade assistant for there, just to fix your watcher problem.  
You can find the guide here and assistant is in the Management page of Kibana:  
[https://www.elastic.co/guide/en/kibana/6.0/xpack-upgrade-assistant.html](https://www.elastic.co/guide/en/kibana/6.0/xpack-upgrade-assistant.html)

---

_[View the full topic](https://discuss.elastic.co/t/es-5-4-6-0-upgrade-watcher-issues/108481)._
