# Migrate Kibana visualizations from Ver 4.6 to Ver 5.3
**URL:** https://discuss.elastic.co/t/migrate-kibana-visualizations-from-ver-4-6-to-ver-5-3/83840
**Category:** Kibana
**Created:** [April 27, 2017, 10:33am UTC](https://discuss.elastic.co/t/migrate-kibana-visualizations-from-ver-4-6-to-ver-5-3/83840 "2017-04-27T10:33:20Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@michalkm](https://discuss.elastic.co/u/michalkm)
#### Post date: [April 27, 2017, 10:33am UTC](https://discuss.elastic.co/t/migrate-kibana-visualizations-from-ver-4-6-to-ver-5-3/83840/1 "2017-04-27T10:33:20Z")
We have a kibana 4.6 with many visualizations configured and would like to move them to a **fresh** install of Kibana 5.3, so .kibana is 100% ver 5.3
When doing an export of specific visualizations in 4.6 and import in 5.3, things break. The visualizations are showing in the list of available visualizations but when clicking on one of them in order to view them, we get the following error:
Error: Could not locate that visualization (id: XXX)
at SavedObject.applyESResp ([https://localhost/portal/bundles/kibana.bundle.js?v=14823:29:23813](https://localhost/portal/bundles/kibana.bundle.js?v=14823:29:23813))
at processQueue ([https://localhost/portal/bundles/commons.bundle.js?v=14823:38:23621](https://localhost/portal/bundles/commons.bundle.js?v=14823:38:23621))
at [https://localhost/portal/bundles/commons.bundle.js?v=14823:38:23888](https://localhost/portal/bundles/commons.bundle.js?v=14823:38:23888)
at Scope.$eval ([https://localhost/portal/bundles/commons.bundle.js?v=14823:39:4619](https://localhost/portal/bundles/commons.bundle.js?v=14823:39:4619))
at Scope.$digest ([https://localhost/portal/bundles/commons.bundle.js?v=14823:39:2359](https://localhost/portal/bundles/commons.bundle.js?v=14823:39:2359))
at Scope.$apply ([https://localhost/portal/bundles/commons.bundle.js?v=14823:39:5037](https://localhost/portal/bundles/commons.bundle.js?v=14823:39:5037))
at done ([https://localhost/portal/bundles/commons.bundle.js?v=14823:37:25027](https://localhost/portal/bundles/commons.bundle.js?v=14823:37:25027))
at completeRequest ([https://localhost/portal/bundles/commons.bundle.js?v=14823:37:28702](https://localhost/portal/bundles/commons.bundle.js?v=14823:37:28702))
at XMLHttpRequest.xhr.onload ([https://localhost/portal/bundles/commons.bundle.js?v=14823:37:29634](https://localhost/portal/bundles/commons.bundle.js?v=14823:37:29634))
From a first glance, it looks like something is messed-up with the ID, something was changed in that matter between the versions.
It is not possible to recreate all of the visualizations, since we're talking about ~50 of them. We can do json changes in advance, before the actual import, but we cannot tel right now what we should change.
Any idea ?
---
### Author:  [@BigFunger](https://discuss.elastic.co/u/BigFunger)
#### Post date: [April 27, 2017, 3:33pm UTC](https://discuss.elastic.co/t/migrate-kibana-visualizations-from-ver-4-6-to-ver-5-3/83840/2 "2017-04-27T15:33:45Z")
For other folk's reference, [here's](https://github.com/elastic/kibana/issues/11441) the issue that was filed as well.
---
### Author:  [@michalkm](https://discuss.elastic.co/u/michalkm)
#### Post date: [May 1, 2017, 7:57am UTC](https://discuss.elastic.co/t/migrate-kibana-visualizations-from-ver-4-6-to-ver-5-3/83840/3 "2017-05-01T07:57:00Z")
I've upgraded to 5.3.1 and tried again. Still the same state. Check out the bug report, you can see the error logs per each visualization. It appears that Line charts migrated with no errors.
Area chart, Table and Heatmap are still broken.
Still looking for a workaround, if anyone has a suggestion. Changing the json outputs in order to make the import work are also an option, but still haven't figured out what to change.
Thanks
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 29, 2017, 8:05am UTC](https://discuss.elastic.co/t/migrate-kibana-visualizations-from-ver-4-6-to-ver-5-3/83840/4 "2017-05-29T08:05:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.