HubSpot to Webflow Migration: A Guide for B2B Teams

A HubSpot to Webflow migration moves your website from HubSpot CMS to Webflow while HubSpot remains your CRM. You export pages and blog posts, rebuild templates as Webflow components and CMS Collections, reconnect forms and tracking to HubSpot, and recreate every redirect in Webflow before the domain switches.

For most B2B teams, the move is about the website alone. HubSpot stays as the system for contacts, deals, lead scoring, workflows, and email, and Webflow becomes the place where marketing builds and publishes pages.

Webflow and HubSpot work well together when the connection is planned before launch. This guide covers what moves, what stays, and the seven steps we follow in our website migration services.

Why B2B Teams Move the Website and Keep HubSpot

Teams usually make this move to give marketing more control over the website, while sales keeps working in the HubSpot records it already trusts. The reasons we hear most often:

• Marketers want to publish landing pages from approved sections, without waiting on a developer.
• Designers want full control of layouts and interactions in a visual editor.
• Content teams want CMS Collections for case studies, integrations, resources, and other structured content.
• Larger teams want Webflow Enterprise for publishing roles and governance across several editors.

None of that requires changing the CRM. HubSpot stays the source of truth for every lead the website creates.

What Stays in HubSpot and What Moves to Webflow

The CRM side of HubSpot stays exactly where it is. Only the parts that build and host the website move.

HubSpot CMS Migration to Webflow, Step by Step

These seven steps cover a typical HubSpot website migration for a B2B team. Steps 5 and 6 need the most care, because they protect your leads and your rankings.

Step 1: Inventory Your HubSpot Site

List everything the site does before you plan the new one. Our website migration plan template gives you a place to track each item.

• Crawl every URL with a tool such as Screaming Frog, including website pages, landing pages, blog posts, and files.
• List every HubSpot form, CTA, chat widget, and meetings embed, and the page each one sits on.
• Note any pages that use smart content, which changes what a visitor sees based on HubSpot data, and any HubDB tables.
• Export your URL redirects as a CSV file from HubSpot's URL redirects tool. You'll need them in Step 6.

Step 2: Export Your Content From HubSpot

HubSpot lets you export HTML files for pages, blog posts, and templates, and export blog post data as a CSV, XLS, or XLSX file. HubSpot sends a download link by email once the export is ready, and the export needs Super Admin or Publish permission.

If your site uses HubDB, the database tables HubSpot uses for dynamic pages, export each table as a CSV file. Each table usually becomes a CMS Collection in Webflow.

Step 3: Rebuild Templates and Modules in Webflow

HubSpot templates and modules are built in HubSpot's own template language, so they get rebuilt in Webflow as components and page templates. This is the point to fix layouts your team has worked around for years.

Build a set of components your marketing team can use to publish pages without a developer. Our Webflow development team builds sites this way, so new landing pages come from approved sections.

Step 4: Move the Blog and Structured Content Into CMS Collections

Map each field in the export to a field in a Webflow CMS Collection: title, slug, author, publish date, featured image, summary, SEO title, and meta description. Then clean the HTML, upload images to Webflow, and import the posts.

Move a small sample first and compare it with the live posts before you import the rest. Our website migration checklist covers what usually breaks in this step, and we explain how we use AI agents to migrate content on larger sites.

Step 5: Reconnect HubSpot Forms, Tracking, and Chat

This is where the Webflow HubSpot integration does its work. There are three ways to connect Webflow forms to HubSpot. Pick one per form and test each one before launch.

• The HubSpot app for Webflow. The HubSpot app in the Webflow Marketplace lets you place HubSpot forms on Webflow pages, or send native Webflow form submissions to HubSpot through HubSpot's non-HubSpot forms feature. The form editor and embed styling features need a HubSpot Marketing Hub Professional or Enterprise plan.
• Webflow form mapping. Webflow's HubSpot forms integration maps the fields of a Webflow form to a HubSpot form. Give every form a unique name, and republish the site after you connect it.
• HubSpot form embeds. Paste a HubSpot form's embed code into a Webflow embed element. The form stays a HubSpot form, with its fields and follow-up emails managed in HubSpot.

Then add the HubSpot tracking code. HubSpot adds it automatically to HubSpot-hosted pages, so on Webflow you paste it before the closing body tag on every page. In Webflow, that's the Footer code field in Site settings. Without it, HubSpot can't track page views or tie visits to contacts.

If your tracking needs work anyway, our analytics and Google Tag Manager setup team can fix it during the move.

Step 6: Recreate Your Redirects in Webflow

This step is easy to miss. HubSpot says its URL redirects only work for domains connected to and hosted in HubSpot. Once your domain points to Webflow, every redirect you set up in HubSpot stops working.

• Start from the redirect CSV you exported in Step 1.
• Add a 301 redirect for every page whose URL changes in the new site. Webflow keeps CMS items inside a folder, such as /blog/post-name, so check your blog URLs.
• Import the full list into Webflow, which accepts a two-column CSV of old and new paths.
• Test a sample of old URLs on the staging site before launch.

Step 7: Switch the Domain and Watch Search Console

Point your domain to Webflow, submit the new sitemap in Search Console, and send a test lead through every form on the live site. Check that each lead reaches HubSpot with its source.

Watch Search Console every day in the first week and every week for the first 30 days.

We track every migration against its pre-launch baseline for 30 days, and our website migration checklist explains what normal movement looks like.

What to Watch For in a HubSpot CMS Migration

These are the HubSpot-specific details that cause problems after launch:

• Duplicate form names in Webflow. Webflow's integration can send the wrong form, or several forms, to HubSpot when two forms share a name.
• Smart content. Rules that personalize a section for each visitor don't carry over. Decide which sections need personalization on the new site.
• Landing pages built for campaigns. Some teams keep HubSpot landing pages on a subdomain connected to HubSpot. Decide this early, because it changes your redirect map.
• Missing tracking code. If the HubSpot tracking code isn't on every page, contact timelines and attribution reports stop updating.

Plan Your HubSpot to Webflow Migration With a Partner

A HubSpot to Webflow move works best when the website team and the HubSpot admin plan the connection together. We've built 500+ Webflow sites as a Webflow Enterprise Partner, and our website migration services cover the export, the rebuild, the redirects, and the HubSpot connection.

On a recent migration for Sidecar Health, we connected HubSpot, GA4, and Google Tag Manager, and the new site launched in half its originally scoped timeline. If your site runs on WordPress, see our WordPress to Webflow migration service instead.

Frequently Asked Questions About HubSpot to Webflow Migration

Can we keep HubSpot as our CRM after moving to Webflow?

Yes. Moving the website to Webflow changes where pages are built and hosted, and HubSpot keeps your contacts, deals, workflows, and email. Forms on the Webflow site send submissions to HubSpot, and the HubSpot tracking code keeps page views and contact activity flowing into the same records.

Do HubSpot forms work on a Webflow site?

Yes. You can place HubSpot forms on Webflow pages with the HubSpot app or an embed code, or map native Webflow forms to HubSpot forms. Each option sends submissions to HubSpot. Test every form on the live site after launch and check that the lead appears in HubSpot.

Will our HubSpot redirects still work after the migration?

No. HubSpot says its URL redirects only work for domains connected to and hosted in HubSpot. Export your redirects as a CSV file before the move, add any new ones for changed URLs, and import the full list into Webflow before you point the domain to Webflow.

Can we export our blog from HubSpot?

Yes. HubSpot exports pages, blog posts, and templates as HTML files, and blog post data as a CSV, XLS, or XLSX file, with a download link sent by email. Map each field to a Webflow CMS Collection, clean the HTML, and import a small sample before moving the rest.

Does HubSpot tracking work on a Webflow site?

Yes. HubSpot tells you to paste its tracking code before the closing body tag on every page of an external site. In Webflow, add it once in the Footer code field in Site settings. The code tracks page views and form submissions, including forms that aren't built in HubSpot.

What happens to HubDB tables and smart content?

HubDB tables can be exported as CSV files and imported into Webflow CMS Collections, which then power the same kind of dynamic pages. Smart content rules stay in HubSpot and don't carry over, so decide which personalized sections the new site needs and plan how each one will work.