# Kibana 6.8 to 7.3 fails: \[uiStateJSON\] within \[dashboard\] is not allowed

**URL:** <https://discuss.elastic.co/t/kibana-6-8-to-7-3-fails-uistatejson-within-dashboard-is-not-allowed/196312>\
**Category:** Kibana\
**Created:** [August 22, 2019, 11:58am UTC](https://discuss.elastic.co/t/kibana-6-8-to-7-3-fails-uistatejson-within-dashboard-is-not-allowed/196312 "2019-08-22T11:58:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![cawoodm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cawoodm/32/14083_2.png) [@cawoodm](https://discuss.elastic.co/u/cawoodm)\
**Post date:** [August 22, 2019, 12:52pm UTC](https://discuss.elastic.co/t/kibana-6-8-to-7-3-fails-uistatejson-within-dashboard-is-not-allowed/196312/2 "2019-08-22T12:52:20Z")

</div>

Solution was to:

- run the old Kibana and
- export all dashboards from Management -\> Saved Objects.
- Edit this JSON file and remove all `uiStateJSON` elements from the JSON.
- Save and re-upload the JSON with overwrite

Now you can stop kibana and upgrade.

Note: if an upgrade failed you may have a kibana\_N index where N is higher than your current `.kibana` alias. This index can be deleted.

Example:  
GET /\_cat/aliases/_kib_ -\> Reveals kibana is using the .kibana\_8  
However, the failed migration created a .kibana\_9 index which can be deleted.

---

_[View the full topic](https://discuss.elastic.co/t/kibana-6-8-to-7-3-fails-uistatejson-within-dashboard-is-not-allowed/196312)._