# Announcing New Names for Internal Historians in 8.3

**URL:** <https://forum.inductiveautomation.com/t/announcing-new-names-for-internal-historians-in-8-3/110131>\
**Category:** Ignition 8.3 Early Access\
**Created:** [August 23, 2025, 1:10am UTC](https://forum.inductiveautomation.com/t/announcing-new-names-for-internal-historians-in-8-3/110131 "2025-08-23T01:10:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kurt.Larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kurt.larson/32/6426_2.png) [@Kurt.Larson](https://forum.inductiveautomation.com/u/Kurt.Larson)\
**Post date:** [August 23, 2025, 1:10am UTC](https://forum.inductiveautomation.com/t/announcing-new-names-for-internal-historians-in-8-3/110131/1 "2025-08-23T01:10:57Z")

</div>

Hi Community,

We want to inform all users of a naming change for the `Internal Historians`, effective in the upcoming Ignition 8.3 Release Candidate. This change was implemented to more accurately reflect the intended role and function of each provider.

The following historians have been renamed:

- `Internal Historian - QuestDB` is now named **Core Historian**. This is our primary, high-performance historian, originally introduced as the `Power Historian`.

- `Internal Historian - SQLite` is now named **Internal Historian (Legacy)**. This provider is maintained for backward compatibility.

Please be advised that we are urgently updating all public documentation and product information to reflect this change.

**Action Required for 8.3 Beta Participants**

Users on the 8.3 Beta who have configured either of these historian types must perform a manual update. The critical requirement is that these changes must be made **while the Gateway is shut down**. This can be done at one of two times:

- **Before** running the upgrade (while the original Gateway is shut down).
- **After** the upgrade is complete, but before the new Gateway is started for the first time.

Failure to complete these steps while the Gateway is offline will result in existing historian providers becoming non-functional upon startup.

**1. Update the Resource Configuration File**

The `type` value within the historian's `config.json` file must be changed to reflect the new naming.

- **File Path:** `/data/config/resources/core/com.inductiveautomation.historian/historian-provider/{historian_name}/config.json`

- **For Internal Historian - QuestDB:** Update the `type` value to `CoreHistorian`.

```python
{
  "profile": {
    "type": "CoreHistorian"
  }

```

- **For Internal Historian - SQLite:** Update the `type` value to `InternalHistorian`.

```python
{
  "profile": {
    "type": "InternalHistorian"
  }

```

**2. Rename the Data Directory**

The directory containing the historian's database files must be renamed to match the new type.

- **Directory Path:** `/data/var/com.inductiveautomation.historian/`

- **For Internal Historian - QuestDB:** Rename the directory `questdbhistorian` to `corehistorian`.

- **For Internal Historian - SQLite:** Rename the directory `sqlitehistorian` to `internalhistorian`.

Completing these two steps will ensure your existing data and configurations are loaded correctly under the new naming convention.

**A Note for Ignition 8.1 Users**

Users upgrading directly from Ignition 8.1 will not need any manual intervention for the Internal Historian. The upgrade process will handle the migration automatically.