On this page
What HubSpot supports natively
Partner Portability is HubSpot’s own route for partners. It’s labeled beta, and it copies in one direction: from your partner account to a client you manage.
| Asset type | What HubSpot copies |
|---|---|
| Agents | Custom agent templates: objective, actions and input |
| Workflows | Workflows not created in Agent Hub |
| Forms | Form names and fields |
| Marketing emails | Automated marketing emails |
| Segments | Segment names and filter criteria |
| Custom objects | The object and its custom properties |
Who can use it: you need Partner Admin permissions in your partner account and in the client’s account, you can’t be listed as a contractor in your partner account, and you and the client must operate in the same region. You must also own the assets or have the rights to copy them.
Dependencies: each asset’s dependencies must copy for the asset to copy. HubSpot adds required connected assets for you, for example the marketing email a selected workflow sends, and shows them for review.
How to copy partner assets to a client account
- In your partner account, go to Client Access Manager and click Copy assets next to the client.
- Choose the asset types, then the specific assets.
- Review the connected assets HubSpot added.
- Resolve conflicts that would block the copy, such as a workflow going to a client account without access to that feature.
- Start the copy, then check View copy history for the result of each asset.
What Partner Portability doesn’t cover
These aren’t on HubSpot’s list, so plan another route:
- Pipelines and their stage automation.
- Properties on standard objects copied on their own (outside the assets that need them).
- Lists of the wider kind, reports and dashboards.
- Regular (non-automated) marketing emails.
- CMS pages, blog posts and HubDB tables. Templates, themes and modules have their own Design Manager copy.
- Anything from one client account to another.
HubSpot’s article also doesn’t say what happens when the client already has an asset with the same name, so check the client portal before copying. For the broader agency process, see how to replicate a portal configuration for agency clients.
Where Jetstack AI fits
Jetstack AI’s Portal reuse works between any two portals you connect, client to client included, and covers asset types Partner Portability doesn’t, such as pipelines, lists, regular emails, CMS assets and reports. It matches assets that already exist in the destination by name instead of duplicating them. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. 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. See how deployment works.
Sources
- Copy partner assets to client accounts (HubSpot Knowledge Base)
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
- Portal reuse deployment (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
Deliver more client work with the same team.
Audit the client portal, build the agreed work and reuse your best setups across clients.
See how partners use Jetstack