HubSpot CMS to Next.js migration, keeping the CRM.
Most teams leaving HubSpot CMS want to leave the website, not the CRM. Here is how the site moves to Next.js while forms, tracking and your sales data stay exactly where they are, and when you should not move at all.
What stays in HubSpot.
The website and the CRM are two decisions. Only the first one changes.
The CRM, contacts and deal pipeline. Nothing about your sales process has to move.
Forms. Submitted from the new site into HubSpot, so leads land exactly where they land today.
The tracking code, so page views and attribution keep flowing into contact timelines.
Email, workflows and sequences. They never depended on where the website is hosted.
What the migration covers.
Scoped before anything is built, fixed-quoted before you commit.
Templates rebuilt, not ported
HubSpot CMS themes are written in HubL, HubSpot’s own templating language, and do not run anywhere else. Every template is rebuilt as a React component in Next.js.
Content exported and remodelled
Pages, blog posts and HubDB tables pulled out and mapped into a real content model in a headless CMS your editors can use.
URL map and redirects
Every indexed URL kept or permanently redirected before launch, then checked against the live crawl after. This decides whether your search traffic survives.
HubSpot wired back in
Forms, tracking, chat and meeting links reconnected so marketing and sales see no gap in their data.
A cutover with no downtime
The new site can go live section by section behind a reverse proxy, with HubSpot still serving the rest until each piece is ready.
One section first, fixed-quote
The smallest sensible first step is migrating one real section end to end for a fixed quote, before anyone commits to the whole site.
How the section-by-section cutover works is in our zero-downtime migration write-up.
When to leave HubSpot CMS, and when not to.
HubSpot CMS is a good product for the team it was built for. Check whether that is still you.
Move to Next.js if
- You are paying for HubSpot CMS mainly to host the website, and the CRM is what you actually use.
- Your developers fight HubL and the theme system for every change that is not a landing page.
- The site needs things a marketing CMS is not built for: logins, app features, data from your own systems.
- Page speed or accessibility is a requirement you are currently failing.
Stay on HubSpot CMS if
- Your marketing team builds landing pages every week in HubSpot’s drag-and-drop editor and has no developer to lean on.
- You rely on smart content, built-in A/B tests or adaptive pages. Rebuilding those elsewhere costs real money.
- The site works and nobody is blocked. A migration that fixes nothing is a cost, not an upgrade.
A CMS migration in production.
Our documented CMS migration is WordPress, not HubSpot: ReelAbilities, four properties rebuilt on Next.js and Directus, operated by us since launch. The content model, URL map and editor work are the same job.
4 → 1
WordPress properties consolidated onto one Next.js codebase
4.2s → 0.8s
page load, before and at launch in 2025
15
city sites running from that single codebase
97
Lighthouse accessibility on the live homepage, Aug 2026
Frequently Asked Questions
On WordPress instead? See WordPress to Next.js migration, with our published price bands.
Tell us about your HubSpot site.
Roughly how many pages, what you use HubSpot for beyond the website, and what is actually going wrong. We will tell you whether moving is worth it, including when it is not.