# ILM Policy Clarification **URL:** \ **Category:** Kibana\ **Tags:** ilm-index-lifecycle-management\ **Created:** [November 5, 2022, 7:48am UTC](https://discuss.elastic.co/t/ilm-policy-clarification/318229 "2022-11-05T07:48:09Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![gbandasha](https://avatars.discourse-cdn.com/v4/letter/g/c0e974/32.png) [@gbandasha](https://discuss.elastic.co/u/gbandasha)\ **Post date:** [November 5, 2022, 7:48am UTC](https://discuss.elastic.co/t/ilm-policy-clarification/318229/1 "2022-11-05T07:48:09Z")
Hello Team, Firstly I would like to define my flow, my setup uses all three components ELK, and the data is sent from a Big Data Platform to Kafka from which logstash reads and sends it to elastic. So I planned to setup the ILM Policy at the logstash level. I have two questions 1. I am processing historical data and when I send the past 5 years' worth of data all is kept in HOT index because the @timstamp is today. How can I make it cold based on the date inside the file ? 2. Below is what I have setup at the logstash config level but I have noticed that when I send all historical months the index doesn't get rollover all stays in the HOT phase. Regards, Guru ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 7, 2022, 3:28am UTC](https://discuss.elastic.co/t/ilm-policy-clarification/318229/2 "2022-11-07T03:28:42Z")
1. Yes. The best way to do that would be to ingest the data by age, then manually migrate the indices with the older data indexing is done 2. That's probably related to point 1 above, and will depend on your policy ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 3, 2022, 11:25pm UTC](https://discuss.elastic.co/t/ilm-policy-clarification/318229/3 "2022-12-03T23:25:42Z")
---
**Author:** ![gbandasha](https://avatars.discourse-cdn.com/v4/letter/g/c0e974/32.png) [@gbandasha](https://discuss.elastic.co/u/gbandasha)\ **Post date:** [December 4, 2022, 10:37am UTC](https://discuss.elastic.co/t/ilm-policy-clarification/318229/4 "2022-12-04T10:37:54Z")
> [@warkolm](#): > > Yes. The best way to do that would be to ingest the data by age, then manually migrate the indices with the older data indexing is done So I need more clarity on when you say manually migrate the indices, do you mean first send the data into seperate indices by month and year , like transaction\_2022\_01, transaction\_2022\_02 , transaction\_2022\_03 ... and then how to manually set it to cold phase ? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 4, 2022, 9:07pm UTC](https://discuss.elastic.co/t/ilm-policy-clarification/318229/5 "2022-12-04T21:07:40Z")
> [@gbandasha](#): > > and then how to manually set it to cold phase > **[Move to lifecycle step API | Elasticsearch Guide \[8.5\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.5/ilm-move-to-step.html)** ---
**Author:** ![gbandasha](https://avatars.discourse-cdn.com/v4/letter/g/c0e974/32.png) [@gbandasha](https://discuss.elastic.co/u/gbandasha)\ **Post date:** [December 5, 2022, 10:00am UTC](https://discuss.elastic.co/t/ilm-policy-clarification/318229/6 "2022-12-05T10:00:07Z")
I will try that, thanks @warkolm ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 2, 2023, 10:01am UTC](https://discuss.elastic.co/t/ilm-policy-clarification/318229/7 "2023-01-02T10:01:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.