# History Splitter Feature Request

**URL:** <https://forum.inductiveautomation.com/t/history-splitter-feature-request/113510>\
**Category:** Ignition\
**Tags:** ignition83\
**Created:** [January 23, 2026, 12:02pm UTC](https://forum.inductiveautomation.com/t/history-splitter-feature-request/113510 "2026-01-23T12:02:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![liam1](https://avatars.discourse-cdn.com/v4/letter/l/e68b1a/32.png) [@liam1](https://forum.inductiveautomation.com/u/liam1)\
**Post date:** [January 23, 2026, 12:02pm UTC](https://forum.inductiveautomation.com/t/history-splitter-feature-request/113510/1 "2026-01-23T12:02:43Z")

</div>

Hi,

I’m not sure if this feature has already been requested, but I’d like to propose an “older-than query date” setting for the History Splitter.

The idea is to define a cutoff date that determines which historian is used for queries. Any history request that goes older than the cutoff would be served from the legacy historian (e.g., the SQL historian), while requests newer than the cutoff would be served from the new historian (e.g., Ignition Core historian).

This would make it much easier to migrate to a new historian while maintaining continuity, without needing to backfill all historical data immediately.

Example:

Query range ends before cutoff → read from legacy historian

Query range starts after cutoff → read from new historian

Query range spans the cutoff → automatically split and merge results from both historians

The current setting only sets date range size limit not a defined cut off threshold.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [January 23, 2026, 1:34pm UTC](https://forum.inductiveautomation.com/t/history-splitter-feature-request/113510/2 "2026-01-23T13:34:18Z")

</div>

This is a very good idea. If you make a proper feature request on [ideas.inductiveautomation.com](http://ideas.inductiveautomation.com), I'll vote for it.

(Put links here and there for reference.)

---

<div class="post-metadata">

**Author:** ![liam1](https://avatars.discourse-cdn.com/v4/letter/l/e68b1a/32.png) [@liam1](https://forum.inductiveautomation.com/u/liam1)\
**Post date:** [January 23, 2026, 1:56pm UTC](https://forum.inductiveautomation.com/t/history-splitter-feature-request/113510/3 "2026-01-23T13:56:03Z")

</div>

Here is the link to the feature request

> **["Query date” setting for the History Splitter | Ignition Features and Ideas |...](https://ideas.inductiveautomation.com/ignition-features-and-ideas/p/query-date-setting-for-the-history-splitter)**
>
> The idea is to define a cutoff date that determines which historian is used for queries. Any history request that goes older than the cutoff would be served