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

Ideas & Features
1

Hi Fibery team :slightly_smiling_face:

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.

2

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.