# Migrating from Curator to ILM policy

**URL:** <https://discuss.elastic.co/t/migrating-from-curator-to-ilm-policy/236120>\
**Category:** Elasticsearch\
**Created:** [June 8, 2020, 5:31am UTC](https://discuss.elastic.co/t/migrating-from-curator-to-ilm-policy/236120 "2020-06-08T05:31:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![maadhav](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maadhav/32/46127_2.png) [@maadhav](https://discuss.elastic.co/u/maadhav)\
**Post date:** [June 8, 2020, 5:31am UTC](https://discuss.elastic.co/t/migrating-from-curator-to-ilm-policy/236120/1 "2020-06-08T05:31:12Z")

</div>

Hi Team

Just wonder that how do we migrate from Curator to Index Lifecycle Management policy.

We have Elastic stack configured on production with version 6.8.0. Logstash sends data to Elasticsearch to certain nodes with box\_type\_1. Currently we are using Curator to manage indices. Curator is configured as a daemon process to move indices from box\_type\_1 nodes to box\_type\_2 nodes.  
Now we want to upgrade ELK with version 7.6.2 and implement ILM policy to manage indices.

How do we migrate current indices from Curator to ILM policy and what strategy to follow ?

Regards

---

<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:** [July 6, 2020, 5:31am UTC](https://discuss.elastic.co/t/migrating-from-curator-to-ilm-policy/236120/2 "2020-07-06T05:31:23Z")

</div>

Closed on July 6, 2020, 5:31am UTC

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