The challenges, and what HubSpot says
| Challenge | HubSpot’s rule | Workaround |
|---|---|---|
| Created dates reset | ”The Create date property is read-only for all objects except deals.” | Store the original date in a custom property and report on that |
| Activities can’t be corrected | Import can create but not update emails, meetings, notes and tasks; calls can be updated | Test on a sample; fix by deleting the batch and importing again |
| Activity dates default to now | Without Activity date, values are “set to the date and time of the import” | Always map Activity date |
| Labelled associations | Labels must be created before import, and importing them requires Professional or Enterprise | Create labels first; separate several labels with a semicolon |
| Custom objects | Need an Enterprise subscription; Smart Transfer doesn’t transfer them | Create the schema, then import with a unique ID property |
| Email history | Connecting an inbox doesn’t log historical emails | Import emails as email activities |
| Undo | Deleting import records doesn’t reverse updates | Export first; tag every batch |
| Workflows firing | Imported records can enroll in active workflows | Pause the relevant workflows or add an exclusion property |
What the native tools do / where they stop
HubSpot gives you three native routes: the import tool (files), Smart Transfer (13 supported apps, one-time, one-way) and the APIs. Each one handles records well. None of them checks the whole picture, meaning that every deal arrived with its company, every note with its contact, and every owner resolved. Most of the “it didn’t migrate properly” threads come down to that missing check, not to a failed import.
Order of operations that avoids most of it
- Create users, teams, pipelines, properties and association labels.
- Add a source-ID property on every object.
- Import companies, then contacts, then deals, then tickets and custom objects, with associations.
- Import activities by type, with Activity date and associations.
- Upload files and link them.
- Reconcile counts and associations, then switch workflows back on.
Where FlitStack AI fits
FlitStack AI handles HubSpot’s rules for you: original dates kept in properties, activities checked on a sample before the full load, association labels created first, and one-click rollback. See the HubSpot import guide or HubSpot migrations.