---
title: "Common challenges migrating data into HubSpot CRM"
description: "The HubSpot migration problems that come up again and again: read-only create dates, activities you can't update, association labels, custom objects."
url: "https://flitstack.ai/answers/common-challenges-migrating-data-into-hubspot"
---

# 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.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Ask us about your migration ](https://flitstack.ai/contact) [Read the full guide →](https://flitstack.ai/guides/hubspot-import)

## 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

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](https://flitstack.ai/guides/hubspot-import) or [HubSpot migrations](https://flitstack.ai/migrations/crm/hubspot).

![Aditya Kumar](https://flitstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://flitstack.ai/about/aditya-kumar)

Founder, FlitStack AI

Aditya Kumar is the founder of FlitStack AI and Jetstack AI, both built at Ambrstack. FlitStack AI migrates CRM and business data between platforms; Jetstack AI is the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about CRM data, migrations, HubSpot architecture and automation from the work of building them.

[More from Aditya](https://flitstack.ai/about/aditya-kumar) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

On this page

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.

## Related

### [What does the HubSpot importer keep, and what does it drop?](https://flitstack.ai/guides/hubspot-import)

[Read →](https://flitstack.ai/guides/hubspot-import)

### [Migrate to HubSpot](https://flitstack.ai/migrations/crm/hubspot)

[Read →](https://flitstack.ai/migrations/crm/hubspot)

### [What do HubSpot Smart Transfer and HubSpot's paid migration cover, and what don't they?](https://flitstack.ai/guides/hubspot-smart-transfer)

[Read →](https://flitstack.ai/guides/hubspot-smart-transfer)

### [CRM migration checklist: what to do before, during and after the move](https://flitstack.ai/guides/crm-migration-checklist)

[Read →](https://flitstack.ai/guides/crm-migration-checklist)

## Sources

1. [HubSpot: Set up your import file](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
2. [HubSpot: Understand the import tool](https://knowledge.hubspot.com/import-and-export/understand-the-import-tool)
3. [HubSpot: Update a property value for a record](https://knowledge.hubspot.com/records/update-a-property-value-for-a-record)
4. [HubSpot: Create and use association labels](https://knowledge.hubspot.com/object-settings/create-and-use-association-labels)
5. [HubSpot: View and analyze previous imports](https://knowledge.hubspot.com/import-and-export/view-and-analyze-previous-imports)

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](https://flitstack.ai/contact)
