Plan your move from HubSpot CMS to Webflow

Move your HubSpot CMS site to Webflow while contacts, forms and campaigns stay in HubSpot: what moves, what changes and how to keep the CRM journey working.

Content export
HubSpot exports pages, posts and templates as HTML files. Posts reach Webflow by CSV.
What stays in HubSpot
The CRM, email, workflows and reporting. Only the website moves.
Biggest risk
Forms that stop feeding the CRM, and page views missing from contact records.
Rebuilt in Webflow
Themes, modules, HubDB-driven pages and smart content.

Is the move worth it?

Why teams move from HubSpot CMS to Webflow

  • Layouts the marketing team can change

    HubSpot pages are assembled from theme modules. In Webflow the website team changes layouts visually, without editing module code.

  • A design system, not a theme

    Components and variables keep pages consistent, and new sections don’t need a developer to add a module.

  • HubSpot keeps doing its job

    Webflow forms send entries to HubSpot through the HubSpot app, and the HubSpot tracking code can run on the new site, with consent and contact association tested before launch.

  • A clearer view of what you need

    Some teams keep a Content Hub subscription mainly to host the website. Moving the site shows which HubSpot features you still use.

When staying on HubSpot CMS is the better call

If you rely on smart content, memberships, adaptive pages or A/B tests driven by CRM data, those features don’t move with the site. Teams that use them heavily and are happy editing in HubSpot are usually better off staying.

What moves

Where each part of the HubSpot CMS site goes

Everything is listed before anything moves. This is how each kind of content usually maps; your inventory decides the final plan.

On HubSpot CMSIn WebflowHow it gets there
Blog postsA Blog posts collectionExported from HubSpot as HTML files or post data, turned into a CSV and imported.
Website pagesStatic Webflow pagesRebuilt from components, with the copy moved across.
Landing pagesWebflow pages, or left in HubSpotRebuild the ones that stay live. Campaign pages can stay in HubSpot on a subdomain.
HubSpot formsWebflow forms mapped to HubSpot forms, or HubSpot’s embedThe HubSpot app sends Webflow form entries to HubSpot. An embed keeps HubSpot’s form logic.
Blog authors and tagsAuthors and Tags collections, referenced from postsFrom the export, then linked to the posts.
HubDB tablesCMS collectionsExported as CSV and imported.
Tracking codeSite-wide custom code in WebflowAdded across the site, with consent and contact association tested before launch.
Meeting links and chatEmbeds on the relevant pagesCopied across and tested.

Rebuilt rather than moved

  • Themes and modulesHubL templates don’t run in Webflow. The design becomes Webflow components.
  • Smart contentRules based on CRM lists don’t carry over. Decide what replaces them, if anything.
  • Blog subscription emailsPoint a HubSpot RSS email at the Webflow blog’s feed, or switch to a regular newsletter.

Step by step

How to move a HubSpot CMS site to Webflow

Before the move

  1. List pages, posts and landing pages

    With the traffic, links and conversions for each, so you know which ones matter.

  2. List every form and what it triggers

    Lists, workflows, owners and notifications. All of them must still fire after the move.

  3. Decide what stays in HubSpot

    Campaign landing pages, meetings and chat can stay. The main site moves.

  4. Write the redirect map

    Including the blog root and any landing pages that change address.

The move

  1. Build the design system

    Components and templates, from the current theme or a new design.

  2. Import posts and data

    A sample first, then the full blog and any HubDB tables.

  3. Connect forms and tracking

    Map each Webflow form to its HubSpot form with the HubSpot app, then add the tracking code and consent banner.

  4. Test the CRM journey

    Submit every form on staging and check the contact, list membership and workflow in HubSpot.

After the move

  1. Switch the domain

    Point DNS at Webflow, publish the redirects and test old URLs.

  2. Stop HubSpot serving the old pages

    Remove the domain from HubSpot hosting. Keep any subdomain that still hosts landing pages.

  3. Submit the sitemap and monitor

    Watch Search Console and form submission counts week by week.

  4. Review the subscription

    Once nothing depends on HubSpot hosting, check which tier you still need.

Search traffic

Keeping your rankings through the move

Google treats a migration as a site move. These are its rules, then the risks that are specific to HubSpot CMS.

What Google asks for

  • A permanent (301) redirect from every changed URL straight to its closest replacement, with no chains.
  • No redirecting old pages to the home page in bulk. Pages with no replacement return a 404 or 410.
  • Redirects kept for at least a year, and a new sitemap submitted in Search Console.
  • Some ranking movement is normal while Google recrawls. On a medium-sized site it can take a few weeks or more to settle.

The migration SEO checklist lists every check before, during and after the move.

If traffic drops anyway, these are the checks to run.

  • Blog URLs can often stay

    HubSpot blogs usually sit at /blog/post-name. If the Webflow collection uses the same slug, most post URLs don’t change.

  • Listing, tag and author pages

    HubSpot creates these automatically. Redirect the ones that bring traffic, or rebuild them as collection pages.

  • Landing pages on a subdomain

    Pages on their own subdomain can stay in HubSpot with no redirects at all.

  • Canonicals and languages

    Check every template sets a self-referencing canonical. Rebuild language versions with Webflow Localization if you publish in more than one language.

Your part

What your team does during the move

  • Marketing operations sign-off

    The person who owns HubSpot workflows confirms each form still triggers the right automation.

  • A short content freeze

    Publishing pauses on the old site between the final content import and launch, usually a few days. Anything urgent in that window is added to Webflow by hand.

  • A staging review

    Your team clicks through the staging site, checks the content and submits every form before the domain switches.

What you provide

  • HubSpot access with permission to export content
  • A list of active forms, the workflows they trigger and the lists they feed
  • Access to the domain and DNS
  • Search Console access

Check in the published site

Keep the CRM journey working

Your website can move while contacts and campaigns stay in HubSpot. Before changing the domain, inventory embedded forms, hidden campaign fields, meeting links, subscription preferences and thank-you actions. Confirm which HubSpot subscription you still need.

  • Submit a new contact and check its field values, owner and follow-up in HubSpot.
  • Submit with an existing contact’s email and check how its record is updated.
  • Decline optional tracking and verify the form and confirmation follow the agreed consent behavior.
  • Complete a meeting booking from a migrated page and check the destination and confirmation.
Prepare the URL mapMatch old URLs to relevant destinations, then review the suggested pairs before importing.

Questions about the move

Can I keep using HubSpot CRM with a Webflow site?

Yes. Most teams that move keep HubSpot for the CRM, email and automation. Webflow forms send entries to HubSpot through the HubSpot app, and the HubSpot tracking code can run on the new site, with consent and reporting tested before launch.

Do HubSpot forms work on Webflow?

Yes, in two ways. Embed the HubSpot form to keep HubSpot’s form logic, or build the form in Webflow and map it to a HubSpot form with the HubSpot app to keep your design. Test either against your workflows.

How do I export my HubSpot blog?

The blog, website page and landing page dashboards in HubSpot have an Actions menu that exports all pages and posts as HTML files, sent as a download link. HubSpot can also export post data such as titles and URLs. The content is cleaned and imported into Webflow by CSV.

Can we keep the same blog URLs?

Usually. If the Webflow collection uses the same slug, such as blog, posts keep their paths. Tag and listing pages are the ones that tend to change.

Will we lose contact attribution?

The site can move while HubSpot continues tracking contacts and conversions. I check the form integration, consent settings, campaign data and the reports you rely on before launch, then monitor them afterwards.

What happens to smart content and A/B tests?

They don’t move. Webflow Optimize handles testing and personalisation on Webflow, or those features move to another tool or are dropped.

Do we still need a HubSpot subscription?

For the CRM, email and automation, yes. Whether you still need Content Hub depends on what else you use it for, so check before you renew.

How long does the move take?

It depends on the number of pages and posts, how many features need replacing and how much content needs cleaning. The first step is an inventory of pages, posts, forms and integrations, and the estimate follows from it. Nothing is estimated before that list exists.