Skip to content

Export HubSpot Website Before You Cancel: What Each Keeps

Export HubSpot website content before you cancel: compare the HTML export, design manager download and a full offline ZIP, plus an exit checklist.

Website Downloader 9 min read

There are three ways to export HubSpot website content, and none of them alone gives you a complete copy of your site. HubSpot's built-in HTML export sends you your pages and blog posts as files. The design manager holds your templates, modules and theme. A crawl of the live site produces a full offline copy, with every page, stylesheet, image and font in one ZIP. Before you leave HubSpot CMS you want all three, plus your CRM data. Do the offline copy first, because once the subscription ends there is no live site left to copy from.

What does "export HubSpot website" actually get you? Three exports compared

Most guides describe only one of these methods, which is why they disagree about whether layout and images survive. They are different tools for different jobs:

HTML export (pages and blog posts)Design manager filesFull offline ZIP
What you getOne HTML file per page and postTemplates, modules, theme CSS and JSEvery reachable public page, rendered, plus its assets
Your text and contentYesNo (content lives in the pages, not the templates)Yes, as published
Layout and stylingMarkup only; stylesheets are usually still links to HubSpotSource files in HubL, HubSpot's template languageYes, CSS saved locally
ImagesUsually referenced by their HubSpot file URLs, not includedOnly images stored inside the themeSaved as files in the ZIP
Opens offline in a browserPartly, while HubSpot still serves the assetsNoYes
Old URL structureVia file names and slugsNoFolder structure mirrors the URLs

In short, the HTML export is your content archive, the design manager is your developer's reference, and the offline ZIP is the only one that still looks and works like your website when HubSpot is out of the picture.

HubSpot's built-in HTML export of pages and blog posts

HubSpot offers an export of all pages and blog posts as HTML files. HubSpot renames and moves settings from time to time, so treat the path below as a guide. HubSpot's knowledge base article on exporting content has the current menu names.

  1. In your HubSpot account, click the settings (gear) icon in the top navigation.
  2. In the settings sidebar, look in the content or website section for an option labelled along the lines of Export all pages and blog posts. Typing "export" into the settings search usually finds it.
  3. Start the export. HubSpot prepares a file in the background and emails you a download link.
  4. Download the file, unzip it and open a few pages before you do anything else.

What is inside, and what to check

You get the rendered HTML of your website pages, landing pages and blog posts. Open a few files in a text editor and look at the src and href attributes. In most exports, images, stylesheets and scripts still point to HubSpot's file hosting and CDN domains, not to local files. A page that looks fine today is often loading those assets from HubSpot in the background. Disconnect from the internet and open it again to see what is really in the file.

Also check coverage. Are your landing pages there, including ones that are not linked from the navigation? Are drafts and unpublished pages included? If something you need is missing, copy it manually from the editor while you still have access.

Where do I export the HubSpot blog separately?

Blog posts are part of the combined export above. Depending on your subscription, the blog tool in the content section may also offer its own export of posts. For a migration, the blog's RSS feed is a third route, because importers on other platforms can read it. Feeds often contain only the most recent posts, so confirm the count before you rely on one.

HubSpot design manager export: templates, modules and themes

The design manager is where HubSpot keeps the building blocks of your site: page and blog templates, custom modules, theme files, CSS and JavaScript. You can open and copy individual files there. For a complete download, developers use the HubSpot CLI. With hs fetch you can pull a theme or folder from the account to your computer, for example hs fetch my-theme ./backup/my-theme.

Keep these files, but don't expect them to work as a website:

  • Templates are written in HubL, HubSpot's templating language, which only renders on HubSpot's servers. Open a template in a browser and you will see tags and placeholders, not your pages.
  • Modules hold the structure, not the content. The text and images you typed into a module's fields are stored with each page, not in the module file.
  • Marketplace themes may come with license terms that limit using them outside HubSpot. Read them before reusing the code.

A developer rebuilding the site will find the CSS, the breakpoints and the module logic useful. That is the real value of the design manager export.

How to keep a full offline copy of the HubSpot site as a ZIP

HubSpot renders pages on its servers and sends finished HTML to the browser, so a crawler can save them faithfully. This is unlike JavaScript-only apps, where copies can come out blank (see why some JavaScript sites download empty). With Website Downloader the process takes three steps:

  1. Enter your site's address, for example https://www.example.com, on the home page.
  2. Watch the progress as it collects every subpage with its images, stylesheets, scripts, fonts and media. You can close the tab; your computer does not need to stay on.
  3. Download the ZIP and open index.html in any browser, offline.

The free plan covers up to 100 subpages without an account, and the archive is kept for one day. Most HubSpot sites with a blog are bigger than that. A one-time Single Site download (7.99 EUR) covers up to 5,000 subpages and keeps the archive for 30 days. All options are on the pricing page.

The offline copy is a normal folder: index.html, one folder per subpage that mirrors your URLs, and the css/, js/ and images/ that HubSpot used to serve.

Three HubSpot-specific things to watch:

  • Blogs on a subdomain. If the blog runs at blog.example.com instead of example.com/blog, download it as a second site.
  • Orphaned landing pages. A crawler finds pages by following links. Campaign landing pages that nothing links to are not discovered. Compare your page list with /sitemap.xml and rely on the HTML export for anything that is not linked.
  • Verify offline. Turn off Wi-Fi and click through the ZIP. If something looks wrong, this troubleshooting guide covers missing images and CSS.

Will HubSpot forms, CTAs and smart content work in an offline copy?

No. Part of what makes a HubSpot site a HubSpot site runs on HubSpot's servers, not in the page itself. Any copy captures how those parts looked, not how they worked:

  • Forms are embedded with a HubSpot script and submit to HubSpot. Offline you get an empty space or a form that sends nowhere. Write down each form's fields and follow-up logic so you can rebuild them.
  • CTAs are managed and tracked by HubSpot. Some show up as a static button in the copy, while others depend on a script and may not appear. Note every CTA's destination URL.
  • Smart content shows different versions to different visitors based on CRM data. The copy holds only the default version the crawler saw, so document the other variants by hand.
  • Memberships and gated pages sit behind a login and are not downloaded. Copy that content from the editor.
  • Site search, live chat and personalization need HubSpot running in the background.
  • HubDB tables appear in the copy as the pages they produced. Export the table data itself as a file from HubDB.
  • CRM data (contacts, companies, deals, form submissions) is not part of any website export. Export it from the CRM separately.
Pages, styles, images, fonts and PDFs work offline. Forms, search, logins and anything that talks to HubSpot's servers does not, so document those before you cancel.

Moving from HubSpot to WordPress or another CMS

Can I import the HubSpot HTML export into WordPress?

Not directly. WordPress has no importer for HubSpot's HTML export. People who migrate HubSpot to WordPress usually split the work:

  • Blog posts: import through the RSS feed with WordPress's RSS importer, or convert the export to a spreadsheet and use an import plugin. Then check images, authors and tags on a sample of posts.
  • Pages: rebuild them in the new theme, copying text and images from the offline ZIP, which shows exactly how each page looked.
  • Design: give your developer the design manager files and the offline copy's CSS as a reference.

How do I keep the old HubSpot URLs for redirects?

Broken links cost you search traffic, so build a list of every old URL before the site goes offline. Good sources are the sitemap at /sitemap.xml, the folder structure of the offline ZIP, and the redirects already set up in HubSpot's URL redirects tool (copy or export them too). Map each old URL to its new address and set up 301 redirects on the new host. Match the old blog URLs where you can. WordPress, for example, lets you set permalinks to /blog/%postname%/.

Files hosted in HubSpot's file manager, such as PDFs and images linked from emails, live at HubSpot addresses that you cannot redirect. Download them, re-upload them on the new site and update the links. For more on keeping old URLs, see archiving a website before a redesign.

Take a full copy off the old host first, then rebuild on the new one. The ZIP is your reference and your safety net while DNS and redirects change.

Checklist: what to export before cancelling HubSpot

Work through this list while the site is still live and your subscription still active:

  1. Make the full offline ZIP of the live site, and of the blog subdomain if you have one. Store it somewhere other than your downloads folder.
  2. Run the HTML export of all pages and blog posts and check that landing pages and drafts are included.
  3. Back up the design manager with hs fetch or by copying the files you need.
  4. Download your file manager assets: images, PDFs, videos, especially anything linked from emails or other sites.
  5. Export HubDB tables if you use them.
  6. Export CRM data: contacts, companies, deals and form submissions.
  7. Document forms, CTAs, smart content and workflows with screenshots and notes on fields and destinations.
  8. Save the URL list and existing redirects, then set up redirects on the new site.
  9. Move DNS from HubSpot to the new host and check that the site and its SSL certificate work there.
  10. Open every backup with HubSpot out of the picture (offline for the ZIP, in a spreadsheet for the CSVs). Only then cancel.

If you already cancelled and the site is gone, a Wayback Machine capture may still hold it. The Wayback Machine downloader can turn one into a ZIP; restores of up to 100 pages are free. For the general version of this checklist, see backing up a website before cancelling hosting.

FAQ

What happens to my website if I cancel HubSpot?

Pages hosted on HubSpot stop being served when the account closes. If you downgrade instead, you are limited to whatever the lower plan or free tools allow, so check HubSpot's current terms for your plan. Your domain stays with your registrar, but it points nowhere useful until you change the DNS. Make every copy before that date.

Does the HubSpot HTML export include templates, modules and the design?

No. It contains the rendered HTML of pages and posts, usually with stylesheets and images still linked to HubSpot. Templates, modules and theme files come from the design manager. To keep the actual look of the site, make a full offline copy as well.

Do images in the exported pages still load after the HubSpot account is cancelled?

Don't count on it. The exported HTML usually points at files in HubSpot's file manager, and whether those stay reachable after cancellation is HubSpot's decision, not yours. Keep local copies through the offline ZIP and a download of your file manager.

Are CRM contacts, form submissions and forms included in the website export?

No. Contacts and form submissions are exported separately from the CRM. Forms themselves can't be exported to another platform as working forms, so record their fields and settings and rebuild them on the new site.

  • export HubSpot website
  • HubSpot
  • website migration
  • website backup
  • CMS export