Skip to content
Book a build

Can you export a HubSpot workflow and import it into another portal?

Not through the HubSpot UI. You can export a spreadsheet of workflow details or a PNG image of one workflow, but neither holds the actions, and there's no workflow import. Developers can fetch a workflow's full definition with the beta v4 workflows API and create it in another portal, after replacing every list, email, user, form and stage ID with the destination's.

On this page

What HubSpot supports natively

OptionWhat you getCan it be imported elsewhere?
Workflows table → Export viewA spreadsheet of workflow details: type, dates, creators, goal totalsNo. It has no triggers or actions
Workflow editor → File → Export as PNGAn image of one workflowNo. It’s a picture
Workflows API v4 (beta)The full definition as JSON: enrollment criteria, actions, branchesYes, through the API’s create endpoint, after you replace the IDs

There’s no workflow import in the HubSpot UI. Between linked accounts, HubSpot’s copy features (multi-account management, Partner Portability, sandbox deploy) do the move for you instead.

How to export and import a workflow with the API

  1. Fetch the definition with GET /automation/v4/flows/{flowId}. The flow ID is in the workflow editor’s URL.
  2. Strip the fields that belong to the source: HubSpot recommends removing createdAt, updatedAt and dataSources to avoid validation errors.
  3. Build an ID map. For every reference in the JSON, find the destination’s equivalent:
Reference in the definitionDestination equivalent
list_idThe matching list or segment
user_idsThe matching users or owners
content_idThe matching marketing email
Form IDs in hs_form_id filtersThe matching form
Pipeline stage valuesThe matching stage ID
Custom propertiesSame internal name, same option values
  1. Create the dependencies first, so they have destination IDs to map to.
  2. Create the workflow with the rewritten JSON. Set the type to CONTACT_FLOW for contact-based workflows and PLATFORM_FLOW for others.
  3. Review it in the editor, keep it off, and test with one record.

Common mistakes

  • Copying only the workflow. The workflow needs its lists, emails and properties in the destination before it can work.
  • Missing IDs in odd places. Custom code actions and webhook bodies can contain portal IDs or tokens the API won’t rewrite for you.
  • Treating the JSON as a backup. It’s a definition, not a restore point; enrollment history isn’t in it.

If the two portals are linked, see the native ways to copy or move a workflow first.

Where Jetstack AI fits

Jetstack AI’s Portal reuse does the export and the import as one job. It imports the full workflow definition and its dependencies into a library that stays available even if the source portal disconnects, then deploys to the destination with list, email, owner, stage and property references rewritten, leaving the workflow inactive. 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 how import works.

Sources

Checked October 29, 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.

Can you export a HubSpot workflow and import it into another portal?

Not through the HubSpot UI. You can export a spreadsheet of workflow details or a PNG image of one workflow, but neither holds the actions, and there's no workflow import. Developers can fetch a workflow's full definition with the beta v4 workflows API and create it in another portal, after replacing every list, email, user, form and stage ID with the destination's.

What does the workflow spreadsheet export include?

Details such as the workflow's type, create and update dates and who made them, plus goal totals. HubSpot says it excludes performance data, the workflow's history and data from emails used in the workflow.

Is the workflows API stable?

HubSpot labels the v4 automation API as beta and subject to change. It needs the automation scope, plus sensitive-data scopes for workflows that use sensitive data.

Can I paste the JSON straight into the other portal?

Not as is. The definition is full of source-portal IDs: list IDs, user IDs, email content IDs, form IDs and pipeline stage IDs. Each one must be swapped for the destination's ID or the workflow points at nothing.