Skip to content
Book a build

What should a HubSpot portal migration checklist include?

A HubSpot portal migration checklist should cover six phases in order: scope and audit, configuration (properties, pipelines, objects, users), records with their associations, automation and forms, content and email, then cutover and reconciliation. Configuration goes before records so every import column maps to the right property, and workflows switch on last so they don't enroll records mid-migration.

On this page

What HubSpot supports natively

HubSpot has no portal-to-portal migration feature. You work with these:

ToolUse in a migration
Export all propertiesCompare property definitions between the two portals
Record export and importMove companies, contacts, deals, tickets, custom objects and activities with associations
Multi-account management, Partner PortabilityCopy workflows, forms, segments and automated emails between linked accounts
Design Manager copyCopy templates, themes and modules

HubSpot’s export guide confirms you can’t merge all data between accounts, so each item below is a deliberate step.

The HubSpot portal migration checklist

PhaseCheck
1. ScopeList what moves and what doesn’t; audit for unused workflows, empty properties and duplicates; name an owner for each decision; freeze structural changes in the source
2. ConfigurationProperties and groups with identical internal names and option values; pipelines and stages; custom objects; association labels; users, teams and permissions; currencies; subscription types
3. RecordsSource record ID property on every object; import companies, contacts, deals, tickets, custom objects, then activities, each with associations; reconcile counts
4. AutomationLists and segments; forms; workflows copied but left off; sequences and snippets; lead scoring
5. Content and emailTemplates, themes and modules; pages and blog posts; images re-uploaded; email templates and emails; sending domain and footer
6. CutoverIntegrations reconnected; tracking code and forms swapped on the website; domains and redirects; workflows switched on after a test record; source set read-only

How to order the work

  1. Decide before you move. Each conflicting definition (“which lifecycle rules win?”) should be settled in phase 1, not mid-import.
  2. Configuration before records. HubSpot’s import makes you map each column, create a property for it in the wizard, or skip it, and a skipped column isn’t imported. A property created mid-import is defined by hand, one at a time, so its type and options are only as right as what you type in.
  3. Records before automation. A workflow switched on early enrolls records as they arrive.
  4. Content before cutover. Site traffic should land on finished pages, with redirects ready.
  5. Reconcile, then retire. Compare counts, associations and a sample of records before closing anything.

For the records phase, see how to avoid losing data in a HubSpot-to-HubSpot migration. For workflows in detail, see the workflow migration checklist.

Where Jetstack AI fits

Jetstack AI’s Portal reuse covers much of phases 2, 4 and 5: it copies properties (including calculated properties with remapped formulas and supported rollup definitions, created in dependency order), pipelines, custom objects, lists, forms, emails, workflows and CMS assets with references remapped to the new portal. Users, teams, permissions, currencies and themes stay manual. It doesn’t move CRM records; use the import tool or a records migration tool for phase 3. 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. For checklist items Portal reuse doesn’t copy, such as subscription types, a Jetstack AI Project can build them in the new portal from a brief, with the plan and the deployment approved separately; Projects is currently in limited release. See the supported asset types and what Projects can build.

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.

What should a HubSpot portal migration checklist include?

A HubSpot portal migration checklist should cover six phases in order: scope and audit, configuration (properties, pipelines, objects, users), records with their associations, automation and forms, content and email, then cutover and reconciliation. Configuration goes before records so every import column maps to the right property, and workflows switch on last so they don't enroll records mid-migration.

What should a consultant audit before the migration?

Which assets are still used, which are broken or duplicated, which properties are empty, and which integrations write to the portal. Migrating clutter doubles the work; decide what not to move first.

How long does a portal-to-portal migration take?

It depends on record volume, the number of workflows and how much of the setup needs redesigning. Settling conflicting definitions usually takes longer than the data move itself.

Should I close the old portal straight away?

No. Keep it read-only for a period so you can check history, recover anything missed and compare reports.