# MIgration to Kibana multi tenancy whilst keeping settings, visualisations etc

**URL:** <https://forum.search-guard.com/t/migration-to-kibana-multi-tenancy-whilst-keeping-settings-visualisations-etc/1692>\
**Category:** Search Guard\
**Created:** [November 7, 2019, 11:30am UTC](https://forum.search-guard.com/t/migration-to-kibana-multi-tenancy-whilst-keeping-settings-visualisations-etc/1692 "2019-11-07T11:30:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikew](https://avatars.discourse-cdn.com/v4/letter/m/7ba0ec/32.png) [@mikew](https://forum.search-guard.com/u/mikew)\
**Post date:** [November 7, 2019, 11:30am UTC](https://forum.search-guard.com/t/migration-to-kibana-multi-tenancy-whilst-keeping-settings-visualisations-etc/1692/1 "2019-11-07T11:30:46Z")

</div>

Searchguard version is 6.25.5.

I’m looking at switching from a set up where we have a Kibana instance for each team, (meaning we have an ever increasing number of Kibana servers and a team can’t use Kibana whilst their Kibana is being upgraded), to having N Kibana instances with multi-tenancy enabled, each team having their own tenancy and being able to use any Kibana instance. Such a switch is only viable if we can preserve team’s Kibana settings, visualisations, etc but I can’t find any information on how do that. Is there a guide somewhere I haven’t found or does anyone have any advice on doing it? Is it even possible? Is it maybe as simple (for some value of simple :D) as using the Elasticsearch reindexing API to copy everything from the existing Kibana indices in to the new indices that get created for tenancies?

---

<div class="post-metadata">

**Author:** ![hsaly](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/hsaly/32/21_2.png) [@hsaly](https://forum.search-guard.com/u/hsaly)\
**Post date:** [November 11, 2019, 9:19pm UTC](https://forum.search-guard.com/t/migration-to-kibana-multi-tenancy-whilst-keeping-settings-visualisations-etc/1692/2 "2019-11-11T21:19:24Z")

</div>

This would be a manual reindex process where each .kibana index of the kibana team instances need to be “copied” to the respective tenant index (with Search Guard Multitenancy every tenant has a separate .kibana index like described here [Kibana Multitenancy | Security for Elasticsearch | Search Guard](https://docs.search-guard.com/latest/kibana-multi-tenancy#multitenancy).

So i suggest to first define and create all the tenants and “copy” (via reindex) the contents of the former .kibana indices.

---

<div class="post-metadata">

**Author:** ![hsaly](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/hsaly/32/21_2.png) [@hsaly](https://forum.search-guard.com/u/hsaly)\
**Post date:** [November 11, 2019, 9:19pm UTC](https://forum.search-guard.com/t/migration-to-kibana-multi-tenancy-whilst-keeping-settings-visualisations-etc/1692/3 "2019-11-11T21:19:58Z")

</div>

@jkressin anything to add?

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/system/32/1870_2.png) [@system](https://forum.search-guard.com/u/system)\
**Post date:** [December 2, 2019, 9:20pm UTC](https://forum.search-guard.com/t/migration-to-kibana-multi-tenancy-whilst-keeping-settings-visualisations-etc/1692/4 "2019-12-02T21:20:07Z")

</div>

Closed on December 2, 2019, 9:20pm UTC

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.