---
title: "Move HubSpot pages with content to another account"
description: "How to move HubSpot pages with their content to another account: why template copies arrive empty, what HubSpot exports, and how to rebuild the pages."
url: "https://jetstack.ai/answers/move-hubspot-pages-with-content-to-another-account/"
---

# Can I move HubSpot pages with their content to another account?

Not natively. HubSpot can move templates, themes and modules to another account through Design Manager, but not the pages built with them, so the content doesn't follow. HubSpot's HTML export is meant for other platforms, and sandboxes don't copy CMS pages. To move HubSpot pages with content, copy the theme first, then rebuild each page, re-upload images and reconnect forms, or use a tool.

![](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

| 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

1. **Copy the theme or templates first** with Design Manager’s Copy to different account, including every module the pages use.
2. **Recreate shared pieces:** global header and footer content, HubDB tables that feed dynamic pages, and the forms and CTAs embedded on pages.
3. **Rebuild each page** on the copied template. Copy the module content, page title, slug, meta description and featured image.
4. **Re-upload images** to the destination’s file manager. Copied content still points at the source account’s file URLs.
5. **Re-embed forms and CTAs.** Embedded forms belong to the source account until you swap them for the destination’s versions.
6. **Connect the domain** and match slugs, then add redirects for any URL that changes.
7. **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](https://jetstack.ai/resources/blog/hubspot-website-migration-checklist-seo-redirects) covers it. For the blog itself, see [how to move a HubSpot blog to another account](https://jetstack.ai/answers/move-hubspot-blog-to-another-account).

## Where Jetstack AI fits

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

## Sources

- [Copy a template or theme to another HubSpot account (HubSpot Knowledge Base)](https://knowledge.hubspot.com/design-manager/copy-a-template-or-theme-to-another-hubspot-account)
- [Export your content and data (HubSpot Knowledge Base)](https://knowledge.hubspot.com/website-and-landing-pages/export-web-content-and-data)
- [Production assets eligible to copy to a sandbox (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account-management/production-assets-eligible-to-copy-to-a-sandbox)
- [Pages (Jetstack AI documentation)](https://jetstack.ai/docs/implementations/asset-types/pages)

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 move HubSpot pages with their content to another account?

Not natively. HubSpot can move templates, themes and modules to another account through Design Manager, but not the pages built with them, so the content doesn't follow. HubSpot's HTML export is meant for other platforms, and sandboxes don't copy CMS pages. To move HubSpot pages with content, copy the theme first, then rebuild each page, re-upload images and reconnect forms, or use a tool.

Do page URLs and SEO carry over?

Only if you recreate them. Set the same slugs on the same domain, copy titles and meta descriptions, and add redirects for any URL that changes.

Can I import the HTML export into another HubSpot account?

HubSpot describes the HTML export as a way to move content to another platform, not as a HubSpot-to-HubSpot import. Use it as a reference copy while you rebuild.

Does transferring a purchased theme move the pages?

No. HubSpot says a Marketplace theme transfer gives the new account access to the theme but doesn't move or recreate the pages that use it.
