On this page
What HubSpot supports natively
| Route | Copies pipelines? | Notes |
|---|---|---|
| Sandbox deploy | New pipelines only | Pipeline rules, the Automate tab and deal tags aren’t included; edits to existing pipelines don’t deploy |
| Multi-account management | No | Copies automated emails, forms, segments and workflows only |
| Partner Portability (beta) | No | Copies custom objects with their properties, not pipelines |
So outside a sandbox and its own production account, a pipeline is rebuilt.
How to copy a pipeline to another account by hand
- Record the source pipeline. For each stage: label, order, win probability (deals) or open/closed state (tickets), and whether it’s closed won or closed lost.
- Record the stage settings. Required properties per stage, stage-entry automation on the Automate tab, and any deal rotation.
- Create the pipeline in the destination with the same stage order and probabilities.
- Recreate the automation. Stage-entry tasks, emails and workflows need the destination’s owners, emails and workflows.
- Update everything that points at stages. Workflows that move deals, list filters, reports and forecast settings all use stage IDs, and the destination’s IDs are new.
- Then import the deals, mapping each deal to the destination pipeline and stage.
When the destination already has a pipeline
Don’t create a second “Sales Pipeline” next to the existing one. Compare stages: if they mean the same thing, map your source stages onto the existing ones and add only the missing stages. Stage labels can match while meaning different things, so confirm with the destination’s owner. For copying the records side, see how to avoid losing data in a HubSpot-to-HubSpot migration.
Where Jetstack AI fits
Jetstack AI’s Portal reuse copies deal, ticket and custom object pipelines between any two connected portals. If the destination has a pipeline with the same label, Jetstack reuses it, creates only the missing stages and leaves existing stage settings alone; you can also map a source pipeline to a different destination pipeline. Stage automation is remapped, but deal rotation can’t be created through HubSpot’s API and must be set up by hand. 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 pipeline mapping.
Sources
- Assets eligible to be deployed to production (HubSpot Knowledge Base)
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
- Pipelines (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