On this page
What HubSpot supports natively
| Tool | Moves pages? | What it does |
|---|---|---|
| Design Manager copy | No | Copies templates, themes and modules. HubSpot: copying a template doesn’t copy content created with it |
| HTML export | No | Exports HTML for pages, posts and templates, described as for moving content to another platform |
| Standard sandbox | No | Website pages, landing pages and blog pages aren’t copied into a sandbox |
| Marketplace theme transfer | No | Gives the new account the theme; doesn’t recreate pages |
That’s why pages look empty after a template copy: the layout arrived, the content didn’t.
How to move pages with their content to another account
- Copy the theme or templates first with Design Manager’s Copy to different account, including every module the pages use.
- Recreate shared pieces: global header and footer content, HubDB tables that feed dynamic pages, and the forms and CTAs embedded on pages.
- Rebuild each page on the copied template. Copy the module content, page title, slug, meta description and featured image.
- Re-upload images to the destination’s file manager. Copied content still points at the source account’s file URLs.
- Re-embed forms and CTAs. Embedded forms belong to the source account until you swap them for the destination’s versions.
- Connect the domain and match slugs, then add redirects for any URL that changes.
- Check every page in preview before publishing.
When it’s worth getting help
A handful of landing pages is a manual job. A full site with dynamic HubDB pages, a blog and dozens of embedded forms is where rebuilding by hand gets slow and error-prone. Plan the URL and redirect map before you start; the website migration checklist covers it. For the blog itself, see how to move a HubSpot blog to another account.
Where Jetstack AI fits
Jetstack AI’s Portal reuse copies site pages and landing pages with their content. It brings the template, modules, forms and HubDB tables they depend on, walks the drag-and-drop layout to remap form, module and HubDB references, uploads images to the destination’s file manager, and maps the source domain to one you choose. Pages arrive as drafts. 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. Pages and HubDB tables must be unpublished before they can be rolled back. See the pages reference.
Sources
- Copy a template or theme to another HubSpot account (HubSpot Knowledge Base)
- Export your content and data (HubSpot Knowledge Base)
- Production assets eligible to copy to a sandbox (HubSpot Knowledge Base)
- Pages (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