# Auto Migration for Elasticsearch Indexes **URL:** \ **Category:** Elasticsearch\ **Created:** [March 5, 2019, 1:57pm UTC](https://discuss.elastic.co/t/auto-migration-for-elasticsearch-indexes/170921 "2019-03-05T13:57:07Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![patrick007](https://avatars.discourse-cdn.com/v4/letter/p/4af34b/32.png) [@patrick007](https://discuss.elastic.co/u/patrick007)\ **Post date:** [March 5, 2019, 1:57pm UTC](https://discuss.elastic.co/t/auto-migration-for-elasticsearch-indexes/170921/1 "2019-03-05T13:57:07Z")
I am new to Elasticsearch, Is there any tools or technique through which we can manage the Index automatically like the concept database schema migration /evolutions for Elasticsearch indexes. We can use Index and assign an Index Aliases and reindex it while switching to new index. Is there a process which can help to automate this process? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 5, 2019, 5:02pm UTC](https://discuss.elastic.co/t/auto-migration-for-elasticsearch-indexes/170921/2 "2019-03-05T17:02:05Z")
App search does similar things. Have a look at the SaaS version: [https://www.elastic.co/cloud/app-search-service](https://www.elastic.co/cloud/app-search-service) Or the standalone version: [https://www.elastic.co/downloads/app-search](https://www.elastic.co/downloads/app-search) ---
**Author:** ![patrick007](https://avatars.discourse-cdn.com/v4/letter/p/4af34b/32.png) [@patrick007](https://discuss.elastic.co/u/patrick007)\ **Post date:** [March 6, 2019, 6:37am UTC](https://discuss.elastic.co/t/auto-migration-for-elasticsearch-indexes/170921/3 "2019-03-06T06:37:03Z")
@dadoonet Thanks for the info regarding app-search-service. But I am searching for a solution which will help me migrate from one index to another. Example: If the is an index **animal\_v1** whose aliases is **animal** **animal\_v1** consist of following fields **name** , **weight** and this **animal\_v1** is in production. Now suppose I need to add a few more fields in **animal** like **height** So I will create a new index **animal\_v2** and perform reindexing from **animal\_v1** to **animal\_v2** and change aliases for **animal** from **animal\_v1** to **animal\_v2**. This is kind of a use case, But I am searching for a solution which will help me write migration template and help to automate the process. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 6, 2019, 7:07am UTC](https://discuss.elastic.co/t/auto-migration-for-elasticsearch-indexes/170921/4 "2019-03-06T07:07:02Z")
You have to write this yourself. ---
**Author:** ![patrick007](https://avatars.discourse-cdn.com/v4/letter/p/4af34b/32.png) [@patrick007](https://discuss.elastic.co/u/patrick007)\ **Post date:** [March 6, 2019, 7:32am UTC](https://discuss.elastic.co/t/auto-migration-for-elasticsearch-indexes/170921/5 "2019-03-06T07:32:21Z")
@dadoonet Okay Thanks we need to write it manually. I just wonder if there is some framework which will help manage this migration process. Like detect new manually written migration file, and update the elasticsearch index. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 6, 2019, 7:47am UTC](https://discuss.elastic.co/t/auto-migration-for-elasticsearch-indexes/170921/6 "2019-03-06T07:47:16Z")
Not anything I'm aware of. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 3, 2019, 7:47am UTC](https://discuss.elastic.co/t/auto-migration-for-elasticsearch-indexes/170921/7 "2019-04-03T07:47:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.