On this page
What HubSpot supports natively
| Tool | What it does | Limits |
|---|---|---|
| Export pages and posts as HTML | Emails you a download of HTML files | Super Admin or Publish permission; meant for moving content to another platform |
| Export blog post data | A CSV, XLS or XLSX of post details | Data, not post bodies |
| Smart copy blog import | Reads posts from a live blog listing and post URL, maps title, author, date, body, featured image and tags | Up to 400 posts per import; HubSpot doesn’t name HubSpot blogs as a supported source, so test it |
| WordPress connect, XML import | Imports from WordPress or Squarespace | Not for HubSpot sources |
| Design Manager copy | Copies blog listing and post templates | Not the posts |
How to move a HubSpot blog to another account
- Copy the templates (blog listing and post templates, and their modules) with Design Manager’s Copy to different account.
- Create the blog in the destination with the same root URL and language, and assign the templates.
- Create the blog authors. Blog authors are separate from users, with their own names, bios and photos.
- Import the posts. Try smart copy on a handful of posts from the live blog, check the mapping, then run the rest. For a small blog, copying posts by hand gives you the most control.
- Re-upload images. Inline and featured images should live in the destination’s file manager.
- Check embedded forms and CTAs. They belong to the source account until you replace them.
- Match slugs and add redirects for anything that changes, then switch the domain.
Common mistakes
- Publish dates reset to today. Check the date mapping on every import.
- Posts without authors because the authors didn’t exist yet.
- Broken images once the source account’s files are removed.
For the rest of the site, see how to move HubSpot pages with their content.
Where Jetstack AI fits
Jetstack AI’s Portal reuse copies blogs and blog posts between connected HubSpot portals: the blog container, its templates, posts with their content, tags and SEO settings, and authors matched in the destination. It uploads featured images to the destination’s file manager and keeps each post’s state from the source: a published or scheduled post with a mapped author keeps that state, and a post whose author has no match in the destination arrives as a draft, so nothing goes live without a byline. 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 blogs reference.
Sources
- Export your content and data (HubSpot Knowledge Base)
- Import your blog from any CMS with smart copy (HubSpot Knowledge Base)
- Copy a template or theme to another HubSpot account (HubSpot Knowledge Base)
- Blog posts and blogs (Jetstack AI documentation)
Checked October 30, 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