# ISM Policy for historical data copied from differnt source

**URL:** https://forum.opensearch.org/t/ism-policy-for-historical-data-copied-from-differnt-source/22072
**Category:** OpenSearch
**Created:** [October 24, 2024, 8:11am UTC](https://forum.opensearch.org/t/ism-policy-for-historical-data-copied-from-differnt-source/22072 "2024-10-24T08:11:34Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Deepa](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@Deepa](https://forum.opensearch.org/u/Deepa)
#### Post date: [October 24, 2024, 8:11am UTC](https://forum.opensearch.org/t/ism-policy-for-historical-data-copied-from-differnt-source/22072/1 "2024-10-24T08:11:35Z")

</div>

**Versions** (relevant - OpenSearch/Dashboard/Server OS/Browser):

2.14.0

**Describe the issue** :  
I am copying historical data from Elasticsearch to opensearch cluster. Eventhough timestamp of the source indices are old, as indices are created as of today, its not going to warm/cold state as per ISM policy.  
Inorder to do that i created separate ISM policies manually keeping allocation rule as warm

 ![image](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/4/4338fce13b2bb086229ff6b41ed0d625457d89cc.png)

But in this case , how can i move this to cold state.

ALso this was feasible as i have only 7days of data to be moved. In PROD envirinment i have more than 30days of data in GB’s to be moved. So creating multiple ISM Policies wont workout. Can help to find a solution for this.

**Configuration** :

**Relevant Logs or Screenshots** :