What HubSpot allows
| Object | Create date on import | What to do |
|---|---|---|
| Deals | Editable: deal Create date “can be manually edited by users” | Map the original date to Create date |
| Contacts | Read-only | Custom date property “Original create date” |
| Companies | Read-only | Same |
| Tickets, custom objects | Read-only | Same |
| Activities (calls, emails, meetings, notes, tasks) | Activity date is set on import | Map Activity date, or it becomes the import time |
Steps
- 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. - Add the source created date to every import file in one consistent format.
- Map it to the new property, and for deals also to Create date.
- 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.
- 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.