Skip to content
Get a quote

Can I keep the original created date when importing records into HubSpot?

Short answer

Only for deals. HubSpot says "the Create date property is read-only for all objects except deals," so contacts, companies and tickets get the import date. Keep the original in a custom date property, such as "Original create date", and use it in reports, lists and views. For activities, map Activity date to the original timestamp.

By

What HubSpot allows

ObjectCreate date on importWhat to do
DealsEditable: deal Create date “can be manually edited by users”Map the original date to Create date
ContactsRead-onlyCustom date property “Original create date”
CompaniesRead-onlySame
Tickets, custom objectsRead-onlySame
Activities (calls, emails, meetings, notes, tasks)Activity date is set on importMap Activity date, or it becomes the import time

Steps

  1. Create a date property on each object, for example “Original create date” (internal name original_create_date). Use a date picker, or datetime if you need the time.
  2. Add the source created date to every import file in one consistent format.
  3. Map it to the new property, and for deals also to Create date.
  4. Update your reports. Any report, list, view or dashboard that filters on Create date (new contacts this quarter, deal age) should use the custom property for migrated records. A common pattern is a calculated “Effective create date”: the original date if it’s filled, otherwise Create date.
  5. Document it so new admins know which date to use.

What the native tool does / where it stops

The import tool and Smart Transfer both bring the data across. Neither one can backdate contact or company creation. People in the community threads keep hoping for a hidden setting, but none exists: the property is read-only by design. The real cost isn’t the migration but the reporting afterwards. Any report built on Create date shows a huge spike on migration day. Swap those reports over to the custom property before anyone looks at them.

Where FlitStack AI fits

FlitStack AI preserves timestamps. On HubSpot, that means deals keep their Create date and other objects keep the original date in a mapped property. See the HubSpot import guide.

Questions, answered

A few useful answers.

Does Smart Transfer keep created dates?

Smart Transfer is subject to the same Create date rule. Map the source's created date to a custom property during setup if you need it.

Can a workflow copy my custom date into Create date?

No. Create date is read-only for contacts and companies, so no workflow, import or API call can overwrite it.

What about Became a lead date and similar fields?

Lifecycle date properties such as Became a lead date are set when the lifecycle stage changes. Check whether yours are editable in your portal before relying on them; many teams use custom properties for these too.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote