On this page
What HubSpot supports natively
Design Manager has a Copy to different account option for templates, themes, modules and folders.
| Rule | Detail |
|---|---|
| Access | Your user must use the same email address in both accounts |
| Dependencies | Anything outside the copied folder doesn’t come along: linked CSS and JavaScript files, global groups, custom modules |
| Images | Not moved. They stay linked to the source account’s URLs |
| Content | Pages, posts and emails built with the template don’t copy |
| Theme folders | Copy the whole theme folder, not files inside it; @hubspot and @marketplace folders can’t be copied |
| Modules | A module can be copied to an account once; clone it to copy again |
| Marketplace purchases | Purchased themes and modules exist in one account at a time. Uninstall, then ask HubSpot Support to transfer them. The transfer doesn’t move pages that use the theme |
Developers can also use the HubSpot CLI: fetch the theme from one account and upload it to the other. In CLI version 8 and later these are hs cms fetch and hs cms upload.
How to copy a theme to another account
- Gather the dependencies into the theme folder. Move linked stylesheets, scripts, global partials and custom modules inside it. Relative paths travel better than absolute ones.
- In Design Manager, right-click the theme folder (or select it and open File) and choose Copy to different account.
- Pick the destination account and click Copy assets. If you get an external dependency error, something the theme uses is still outside the folder.
- Re-upload images to the destination’s file manager and update the references, or they keep loading from the source account.
- Check theme settings and global content in the destination, then build or move the pages.
Common mistakes
- Copying a child theme without its parent. The child depends on the parent theme being present.
- Expecting the pages to follow. They don’t; see how to move HubSpot pages with their content.
- Copying a purchased theme. It can’t be copied, only transferred through Support.
Where Jetstack AI fits
Jetstack AI doesn’t copy themes, so use Design Manager or the CLI for the theme itself. Its Portal reuse does copy templates, template modules and email templates, remapping module paths, includes and HubDB references, and can then copy the pages, blog posts and emails built on them. 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 templates reference.
Sources
- Copy a template or theme to another HubSpot account (HubSpot Knowledge Base)
- CMS commands, HubSpot CLI (HubSpot Developers)
- Templates (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