# Help create ILM policy **URL:** \ **Category:** Kibana\ **Tags:** ilm-index-lifecycle-management\ **Created:** [April 21, 2022, 6:49am UTC](https://discuss.elastic.co/t/help-create-ilm-policy/302876 "2022-04-21T06:49:09Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![vladislav](https://avatars.discourse-cdn.com/v4/letter/v/bbce88/32.png) [@vladislav](https://discuss.elastic.co/u/vladislav)\ **Post date:** [April 21, 2022, 6:49am UTC](https://discuss.elastic.co/t/help-create-ilm-policy/302876/1 "2022-04-21T06:49:09Z")
Good day! Please advice! I have a couple of indices - `filebeat-current` and `filebeat-old` I need to create ILM policy, which will copy data that is more than 7 days old from `filebeat-current` to `filebeat-old`. New incoming data should always continue to be written to the index `filebeat-current`. The index names should not change. Is it even possible? ---
**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:** [April 26, 2022, 1:34am UTC](https://discuss.elastic.co/t/help-create-ilm-policy/302876/2 "2022-04-26T01:34:41Z")
> [@vladislav](#): > > I need to create ILM policy, which will copy data that is more than 7 days old from `filebeat-current` to `filebeat-old` . ILM will not copy data between indices like that. You could use ILM to use aliases called `filebeat-current` and `filebeat-old`, and then move the underlying indices between those. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 24, 2022, 1:34am UTC](https://discuss.elastic.co/t/help-create-ilm-policy/302876/3 "2022-05-24T01:34:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.