# Historian pruning customization to move data instead of drop them

**URL:** <https://forum.inductiveautomation.com/t/historian-pruning-customization-to-move-data-instead-of-drop-them/75588>\
**Category:** Ignition\
**Tags:** database, datascience\
**Created:** [June 27, 2023, 2:51pm UTC](https://forum.inductiveautomation.com/t/historian-pruning-customization-to-move-data-instead-of-drop-them/75588 "2023-06-27T14:51:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Martial\_Wilbert](https://avatars.discourse-cdn.com/v4/letter/m/3ab097/32.png) [@Martial\_Wilbert](https://forum.inductiveautomation.com/u/Martial_Wilbert)\
**Post date:** [June 27, 2023, 2:51pm UTC](https://forum.inductiveautomation.com/t/historian-pruning-customization-to-move-data-instead-of-drop-them/75588/1 "2023-06-27T14:51:54Z")

</div>

Hi,  
A customer would like to keep only 2 years of data on historian and pushing older data on a "Cold" storage infrastructure.  
Purpose of this "Cold" storage is in case of using Machine Learning one day, that would need data as much as possible.

Keeping only 2 years of data is purpose of pruning but this will drop all partitions. Can we customize the pruning process to copy before drop them ?

Thanks

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 27, 2023, 4:41pm UTC](https://forum.inductiveautomation.com/t/historian-pruning-customization-to-move-data-instead-of-drop-them/75588/2 "2023-06-27T16:41:34Z")

</div>

> [@Martial\_Wilbert](#):
>
> Can we customize the pruning process to copy before drop them ?

No. Push this storage logic to your DB or some external application.

---

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [June 27, 2023, 9:42pm UTC](https://forum.inductiveautomation.com/t/historian-pruning-customization-to-move-data-instead-of-drop-them/75588/3 "2023-06-27T21:42:18Z")

</div>

There is such a thing as a tag history splitter, that would allow you to simultaneously have a redundant database with different pruning and partition settings.