HubSpot CMS → Next.js · Updated
HubSpot CMS to Next.js Migration
A HubSpot CMS to Next.js migration uses HubSpot’s documented HTML export of pages, posts and templates plus the blog CSV export, rebuilds the site in code, and keeps HubSpot forms, tracking and CRM connected. You leave the CMS, not the marketing platform.
Who this migration is for
- Companies paying for Content Hub mainly to host a website whose templates have become hard to change.
- Marketing teams that want to keep HubSpot forms, workflows and CRM but need a faster, more flexible site.
- B2B sites that need deep resource and comparison content served as clean HTML for search and AI agents.
What HubSpot CMS lets you export
Taken from the vendor’s own documentation, linked below. We do not promise an export the platform does not provide.
Documented export
- HubSpot documents an export of "pages, blog posts, and templates" as HTML, delivered by a download link sent by email, with template files in a Styles folder.
- Blog posts can be exported as data in CSV, XLS or XLSX; the export includes all posts regardless of filters unless a filter is applied first.
- HubSpot states the blog and HTML exports are available on all products and plans; Publish permission is required.
Not exported or stops working
- Per HubSpot, report exports contain page-level data and metrics only, not full HTML content.
- Modules, themes and HubL logic come out as rendered HTML, not as reusable components; they are rebuilt.
Source: HubSpot Knowledge Base, Export web content and data. Accessed October 2026.
What we rebuild rather than import
- HubSpot forms are embedded or submitted through the Forms API so leads still land in the CRM with the same properties.
- HubSpot tracking is kept for attribution while analytics and consent are rebuilt natively.
- Design and templates. A migration is a rebuild of the presentation layer; we do not try to convert a theme or builder output into React.
- Forms, lead routing and spam protection, wired to your CRM or inbox and tested end to end.
- Structured data: one Organization node, Service and FAQ markup that mirrors the visible page, validated before launch.
- Analytics, consent and conversion events, so the first month after cutover is measurable.
Want to know what your HubSpot CMS site would keep?
The free audit inventories your URLs and traffic and tells you what a migration would have to preserve.
How rankings are preserved
HubSpot CMS-specific notes first, then the eight steps every migration follows.
- HubSpot blog URLs usually include the blog path; those are preserved or redirected one-to-one depending on the new structure.
- HubSpot-hosted file URLs (hubfs) are replaced with self-hosted assets before cutover.
- Landing pages used in live campaigns are migrated last and tested with the actual form and workflow.
- 1
Inventory every URL that exists and every URL that earns
Crawl the live site, pull the sitemap, and export the Search Console Pages and Performance reports. The union is the redirect map input; the Performance rows decide what must be preserved exactly.
- 2
Decide the new URL structure before building
Keep paths where they are sane. Change them only where the old structure was a liability, and record the change in a one-to-one map. No wildcard redirects to the homepage.
- 3
Carry metadata field by field
Titles, descriptions, canonicals, Open Graph and existing structured data are exported with the content and loaded into the new pages, then diffed against the live site.
- 4
Rebuild structured data from one identity
One Organization node with the real address, phone and founder; Service, Article and FAQ markup that mirrors the visible page; validated before launch.
- 5
Preserve internal links and images
In-body links are rewritten to the new paths rather than left to bounce through redirects. Images are self-hosted so nothing depends on the old platform staying up.
- 6
Test the redirect map against the inventory
Every old URL is requested and must return one 301 to a 200 page. Chains, loops and 404s fail the launch.
- 7
Cut over and submit
DNS switch, new sitemap submitted, IndexNow ping, and a full crawl of the new site within the first day.
- 8
Monitor index coverage for a month
Indexed versus submitted, crawl errors, redirect-reported URLs and the top earning queries are checked weekly. A migration is done when coverage matches or beats the old site, not when the new one is live.
Why coverage is the finish line: our index coverage research. How AI agents read the result: which AI crawlers visit your site.
Why businesses make this move
- You keep the HubSpot tools that earn their fee (CRM, forms, workflows) and stop paying for the ones that do not (CMS hosting).
- Server-rendered HTML. Search engines and the search-type AI agents read the page as delivered, not after a browser runs scripts.
- No plugin or app layer to patch, which removes a class of security and performance regressions.
- Content modeled as data, so the same facts feed pages, schema and llms.txt without drifting apart.
How the engagement runs
| Phase | What happens |
|---|---|
| Discovery | Goals, constraints, what the current platform does well, what it blocks. Access to analytics, Search Console and the admin. |
| Inventory | URL list, content audit, export of everything the platform allows, capture of everything it does not. |
| Content model and design | Document types and fields, page templates, components. Approval before build. |
| Build | Next.js frontend, CMS setup, content load, forms, schema, analytics and consent. |
| Redirect map and QA | Old to new URL map, automated redirect test, page-by-page content diff, accessibility and performance checks. |
| Cutover | DNS switch, sitemap and IndexNow submission, first crawl, old platform kept read-only until coverage is confirmed. |
| Monitoring | Weekly index coverage, crawl errors and query checks for a month; fixes shipped as found. |
Common questions
Do I lose HubSpot forms and tracking?
No. Forms are embedded or wired through the Forms API and the tracking script is kept, so contacts, attribution and workflows continue to work.
What does the HubSpot export include?
HubSpot documents an HTML export of pages, blog posts and templates, and a CSV, XLS or XLSX export of blog post data. Both are available on all plans and require Publish permission.
Can landing pages move too?
Yes. They are included in the HTML export and rebuilt as templates in the new site; campaign pages are migrated last so live campaigns are not interrupted.
Will my blog URLs change?
Only if you want them to. The existing paths can be kept; where a cleaner structure is chosen, each old URL gets one 301.
Related
Other migration paths
Planning a HubSpot CMS move?
Tell us the page count and what the site has to keep doing. We will come back with what can be exported, what has to be rebuilt, and a dated plan.
Book a Free Call