Skip to content
Get a quote

What are common challenges when migrating data into HubSpot CRM?

Short answer

The common challenges are the platform's own rules. Create date is read-only for everything except deals. Imported emails, meetings, notes and tasks can't be updated later. Association labels must exist before import and need Professional or Enterprise, and custom objects need Enterprise. Smart Transfer doesn't move custom objects, and connecting inboxes doesn't backfill old emails.

By

The challenges, and what HubSpot says

ChallengeHubSpot’s ruleWorkaround
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 correctedImport can create but not update emails, meetings, notes and tasks; calls can be updatedTest on a sample; fix by deleting the batch and importing again
Activity dates default to nowWithout Activity date, values are “set to the date and time of the import”Always map Activity date
Labelled associationsLabels must be created before import, and importing them requires Professional or EnterpriseCreate labels first; separate several labels with a semicolon
Custom objectsNeed an Enterprise subscription; Smart Transfer doesn’t transfer themCreate the schema, then import with a unique ID property
Email historyConnecting an inbox doesn’t log historical emailsImport emails as email activities
UndoDeleting import records doesn’t reverse updatesExport first; tag every batch
Workflows firingImported records can enroll in active workflowsPause 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

  1. Create users, teams, pipelines, properties and association labels.
  2. Add a source-ID property on every object.
  3. Import companies, then contacts, then deals, then tickets and custom objects, with associations.
  4. Import activities by type, with Activity date and associations.
  5. Upload files and link them.
  6. 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.

Questions, answered

A few useful answers.

What are HubSpot's import file limits?

On paid accounts: 512 MB and 1,048,576 rows per file, and 500 imports or 10 million rows per rolling 24 hours. Free tools: 20 MB per file, 50 imports and 500,000 rows a day. Files must have fewer than 1,000 columns.

Can I undo a HubSpot import?

You can delete the records an import created. HubSpot says changes made to existing records can't be reversed by deleting, so export before you import updates.

Does HubSpot dedupe on import?

Contacts match on email and companies on domain, or on Record ID. Without those, an import creates new records, so clean duplicates before you load.

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