# How to migrate the existing json dashboards in 3.x to 4.x/5?

**URL:** <https://discuss.elastic.co/t/how-to-migrate-the-existing-json-dashboards-in-3-x-to-4-x-5/58085>\
**Category:** Kibana\
**Created:** [August 16, 2016, 3:20am UTC](https://discuss.elastic.co/t/how-to-migrate-the-existing-json-dashboards-in-3-x-to-4-x-5/58085 "2016-08-16T03:20:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![xldai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xldai/32/11388_2.png) [@xldai](https://discuss.elastic.co/u/xldai)\
**Post date:** [August 16, 2016, 3:20am UTC](https://discuss.elastic.co/t/how-to-migrate-the-existing-json-dashboards-in-3-x-to-4-x-5/58085/1 "2016-08-16T03:20:41Z")

</div>

Hello,

We have some json dashboards defined in the kibana-3.1.2/app/dashboards/, they worked fine with ElasticSearch 1.5.2, now we are testing and want to move to ElasticSearch 5/Kibana 5. My questions,

1. how to migrate these existing json dashboards?
2. I saw that kibana 5 has an embeded server, is it still possible to deploy kibana 5 into Tomcat container like kibana 3.x did?

Thanks much!  
Xldai

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 16, 2016, 3:32am UTC](https://discuss.elastic.co/t/how-to-migrate-the-existing-json-dashboards-in-3-x-to-4-x-5/58085/2 "2016-08-16T03:32:21Z")

</div>

You need to rebuild these dashboards from scratch, the underlying analysis that KB 3 used was removed in KB 4.

---

<div class="post-metadata">

**Author:** ![xldai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xldai/32/11388_2.png) [@xldai](https://discuss.elastic.co/u/xldai)\
**Post date:** [August 16, 2016, 3:38am UTC](https://discuss.elastic.co/t/how-to-migrate-the-existing-json-dashboards-in-3-x-to-4-x-5/58085/3 "2016-08-16T03:38:24Z")

</div>

Thanks Mark! and any possibility that deploy kibana 5 into Tomcat container instead of starting it standalong?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 16, 2016, 3:39am UTC](https://discuss.elastic.co/t/how-to-migrate-the-existing-json-dashboards-in-3-x-to-4-x-5/58085/4 "2016-08-16T03:39:46Z")

</div>

Why would you want to do that?  
But honestly, I don't know if you can.

---

<div class="post-metadata">

**Author:** ![xldai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xldai/32/11388_2.png) [@xldai](https://discuss.elastic.co/u/xldai)\
**Post date:** [August 16, 2016, 4:00am UTC](https://discuss.elastic.co/t/how-to-migrate-the-existing-json-dashboards-in-3-x-to-4-x-5/58085/5 "2016-08-16T04:00:19Z")

</div>

We have web applications and deployed kibana 3 also on the same Tomcat container together. just from security point of view, reuse the port of Tomcat and avoid to start a new process.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:41pm UTC](https://discuss.elastic.co/t/how-to-migrate-the-existing-json-dashboards-in-3-x-to-4-x-5/58085/6 "2017-07-06T13:41:07Z")

</div>