I have also used Elasticdump and had pretty good success with it. But there's a couple of things you need to understand and account for.
- You SHOULD export the
mappingand thedatain 2 steps (see the elasticdump help) and on the new Kibana you should load themappingbefore loading thedata. The reason for this is that Kibana uses some data types that are not the default types and if you import the .kibana data (docs) before loading the mapping, things will break.
Another way around this is, on the new Kibana instance create and save one of each object type manually then the mapping would be set by Kibana and you could then just use Elasticdump to load the data.
We can see from your output that it didn't load any documents. Maybe you can show your command line?
- Using Elasticdump (or any other method that writes directly to the .kibana index) is not supported. The structure of data in the .kibana index will change (probably for 6.0) and Kibana will migrate the data in it's index. So loading 5.x saved objects directly into the 6.x .kibana index would probably fail.
There are some open issues to create officially supported APIs in Kibana for creating saved objects. Not sure when these would become available.
Thanks,
Lee