---
title: "Copy a HubSpot pipeline to another portal or account"
description: "How to copy a HubSpot deal or ticket pipeline to another portal or account: the one native route, what it leaves out, and how to rebuild the rest."
url: "https://jetstack.ai/answers/copy-hubspot-pipeline-to-another-account/"
---

# Can I copy a HubSpot pipeline to another portal or account?

HubSpot only copies a pipeline to another account in one case: a new pipeline built in a standard sandbox can deploy to its production account, without pipeline rules or Automate tab settings. Multi-account management and Partner Portability don't copy pipelines. Between other accounts, recreate the pipeline, its stages, probabilities and stage automation by hand, or use a tool. Deals never share between accounts.

![](https://jetstack.ai/images/authors/aditya-kumar.webp)

By [Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/) Founder, Jetstack AI

Updated October 29, 2026

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

1. **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.
2. **Record the stage settings.** Required properties per stage, stage-entry automation on the Automate tab, and any deal rotation.
3. **Create the pipeline in the destination** with the same stage order and probabilities.
4. **Recreate the automation.** Stage-entry tasks, emails and workflows need the destination’s owners, emails and workflows.
5. **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.
6. **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](https://jetstack.ai/answers/avoid-losing-data-hubspot-to-hubspot-migration).

## Where Jetstack AI fits

Jetstack AI’s [Portal reuse](https://jetstack.ai/roll-out) 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](https://jetstack.ai/docs/implementations/deploying/pipeline-mapping).

## Sources

- [Assets eligible to be deployed to production (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account-management/assets-eligible-to-be-deployed-to-production)
- [Copy assets to another HubSpot account (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account-management/copy-assets-to-another-hubspot-account)
- [Pipelines (Jetstack AI documentation)](https://jetstack.ai/docs/implementations/asset-types/pipelines)

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

![Aditya Kumar](https://jetstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/)

Founder, Jetstack AI

Aditya Kumar is the founder of Jetstack AI, the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about HubSpot architecture, automation and AI from the work of building it.

[More from Aditya](https://jetstack.ai/authors/aditya-kumar/) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

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](https://jetstack.ai/roll-out)

On this page

Copy & migrate between portals

## Related questions.

Can I copy a HubSpot pipeline to another portal or account?

HubSpot only copies a pipeline to another account in one case: a new pipeline built in a standard sandbox can deploy to its production account, without pipeline rules or Automate tab settings. Multi-account management and Partner Portability don't copy pipelines. Between other accounts, recreate the pipeline, its stages, probabilities and stage automation by hand, or use a tool. Deals never share between accounts.

Can two HubSpot accounts share one pipeline and its deals?

No. Each account holds its own records and pipelines, and HubSpot's copy features copy definitions, not live records. To work from one pipeline, the teams need to be in one account.

How do I move the deals as well?

Create the pipeline and stages in the destination first, then export the deals and import them with pipeline and stage columns that match the destination's labels. Import associated companies and contacts in the same import or before it.

Will stage IDs match after I copy?

No. The destination assigns new pipeline and stage IDs. Any workflow, report or integration that refers to stage IDs needs updating.
