# Kibana is always migrating from .kibana to .kibana\_1 on fresh startup

**URL:** https://discuss.elastic.co/t/kibana-is-always-migrating-from-kibana-to-kibana-1-on-fresh-startup/201569
**Category:** Kibana
**Created:** [September 30, 2019, 4:58am UTC](https://discuss.elastic.co/t/kibana-is-always-migrating-from-kibana-to-kibana-1-on-fresh-startup/201569 "2019-09-30T04:58:17Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![lmqnam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lmqnam/32/53624_2.png) [@lmqnam](https://discuss.elastic.co/u/lmqnam)
#### Post date: [September 30, 2019, 4:58am UTC](https://discuss.elastic.co/t/kibana-is-always-migrating-from-kibana-to-kibana-1-on-fresh-startup/201569/1 "2019-09-30T04:58:17Z")

</div>

I'm using Kibana 6.5.4

When staring fresh Kinaba, it always migrates index.

Why does Kibana always migrate index on fresh startup? Please help to explain. Thanks in advance!

I referred similar case [https://www.elastic.co/guide/en/kibana/6.5/upgrade-migrations.html](https://www.elastic.co/guide/en/kibana/6.5/upgrade-migrations.html)  
But that case is 'Kibana is upgraded'.

```
{"type":"log","@timestamp":"2019-09-26T04:45:55Z","tags":["info","Sentinl","init_indices"],"pid":1,"message":"checking watcher_alarms-2019.09.26 index ..."}
{"type":"log","@timestamp":"2019-09-26T04:45:55Z","tags":["info","migrations"],"pid":1,"message":"Creating index .kibana_1."}
{"type":"log","@timestamp":"2019-09-26T04:45:55Z","tags":["info","migrations"],"pid":1,"message":"Pointing alias .kibana to .kibana_1."}
{"type":"log","@timestamp":"2019-09-26T04:45:55Z","tags":["info","migrations"],"pid":1,"message":"Finished in 126ms."}
```

---

<div class="post-metadata">

### Author: ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)
#### Post date: [September 30, 2019, 9:24pm UTC](https://discuss.elastic.co/t/kibana-is-always-migrating-from-kibana-to-kibana-1-on-fresh-startup/201569/2 "2019-09-30T21:24:46Z")

</div>

It's mostly part of the legacy conversion process - in this case it's probably too verbose. We transitioned from saving state in `.kibana` to saving state in a numbered kibana index that gets upgraded between versions. .kibana going forward is an alias pointing to the most recent version.

---

<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 28, 2019, 9:24pm UTC](https://discuss.elastic.co/t/kibana-is-always-migrating-from-kibana-to-kibana-1-on-fresh-startup/201569/3 "2019-10-28T21:24:46Z")

</div>

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