On this page
What HubSpot supports natively
| Route | Emails it copies | Left for you |
|---|---|---|
| Multi-account management | Automated marketing emails and their content | Non-automated emails; some settings, such as a custom subscription type, must be set in the destination |
| Partner Portability (beta) | Automated marketing emails, including ones a copied workflow sends | Non-automated emails |
| Sandbox deploy | New automated emails tied to subscriptions that exist in production; new footer addresses | Edits to existing emails, regular emails, blog/RSS emails, emails tied to brands; Settings tab values |
| Design Manager copy | Coded email templates and modules | The emails built on them |
So a regular newsletter or one-off campaign email has no native route between accounts.
How to copy a marketing email to another account
- Move the template first. Coded templates can use Design Manager’s Copy to different account. Drag-and-drop emails need their layout rebuilt.
- Set up the sending basics in the destination: subscription types, sender name and address, email footer and sending domain.
- Rebuild the content. Copy the text and modules. Re-upload images to the destination’s file manager rather than linking to the source account’s URLs.
- Check personalization tokens. Each token refers to a property by internal name; the destination needs the same properties.
- Recreate smart content and the audience. Smart rules and send lists point at lists that have new IDs in the destination.
- Reconnect automation. If a workflow sends the email, point the workflow’s send action at the new email.
- Send a test to an internal address before scheduling anything.
Common mistakes
- Missing subscription type. An email can’t send without a valid subscription type in the destination.
- Linked images. They look fine until the source account’s files are deleted.
- Copying a sequence template as an email. Sales sequences and their templates are separate asset types from marketing emails.
Where Jetstack AI fits
Jetstack AI’s Portal reuse copies regular, automated, A/B, blog and RSS emails between any two connected portals. It copies the template, uploads images to the destination’s file manager and rewrites their URLs, remaps send and exclusion lists, and creates emails as drafts. The subscription type must map to one in the destination or that email won’t deploy; if the destination has no suitable one, a Project (currently in limited release) can add it there first, with the plan and the deployment each approved by you. 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 the emails reference.
Sources
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
- Assets eligible to be deployed to production (HubSpot Knowledge Base)
- Copy a template or theme to another HubSpot account (HubSpot Knowledge Base)
- Emails (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