If your website runs on HubSpot’s CMS, you’re probably paying for it as part of Content Hub, and at some point someone has looked at the invoice and asked whether the website really needs to live there.
It’s a fair question, and the answer for a lot of teams is that it doesn’t. The CRM is where your sales team lives, and that can stay exactly where it is. The website is a separate decision. You can move it to a faster, cheaper home and keep your HubSpot forms, meetings links, tracking and workflows running as they do today.
We’ve done this twice recently. AccountKit moved off a HubSpot CMS that was costing them $12,000 a year, without losing a single page. Easy Business is moving off HubSpot’s CMS onto a site the team edits themselves. This guide walks you through how a HubSpot CMS migration works, what it costs, and where the risks are, so you can decide whether it’s right for you.
What HubSpot’s CMS costs as of October 2026
HubSpot sells its CMS as part of Content Hub. As of October 2026, its Content Hub product page lists these starting prices, in US dollars and subject to tax:
| Edition | Starting price HubSpot lists | What HubSpot highlights |
|---|---|---|
| Free | US$0 a month | Landing pages, AI blog posts, basic SEO tips |
| Starter | US$20 a month per seat (shown at US$10 as a limited-time discount for new customers) | Removes HubSpot branding, adds website pages |
| Professional | US$500 a month, with three seats included | Brand voice, content remixing, podcasts |
| Enterprise | US$1,500 a month, with five seats included | Multiple sites, content approvals, CMS customisation |
At those starting prices, Professional comes to US$6,000 a year and Enterprise to US$18,000 a year, before extra seats or tax. HubSpot’s pricing page also says Professional and Enterprise customers are required to buy onboarding, which adds to the first year.
If you go looking yourself, you’ll find the old Content Hub pricing link now opens HubSpot’s combined pricing page for the whole platform, so the product page is the clearest place to see Content Hub’s own figures. Check your own invoice too, because what you actually pay depends on your seats and the other hubs you have.
Why teams move their website off HubSpot’s CMS
The cost stops matching the use. AccountKit’s team was paying for a content platform they only used to publish the odd post. When the website is mostly a set of pages that change a few times a month, a CMS subscription at that level is hard to justify.
Editing gets harder than it should be. At Easy Business, the website lived in three places: the marketing pages on HubSpot, the blog on its own subdomain, and the landing pages on another one. Adding a page meant working in HubSpot’s editor, and every change looked slightly different from the last.
The design is limited by the theme. On HubSpot’s CMS, your pages are built from the theme and modules a developer set up. HubSpot describes that as a strength, because marketers can update pages without a developer, but it also means anything the theme didn’t plan for needs a developer anyway.
Speed is worth measuring rather than assuming. Run your key pages through a phone speed test before you decide. Some HubSpot sites are quick and some aren’t, and the scripts and modules a site has picked up over the years usually matter more than the platform. After the move, AccountKit’s homepage scored 97 for performance and 100 for SEO on Google’s Lighthouse test on a phone.
To be fair to HubSpot, its CMS does some things well. Everything lives in one platform, so page views, form submissions and deals connect without any set-up. Your marketing team can edit pages without code, and HubSpot looks after hosting and security. The paid plans add features like personalised content. If your team builds and tests landing pages in HubSpot every week, and relies on those features, staying may be the right call.
What you keep when the website leaves HubSpot
Moving the website doesn’t mean leaving HubSpot. You can cancel Content Hub, keep your CRM and the other hubs you use, and connect the new site to them.
Your HubSpot CRM stays as it is. Contacts, deals, pipelines, emails and reports aren’t tied to where your website is hosted, so the sales team won’t notice the move.
Your HubSpot forms can be embedded on the new site. HubSpot’s guide to using forms on an external site explains that you copy each form’s embed code and paste it into your page, and submissions sync straight to your HubSpot account. If your developer would rather build the form into the site, HubSpot’s Forms API can receive the submissions instead. AccountKit’s demo form posts straight into their existing HubSpot form.
Your meetings links still work. HubSpot’s meetings widget can be embedded on an external page with the same copy-and-paste embed code.
Your tracking code carries on. HubSpot’s tracking code is added automatically to HubSpot-hosted pages, so once you leave you install it yourself. HubSpot’s tracking code guide says to paste it before the closing body tag on every page of your site. Your existing analytics history stays in HubSpot.
Your workflows keep firing. If a submission lands in the same HubSpot form as before, any workflow that starts from that form keeps running, whether it sends a follow-up email or assigns the lead to someone on the sales team.
A step-by-step HubSpot CMS migration
Step 1: Take an inventory of everything on HubSpot
Start with the sitemap, then crawl the site to catch anything the sitemap misses. List every website page, landing page, blog post, blog tag and author page, and every subdomain. Easy Business had a blog on its own subdomain and landing pages on another, and those are easy to forget.
Then check Google Search Console for the pages that actually bring in visitors. Those are the ones you protect most carefully. Our guide on redesigning without losing your Google rankings covers this step in more detail.
Step 2: Export your blog and pages
HubSpot’s guide to exporting web content explains two exports. From Website Pages, Landing Pages or Blog, the Actions menu has an option to export all pages and blog posts as HTML files, and HubSpot emails you a download link. The blog also has a separate export of blog post data as a CSV or Excel file. You need Super Admin or Publish permission for both.
Download your images from the Files tool as well, so every post moves across with its pictures. AccountKit’s 45 blog posts moved across word for word with their images, and all 66 of Easy Business’s posts came across with their tags and dates.
Step 3: Export your redirects and build a redirect map
This step is the one teams most often miss. HubSpot’s URL redirects guide says redirects set up in HubSpot only work for domains connected to and hosted in HubSpot. Once your domain points somewhere else, every redirect you created in HubSpot stops working. Export them as a CSV from Content > Domains & URLs before you switch, and rebuild them on your new host.
Then map every old URL to its new home. Keep addresses the same wherever you can, and give everything that moves a permanent redirect to its closest match. For AccountKit, 62 pages kept their address and 12 got a permanent redirect, so all 74 old URLs were accounted for. Easy Business kept almost every address and needed 30 redirects, mostly to bring the blog in from its subdomain.
Step 4: Rebuild your landing pages
Landing pages are often scattered across a HubSpot account, and some of them are still linked from old ads and emails. Decide which ones are still live, rebuild those on the new site at the same address, and redirect the rest to the closest current page.
Step 5: Re-embed your forms and meetings
Add each HubSpot form and meetings widget to its new page. Before you do, add the new site’s domain to your HubSpot settings. HubSpot says submissions from a domain that hasn’t been added are marked as spam, which is the easiest way to lose leads without noticing.
Styling is worth checking too. HubSpot’s form editor lets you style embedded forms, but the developer code that lets you style a form fully with your own CSS needs a Marketing Hub or Content Hub Professional or Enterprise subscription. If you’re dropping Content Hub and don’t have Marketing Hub Professional, plan the form design around the editor’s styling options or build the form into the site.
Step 6: Install the tracking code
Add the HubSpot tracking code to every page, usually once in the site’s shared layout so no page is missed. HubSpot warns against installing it twice on the same page, and notes that ad blockers can interfere with it. After it’s installed, add the new site’s domain to your reports settings so its traffic appears in your HubSpot analytics.
On AccountKit, the HubSpot scripts wait until someone interacts with the page before they load, so they don’t slow down the first screen.
Step 7: Test lead flow into the CRM
Before you switch, submit every form on the new site with a test contact and check that each one arrives in HubSpot as the right form, with the right fields and source, and that the workflows you expect fire. Book a test meeting through each meetings link. This is the step that tells you whether the sales team will notice the move.
Step 8: Switch DNS
When everything has passed, point your domain at the new host. If your sales team sends HubSpot quotes hosted on your main domain, check those first, because HubSpot says published quotes can’t be redirected to another domain.
On the day, test a sample of old URLs, including the redirects, submit the new sitemap in Search Console and request indexing for your most important pages. After AccountKit’s move, we checked 92 URLs against the live site, including every redirect.
Step 9: Monitor, then cancel Content Hub
Watch Search Console for new “not found” errors, compare clicks on your key pages with the weeks before, and keep an eye on form submissions in HubSpot. Once the new site has settled and leads are arriving as they should, cancel Content Hub. Check your renewal date with HubSpot first so you’re not paying for another term you won’t use, and confirm what your remaining subscriptions still include.
What it costs to move off HubSpot’s CMS
There are two sides to the sum. On the HubSpot side, the Content Hub subscription goes, while your CRM and any other hubs stay on whatever you pay for them now. On the website side, you pay for the build once and then for hosting and changes.
With us, a HubSpot CMS migration is a fixed-price build. Our packages are Essential at A$7,500 for up to 5 pages, Studio at A$12,500 for up to 12 pages, and Full build at A$19,500 for up to 20 pages Migrating off a CMS is included in Studio and Full build, and Full build is the one made for a full content migration. Every package includes redirects from your old site, on-page SEO and enquiry forms tested end to end into your CRM. After launch, Care covers hosting, support and your changes from A$250 a month, with a 12-month minimum and then month to month. Your site is live for review on Day 7, or we refund the build in full. You can read how we handle the move itself on our website migration page.
Whether that’s cheaper than staying depends on what you pay HubSpot now, so put your own Content Hub invoice next to it. For AccountKit, the move took $12,000 a year off their costs.
Frequently asked questions
Can I keep HubSpot as my CRM if I move my website off its CMS?
Yes. Your CRM isn’t tied to where your website is hosted. You cancel Content Hub, keep the hubs you use, and connect the new site with embedded forms, meetings links and the tracking code. AccountKit’s sales team still runs on HubSpot, with the demo form posting into their existing HubSpot form.
Will my HubSpot forms work on a site that isn’t hosted on HubSpot?
Yes. HubSpot forms can be embedded on any external page, and submissions sync to your HubSpot account as before. Add the new domain to your HubSpot settings first, or HubSpot will mark the submissions as spam.
Will I lose my Google rankings in a HubSpot CMS migration?
Not if every old URL keeps its address or gets a permanent redirect, and titles and content carry across. Expect some movement while Google recrawls the site. The biggest HubSpot-specific risk is the redirects you set up inside HubSpot, which stop working once the domain leaves, so export and rebuild them.
Can I export my blog from HubSpot?
Yes. HubSpot lets you export all pages and blog posts as HTML files, and export blog post data as a CSV or Excel file. You need Super Admin or Publish permission, and HubSpot emails you a download link when the export is ready.
How long does it take to move off HubSpot’s CMS?
With us, your new site is live for review seven days after your build starts, followed by two rounds of changes, each turned around in two business days, and then the switch-over. AccountKit’s rebuild and move took seven build days. Leave a few weeks of monitoring before you cancel Content Hub.
What are the alternatives to HubSpot’s CMS?
The common ones are Webflow, WordPress and a site built in code. Webflow and WordPress give your team an editor to work in. A coded site, like the ones we build on Astro, is usually the fastest and cheapest to run, and the content lives in plain files rather than a platform. All of them can carry HubSpot forms and the tracking code, so the right choice depends on how your team wants to make changes.
