# Moving kibana visualisation to a new cluster with differently named indexes

**URL:** <https://discuss.elastic.co/t/moving-kibana-visualisation-to-a-new-cluster-with-differently-named-indexes/305114>\
**Category:** Kibana\
**Created:** [May 18, 2022, 11:26pm UTC](https://discuss.elastic.co/t/moving-kibana-visualisation-to-a-new-cluster-with-differently-named-indexes/305114 "2022-05-18T23:26:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Russell\_Fulton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/russell_fulton/32/62888_2.png) [@Russell\_Fulton](https://discuss.elastic.co/u/Russell_Fulton)\
**Post date:** [May 18, 2022, 11:26pm UTC](https://discuss.elastic.co/t/moving-kibana-visualisation-to-a-new-cluster-with-differently-named-indexes/305114/1 "2022-05-18T23:26:43Z")

</div>

I have just upgraded to 17.7.1 and I now find that I can no longer change the index pattern associated with a visualisation by exporting it, deleting the the index temporarily and importing it back it.

It used to detect that the index was missing and allow one to select another. Now the only thing it allows is to create the missing index pattern.

I am actually moving the visualisations to a new cluster which has different indexes and I expected to get prompted to enter new patterns bu instead the missing pattern was created which was not useful

---

<div class="post-metadata">

**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\
**Post date:** [May 30, 2022, 3:26am UTC](https://discuss.elastic.co/t/moving-kibana-visualisation-to-a-new-cluster-with-differently-named-indexes/305114/2 "2022-05-30T03:26:57Z")

</div>

Hello @Russell_Fulton -

You've definitely identified a functional gap in Kibana.

Use Saved object management to export the index pattern in question, edit it in a text editor (looking for the title) and reimport it, overwriting the existing index pattern.

Let me know if that works for you. There are a couple of variations that achieve the same result.

Thanks,  
Matt

---

<div class="post-metadata">

**Author:** ![Russell\_Fulton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/russell_fulton/32/62888_2.png) [@Russell\_Fulton](https://discuss.elastic.co/u/Russell_Fulton)\
**Post date:** [May 30, 2022, 5:35am UTC](https://discuss.elastic.co/t/moving-kibana-visualisation-to-a-new-cluster-with-differently-named-indexes/305114/3 "2022-05-30T05:35:32Z")

</div>

Been there and done that ; ). I was hoping for something simpler. Should i log feature request?

---

<div class="post-metadata">

**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\
**Post date:** [June 1, 2022, 3:35am UTC](https://discuss.elastic.co/t/moving-kibana-visualisation-to-a-new-cluster-with-differently-named-indexes/305114/4 "2022-06-01T03:35:35Z")

</div>

@Russell_Fulton Please do, create an issue here - [Issues · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues)

Its always helpful to have specific customer requests to point to when prioritizing work.

---

<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:** [June 29, 2022, 3:36am UTC](https://discuss.elastic.co/t/moving-kibana-visualisation-to-a-new-cluster-with-differently-named-indexes/305114/5 "2022-06-29T03:36:02Z")

</div>

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