HubSpot CMS to Webflow Migration, Avoid Costly Mistakes
Migrating from HubSpot CMS to Webflow? Learn the content modelling gaps, blog restructuring steps, CRM integration pitfalls, and redirect plan most teams get wrong.
Most teams migrating from HubSpot CMS to Webflow focus on visual design. They pick a template, rebuild a few pages, and assume the rest will follow. Then they discover that half their blog taxonomy has vanished, their forms no longer push data into lifecycle stages, and Google is serving 404s for URLs that once drove 40% of organic traffic. The migration from HubSpot to Webflow is not primarily a design project. It is a content modelling, integration, and information architecture project with a design layer on top.
Get a technical migration audit before you lose rankings or lead data.
HubSpot and Webflow Model Content Differently. That Changes Everything.
HubSpot CMS uses what it calls “HubDB” tables and custom modules inside a template system that is tightly coupled to the HubSpot CRM. Content types (blog posts, landing pages, site pages) are predefined categories with distinct editorial workflows, analytics dashboards, and URL conventions baked in. You do not choose how a blog post relates to a landing page. HubSpot decides that for you.
Webflow uses a CMS Collection model. Collections are flexible: you define the fields, the reference relationships, and the slug structure. This flexibility is the reason teams move to Webflow. It is also the reason migrations break.
The mismatch surfaces in three places:
- Blog taxonomy: HubSpot blogs have tags and a single “topic” taxonomy. Webflow has no built-in blog feature at all. You build it from a CMS Collection. If your HubSpot blog uses multi-author attribution, topic clusters, or related-post logic, you need to recreate each of those as reference fields and multi-reference fields in Webflow Collections.
- Landing pages with smart content: HubSpot lets you swap content blocks based on CRM list membership. Webflow has no native equivalent. Any personalisation logic needs to move to a third-party tool like Mutiny, Intellimize, or a custom script layer.
- Global content and modules: HubSpot’s global modules (header, footer, CTA banners) update everywhere at once. Webflow offers symbols and components, but the inheritance model differs. Nested symbol overrides behave in ways that surprise teams accustomed to HubSpot’s module approach.
Before you export a single page, map every HubSpot content type to a Webflow Collection. Define the fields, the reference relationships, and the slug pattern. This is the step that determines whether the migration takes six weeks or six months. Our guide on CMS replatform planning covers the broader project structure, but the content modelling work is where HubSpot-to-Webflow migrations specifically go sideways.
Blog Restructuring: More Than a Copy-Paste Job
HubSpot’s blog engine handles several things silently: auto-generated listing pages for each topic, pagination, canonical URLs, author archive pages, and RSS feeds. When you move to Webflow, you are responsible for all of them.
Start with the URL structure. HubSpot defaults to /blog/post-slug or /knowledge/post-slug depending on your configuration. Webflow Collections generate URLs based on Collection slug settings. If your HubSpot blog lived at /blog/ and your Webflow Collection slug is “posts,” you will get /posts/post-slug unless you explicitly configure otherwise. Every URL that changes without a redirect is a ranking you forfeit.
The most common blog migration mistake is not mismatched slugs. It is forgetting that HubSpot auto-generates topic listing pages (like /blog/topic/seo) that accumulate backlinks and rankings. These do not exist in Webflow unless you build filtered Collection pages or static pages to replace them.
Rich content elements deserve special attention. HubSpot blog posts often contain embedded CTAs, forms, video modules, and “smart” content blocks. Webflow’s rich text field supports basic formatting, embedded images, and videos, but not interactive components inside the rich text block. You will need to use Webflow’s “nested Collection” approach or place components outside the rich text field and control layout with conditional visibility. The comparison of CMS platform trade-offs explains where Webflow’s content flexibility ends.
Audit every HubSpot blog URL with traffic:
Export from Google Search Console or Ahrefs. Flag every URL that received at least one click in the past 12 months.
Map HubSpot topics to Webflow Collection categories:
Create a multi-reference field for topics. Build a filtered Collection list page for each topic that replicates the old listing URL.
Recreate author pages:
If author archive pages drive traffic, build an "Authors" Collection in Webflow and reference it from your blog posts Collection. Link the author page to a filtered list.
Rebuild RSS:
Webflow auto-generates an RSS feed per Collection, but the feed URL will differ from HubSpot’s. Update any feed subscribers, email digest tools, or syndication partners.
Handle pagination:
Webflow’s Collection list pagination uses a different URL pattern than HubSpot’s. If Google has indexed paginated URLs (page/2, page/3), you need redirects or a clear crawl strategy.
Form and CRM Integration Gaps
This is where the migration gets politically complicated, not just technically.
HubSpot CMS forms are native to the HubSpot CRM. A form submission automatically creates or updates a contact record, assigns lifecycle stages, triggers workflows, and attributes the conversion to a campaign. None of that is free when you leave HubSpot CMS.
Webflow has its own form handling, but it is a simple notification layer. Form data goes to Webflow’s dashboard or an email. It does not go to HubSpot’s CRM unless you build a connector. Your options:
- HubSpot embed code: You can embed HubSpot forms on Webflow pages using HubSpot’s JavaScript embed snippet. This preserves CRM integration, workflows, and tracking. The trade-off: the form styling is controlled by HubSpot’s CSS, which may clash with your Webflow design system. You also inherit HubSpot’s script weight.
- Zapier or Make (Integromat): Route Webflow native form submissions to HubSpot via an automation layer. This works for simple contact creation but struggles with progressive profiling, dependent fields, and multi-step forms. Latency can also be an issue: a Zapier trigger on a free plan runs every 15 minutes, not instantly.
- HubSpot API direct integration: The cleanest long-term solution. Use Webflow’s form submission webhook or a lightweight serverless function to POST contact data to HubSpot’s Contacts API. This preserves full CRM field mapping and lets you trigger workflows. It requires engineering effort.
The hidden cost is attribution. HubSpot CMS automatically tracks a visitor’s page views, form interactions, and email clicks in one timeline. When the form lives on Webflow, that timeline breaks unless you install HubSpot’s tracking script on Webflow and ensure cookie domains align. Test this in staging, not production.
If your sales team relies on HubSpot contact timelines to qualify leads, moving forms off HubSpot CMS without preserving tracking will surface as a pipeline problem weeks after launch. Verify attribution end-to-end before go-live.
The Redirect Plan Most Teams Underestimate
Every CMS migration needs a redirect map. But HubSpot-to-Webflow migrations produce more redirect complexity than most teams budget for.
HubSpot generates URLs you may not know about. Beyond your published pages and blog posts, there are system pages: the subscription preferences page, the email unsubscribe page, the blog subscription confirmation page, and any “thank you” pages created as part of workflows. There are also landing page URLs, which HubSpot sometimes nests under /lp/ or a custom path. And there are file URLs for PDFs, images, and other assets hosted on HubSpot’s CDN at *.hubspotusercontent.com or *.hsforms.com.
The file URLs are particularly treacherous. If other sites link to a PDF you hosted on HubSpot’s CDN, those backlinks point to a domain you do not control and cannot redirect from. You need to re-upload assets to Webflow (or a CDN you own) and then request link updates where possible, or accept the lost equity.
Our CMS migration SEO guide details the redirect methodology in more depth, including how to handle parameter-based URLs and localized content paths.
Crawl the HubSpot site completely:
Use Screaming Frog or Sitebulb. Include subdomains and CDN URLs. Export every URL that returns a 200 status.
Cross-reference with analytics:
Merge the crawl with Google Analytics and Search Console data. Prioritise redirects for pages with traffic, backlinks, or conversions. Pages with zero signals in the past 18 months can often be dropped.
Build the redirect map in Webflow:
Webflow supports 301 redirects in its hosting dashboard, but there is a practical limit. For sites with thousands of blog posts and landing pages, managing redirects inside Webflow becomes unwieldy. Consider a reverse proxy layer (Cloudflare Workers, Netlify edge functions) if your redirect list exceeds a few hundred entries.
Test before DNS cutover:
Preview the Webflow staging site, then spot-check the redirect map by manually verifying the 50 highest-traffic old URLs. Confirm each returns a 301 to the correct new URL, not a 302, not a redirect chain, and not a 404.
Monitor for 30 days post-launch:
Watch Search Console’s coverage report daily for the first two weeks. Any spike in "Not found (404)" errors means the redirect map has gaps. Fix them within 48 hours.
What Gets Missed Until It Hurts
A few less obvious items that teams consistently discover too late:
Membership and gated content. HubSpot CMS supports content gating natively through smart content and list-based access. Webflow’s membership feature (Memberships) handles gating differently, with its own user accounts and access levels. If your gated content strategy depends on HubSpot CRM list membership, you will need middleware or a rethink of your gating model.
Structured data and schema. HubSpot auto-generates some schema markup (Article, BlogPosting). Webflow does not. You need to add JSON-LD manually via custom code blocks or a Webflow app. Audit your existing schema before migrating, and rebuild it in Webflow’s custom code sections.
Staging and content freeze. HubSpot does not offer a clean content export. You will be copying content manually or using the HubSpot API to extract blog posts as JSON. During the migration window, freeze content on HubSpot so you are not chasing a moving target. Any post published on HubSpot after you begin migration needs to be ported to Webflow separately. For broader migration planning, the Drupal migration guide covers content freeze protocols that apply to any platform move.
Internationalization. HubSpot supports multi-language page variants with hreflang annotations managed through its language settings. Webflow handles localization through its own Localization feature, but the hreflang implementation and URL folder structure will differ. Confirm that Google’s documentation on hreflang aligns with your new Webflow URL pattern before you launch.
FAQs
Can I keep using HubSpot CRM after migrating to Webflow?
Yes. Webflow replaces only the CMS and hosting layer. HubSpot CRM, marketing automation, email, and sales tools remain fully functional. You need to reconnect forms, tracking scripts, and any CRM-dependent page logic through embeds, API integrations, or automation tools like Zapier.
How long does a HubSpot to Webflow migration typically take?
For a site with 50 to 200 pages and an active blog, expect 8 to 14 weeks. The timeline depends on content modelling complexity, the number of forms and integrations, and the size of the redirect map. Sites with gated content, multi-language variants, or heavy CRM automation take longer.
Will I lose SEO rankings when migrating from HubSpot CMS to Webflow?
Ranking loss is common but preventable. The primary causes are incomplete redirect maps, changed URL structures, missing structured data, and lost internal links. A thorough crawl, a complete 301 redirect map, and a 30-day monitoring plan after launch will mitigate most ranking disruption.
Does Webflow support HubSpot forms natively?
Not natively. You can embed HubSpot forms using their JavaScript embed code, which preserves CRM integration and workflow triggers. Alternatively, you can use Webflow’s native forms and route submissions to HubSpot via API or an automation platform, though this requires additional setup and testing.
What happens to HubSpot-hosted assets like PDFs and images after migration?
Files hosted on HubSpot’s CDN (hubspotusercontent.com) remain accessible as long as your HubSpot account is active. However, you cannot set redirects on HubSpot’s CDN domain. Re-upload critical assets to Webflow or your own CDN, update internal links, and request external link updates where possible to preserve backlink equity.
Plan your HubSpot to Webflow migration right
Content modelling, redirect mapping, and CRM integration are where most migrations fail. Moburst Digital Experience builds the technical migration plan that protects your rankings and lead pipeline.