Skip to content
Book a build

How do I avoid losing data in a HubSpot-to-HubSpot migration?

To avoid losing data in a HubSpot-to-HubSpot migration, move the configuration before the records, store each source record ID in a custom property, and import objects in dependency order with their associations. Map owners before importing. Then reconcile record counts, associations and activities against the source before you retire it. HubSpot can't merge accounts, so anything you don't export and import stays behind.

On this page

What HubSpot supports natively

HubSpot has no account-to-account migration. Its export guide says you can’t merge all data between HubSpot accounts: you export from one and import into the other.

Native toolWhat it movesLimits to plan for
ExportRecords with the properties you choose; lists of properties; content HTMLYou choose what’s in the file; anything left out is lost
ImportContacts, companies, deals, tickets, custom objects, and activities such as calls, meetings, notes, tasks and emails, with associationsAssociation labels need Professional or Enterprise; existing emails, meetings, notes and tasks can’t be updated by import
DeduplicationContacts match on email, companies on primary domainOther objects don’t dedupe unless you include a Record ID or unique-value property

How to avoid losing data in the migration

  1. Freeze structural changes in the source while you migrate.
  2. Move configuration first: properties (with identical internal names and option values), pipelines and stages, custom objects and association labels. HubSpot’s import lets you create a property for an unmatched column or skip it, but a property made in the import wizard is defined by hand and a skipped column isn’t imported, so build the real definitions first.
  3. Create users and teams in the destination so owner columns have someone to map to.
  4. Add a “source record ID” property to each object and fill it from the export. It’s your audit trail and your key for fixing associations.
  5. Import in order: companies, then contacts, then deals and tickets, then custom objects, then activities, each with its associations.
  6. Reconcile. Compare record counts per object, association counts, and a sample of records field by field.
  7. Then move automation. Turn workflows on only after the records they act on are in place, or they’ll enroll records mid-import.

What to check before you retire the source

  • Marketing contact status and subscription preferences.
  • Activities that didn’t import (they’re easy to miss in a count).
  • Attachments and files.
  • Integrations writing to the old portal.
  • Tracking code, forms and email sending domains moved to the new portal.

Keep the source account read-only for a while rather than closing it. For the full sequence, see the HubSpot portal migration checklist.

Where Jetstack AI fits

Jetstack AI doesn’t move CRM records; use the import tool or a records migration tool for those. Its Portal reuse handles the whole configuration step, copying properties (calculated properties with their formulas remapped, and supported rollup definitions created after the properties they depend on), pipelines, custom objects, lists, forms, emails and workflows with references remapped to the new portal. You can roll back a Portal reuse deployment: Jetstack shows you what will be removed first, then deletes the assets that deployment created in the destination portal. It won’t delete anything another deployment or Project still uses, and it skips assets that were changed after the deployment. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. See what Jetstack imports.

Sources

Checked October 30, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.

Copy & migrate between portals

Take a proven setup to the next portal.

Import a setup with its dependencies, map it to the destination portal and deploy it with references rewritten.

Explore Portal reuse

Copy & migrate between portals

Related questions.

How do I avoid losing data in a HubSpot-to-HubSpot migration?

To avoid losing data in a HubSpot-to-HubSpot migration, move the configuration before the records, store each source record ID in a custom property, and import objects in dependency order with their associations. Map owners before importing. Then reconcile record counts, associations and activities against the source before you retire it. HubSpot can't merge accounts, so anything you don't export and import stays behind.

Can I import activities such as calls, notes and meetings?

Yes. HubSpot's import tool accepts calls, meetings, notes, tasks and emails as well as records, with associations. It can't update existing emails, meetings, notes or tasks, so import them once, cleanly.

Will record IDs stay the same?

No. The destination assigns new IDs. Keep the source ID in a custom property so you can trace records, reconnect integrations and fix associations later.

What usually gets lost?

Things that live outside records: marketing email engagement, form submission history, page analytics, workflow enrollment history and owner assignments for users who weren't created first. Decide upfront which you need and how you'll move them.