# Migration of ELK users

**URL:** <https://discuss.elastic.co/t/migration-of-elk-users/342647>\
**Category:** Kibana\
**Created:** [September 9, 2023, 1:55am UTC](https://discuss.elastic.co/t/migration-of-elk-users/342647 "2023-09-09T01:55:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mostafaelsayed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mostafaelsayed/32/82057_2.png) [@mostafaelsayed](https://discuss.elastic.co/u/mostafaelsayed)\
**Post date:** [September 9, 2023, 1:55am UTC](https://discuss.elastic.co/t/migration-of-elk-users/342647/1 "2023-09-09T01:55:06Z")

</div>

Hello,

Is there a secure way to migrate kibana users from one instance to another along with their passwords?

Thanks

---

<div class="post-metadata">

**Author:** ![nickpeihl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickpeihl/32/112622_2.png) [@nickpeihl](https://discuss.elastic.co/u/nickpeihl)\
**Post date:** [September 11, 2023, 6:19pm UTC](https://discuss.elastic.co/t/migration-of-elk-users/342647/2 "2023-09-11T18:19:25Z")

</div>

Hi @mostafaelsayed. I'm not aware of any one-step solutions for migrating users directly. But perhaps you can use the [`elasticsearch-users list` command](https://www.elastic.co/guide/en/elasticsearch/reference/current/users-command.html) to show each user and their role(s). You can also use the `elasticsearch-users` command to create users with roles on the new cluster. However, I don't believe you can copy over the users' passwords. They will probably need to create new passwords.

---

<div class="post-metadata">

**Author:** ![mostafaelsayed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mostafaelsayed/32/82057_2.png) [@mostafaelsayed](https://discuss.elastic.co/u/mostafaelsayed)\
**Post date:** [September 12, 2023, 8:48am UTC](https://discuss.elastic.co/t/migration-of-elk-users/342647/3 "2023-09-12T08:48:00Z")

</div>

Thanks @nickpeihl

My challenge is with the passwords mainly

So there will be no way even if I am managing the Elasticsearch cluster myself ( I am managing it in kubernetes cluster, I am not using SAAS solution)?

---

<div class="post-metadata">

**Author:** ![nickpeihl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickpeihl/32/112622_2.png) [@nickpeihl](https://discuss.elastic.co/u/nickpeihl)\
**Post date:** [September 13, 2023, 8:59pm UTC](https://discuss.elastic.co/t/migration-of-elk-users/342647/4 "2023-09-13T20:59:59Z")

</div>

Hi @mostafaelsayed. [There may be a way to accomplish this from the Elasticsearch side](https://www.elastic.co/guide/en/elasticsearch/reference/8.10/snapshots-take-snapshot.html#back-up-specific-feature-state). But we're in the Kibana category and I'm not very familiar with this aspect of Elasticsearch.

Would you mind posting your question in the [Elasticsearch category](https://discuss.elastic.co/c/elastic-stack/elasticsearch/6)?

---

<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:** [October 11, 2023, 9:00pm UTC](https://discuss.elastic.co/t/migration-of-elk-users/342647/5 "2023-10-11T21:00:38Z")

</div>

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