# Rejecting mapping update to \[.kibana\] as the final mapping would have more than 1 type: \[visualization, doc\]" error

**URL:** <https://discuss.elastic.co/t/rejecting-mapping-update-to-kibana-as-the-final-mapping-would-have-more-than-1-type-visualization-doc-error/133557>\
**Category:** Kibana\
**Created:** [May 28, 2018, 2:07pm UTC](https://discuss.elastic.co/t/rejecting-mapping-update-to-kibana-as-the-final-mapping-would-have-more-than-1-type-visualization-doc-error/133557 "2018-05-28T14:07:43Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\
**Post date:** [May 28, 2018, 2:42pm UTC](https://discuss.elastic.co/t/rejecting-mapping-update-to-kibana-as-the-final-mapping-would-have-more-than-1-type-visualization-doc-error/133557/8 "2018-05-28T14:42:45Z")

</div>

Hi,

yeah those saved objects cannot be pushed directly to the Elasticsearch index as you are trying. They are meant to be imported via Kibana again, which will take care of modeling the appropriate ES document for that.

There is currently an experimental (yet undocumented) API, that allows you to import those saved objects again into Kibana. You can find information about this API in this [pull request](https://github.com/elastic/kibana/pull/11632). This (or using the UI) are the only ways to import those saved objects again.

Cheers,  
Tim

---

_[View the full topic](https://discuss.elastic.co/t/rejecting-mapping-update-to-kibana-as-the-final-mapping-would-have-more-than-1-type-visualization-doc-error/133557)._