# Allow setting Created Date during import (for historical data migration)

**URL:** <https://community.fibery.io/t/allow-setting-created-date-during-import-for-historical-data-migration/10760>\
**Category:** Ideas & Features\
**Created:** [April 22, 2026, 9:55am UTC](https://community.fibery.io/t/allow-setting-created-date-during-import-for-historical-data-migration/10760 "2026-04-22T09:55:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ID.000](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/id.000/32/14109_2.png) [@ID.000](https://community.fibery.io/u/ID.000)\
**Post date:** [April 22, 2026, 9:55am UTC](https://community.fibery.io/t/allow-setting-created-date-during-import-for-historical-data-migration/10760/1 "2026-04-22T09:55:38Z")

</div>

Hi Fibery team 🙂

We ran into a small issue when trying to import **historical data** from another system (or google sheets for example).

For example we have past tasks data that we would like to bring into Fibery and keep the **original creation date** for reporting and analysis.

However, since the **Created Date field is read-only** , all imported records get the **import date as their creation date** , which breaks historical sorting and analytics.

We understand the reasoning behind keeping this field read-only, but for migration scenarios this becomes quite limiting.

**Suggestion:**

Allow setting the **Created Date during import (CSV / API)**, or provide an option like:

- “Use provided value as Created Date during import”

This would make it much easier to migrate historical data correctly without needing workarounds.

Currently, the workaround is to:

- create a separate editable date field

- store the original creation date there

- and use it instead of the system field

…but this adds extra complexity for scripts if you want a new base of task to merge with previous tasks and use original creation date from Fibery.

Supporting this directly during import would make Fibery much more migration-friendly.

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [April 22, 2026, 11:58am UTC](https://community.fibery.io/t/allow-setting-created-date-during-import-for-historical-data-migration/10760/2 "2026-04-22T11:58:47Z")

</div>

Yes! I faced this issue as well. I had to create a seprate formula field “Creation Date (real)” which checks for the original creation date first, and if it doesnt exist it shows the Fibery creation date. Far from ideal, and a way to do this built in is ideal.