On this page
What HubSpot supports natively
| Option | What you get | Can it be imported elsewhere? |
|---|---|---|
| Workflows table → Export view | A spreadsheet of workflow details: type, dates, creators, goal totals | No. It has no triggers or actions |
| Workflow editor → File → Export as PNG | An image of one workflow | No. It’s a picture |
| Workflows API v4 (beta) | The full definition as JSON: enrollment criteria, actions, branches | Yes, 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
- Fetch the definition with
GET /automation/v4/flows/{flowId}. The flow ID is in the workflow editor’s URL. - Strip the fields that belong to the source: HubSpot recommends removing
createdAt,updatedAtanddataSourcesto avoid validation errors. - Build an ID map. For every reference in the JSON, find the destination’s equivalent:
| Reference in the definition | Destination equivalent |
|---|---|
list_id | The matching list or segment |
user_ids | The matching users or owners |
content_id | The matching marketing email |
Form IDs in hs_form_id filters | The matching form |
| Pipeline stage values | The matching stage ID |
| Custom properties | Same internal name, same option values |
- Create the dependencies first, so they have destination IDs to map to.
- Create the workflow with the rewritten JSON. Set the type to
CONTACT_FLOWfor contact-based workflows andPLATFORM_FLOWfor others. - 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
- Export your content and data (HubSpot Knowledge Base)
- Workflows API, v4 (HubSpot Developers)
- Workflows (Jetstack AI documentation)
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