HubSpot to Webflow Migration Guide (2026) | Studio Huncho blog
Webflow and Framer

10 min readMINUTES

How to Migrate from HubSpot CMS to Webflow: A Step-by-Step Guide

Arpit Agrawal, Co-founder and Design Director, Studio Huncho
Arpit Agrawal
November 22, 2026
HubSpot to Webflow Migration Guide (2026) | Studio Huncho blog

The short answer

To migrate from HubSpot CMS to Webflow, audit every URL, export your blog posts, HubDB tables and existing URL redirects from HubSpot, rebuild the design and templates in Webflow, import the content into Webflow CMS collections, reconnect forms and tracking to HubSpot, redirect every old URL and launch with SEO checks. You can keep HubSpot as your CRM and marketing tool: only the website moves. For a startup marketing site with a blog, the move usually takes a few weeks.

We are a Webflow Certified Partner and build Webflow sites for AI and SaaS startups, many of whom run HubSpot as their CRM. This guide is the process we follow. Last checked: 22 November 2026, against HubSpot's knowledge base, Webflow's help centre, app listing and pricing page, and Google's site move guidance.

The seven steps at a glance

  1. Audit: list every URL, form, smart content rule and landing page on HubSpot.
  2. Map: match blogs and HubDB tables to Webflow CMS collections.
  3. Export: export blog posts, HubDB tables, existing redirects and files.
  4. Rebuild: design and build the pages and CMS templates in Webflow.
  5. Reconnect HubSpot: forms, tracking code and chat go back to the same HubSpot account.
  6. Redirect: write a 301 map for every old URL, including a blog subdomain if you have one.
  7. Launch: switch DNS, submit the sitemap and watch Search Console for 30 days.

Should you move from HubSpot CMS to Webflow at all?

Teams move the website off HubSpot CMS when design and speed start to matter more than having everything in one tool: designers want full control of layout and interactions, marketers want to publish without template limits, and the team wants to stop paying for CMS features it does not use. The CRM, email, forms and reporting can stay in HubSpot. If the site leans heavily on HubSpot smart content, memberships or personalised pages, plan those replacements first. Our Webflow vs HubSpot comparison covers the trade-offs.

What moves from HubSpot to Webflow, and what does not

  • Moves as data: blog posts, HubDB tables and your existing list of URL redirects, which HubSpot can all export.
  • Has to be rebuilt: page templates, modules, themes and landing page layouts. HubSpot can export page HTML, but it is a reference for the rebuild, not something Webflow imports.
  • Reconnected, not moved: forms, the tracking code and chat. They keep working with the same HubSpot account from the Webflow site.
  • Needs a plan: smart content, personalisation, memberships and A/B tests built in HubSpot CMS. Decide what replaces them before the build.

How to get your content out of HubSpot

HubSpot's export guide covers the main exports. You need Super Admin or publishing permissions for most of them.

Blog posts

Under Content > Blog > Actions, choose Export blog posts to download post data as CSV, XLS or XLSX. To get the full post HTML as well, use Export all pages and blog posts (HTML) from the same Actions menu in Website Pages, Landing Pages or Blog. Combine the two into one CSV that matches your Webflow blog collection, with the body as clean rich text.

HubDB tables

If you use HubDB for team members, locations, resources or pricing tables, open each table, choose Actions > Export and download it as CSV (see HubSpot's HubDB guide). Each table usually becomes one Webflow collection.

Existing URL redirects

HubSpot lets you export your URL redirects as a CSV file from the URL Redirects settings (see the redirects guide). Bring these into your redirect map, so old redirects keep working and do not turn into chains.

Files and images

Images in post bodies point at HubSpot's file storage. Download the ones you need, rename and compress them, and upload them to Webflow's Assets panel. PDFs and other gated files need a new home, often a Webflow asset or a HubSpot file link behind a form.

The HubSpot to Webflow migration, step by step

1. Audit what you have

Make a spreadsheet of every URL on the HubSpot site: static pages, blog posts, collection pages, legal pages and anything that only shows up in search. Add each page's traffic and backlinks from Google Search Console or your SEO tool, its title and meta description, and the forms, embeds and scripts it uses. This sheet becomes your redirect map later.

2. Map your content to the Webflow CMS

Decide what becomes a static page and what becomes a CMS collection. Blog posts, case studies, team members, job openings and customer logos are usually collections. Write down the fields each one needs (title, slug, summary, body, cover image, author, category, SEO title, meta description) before you build anything, because the CSV you import has to match them column by column.

3. Get the content out of HubSpot

Export blog posts (data and HTML), each HubDB table and your existing redirects, then download the images and files. Note every HubSpot form and where it appears, because each one is reconnected later.

4. Import into Webflow and check a small batch

Create the collections in Webflow, then import the CSV into each one. Webflow's CMS import guide walks through matching columns to fields. Import five or ten items first, check them on the collection template, fix the mapping, then import the rest. Images in rich text need a second look, because links that point back at the old platform break once it is switched off.

5. Rebuild the design

Nothing visual imports into Webflow, so every page and template is designed and built again. Start with a style guide (colours, type, spacing, buttons), then build the global parts such as the navigation and footer, then the templates. Many teams keep the brand and use the rebuild to fix structure, speed and the pages that never converted.

6. Set up 301 redirects

Go back to the audit sheet and give every old URL a new home: the same page at its new path, the closest page if it was merged, or a parent page if it was cut. Add them in Webflow under Site settings > Publishing > 301 redirects (see Webflow's redirect guide). Redirect one hop only, from the old URL straight to the final one.

7. Run SEO checks and launch

Carry every title, meta description and Open Graph image across, check headings and alt text, and publish to the staging domain for a full pass at desktop, tablet and mobile sizes. Then add the redirects, switch DNS and submit the new sitemap. Google's site move guide is the reference for this part.

Keeping HubSpot working on a Webflow site

  • Forms: the HubSpot app for Webflow lets native Webflow forms send submissions to HubSpot through its non-HubSpot forms feature, or you can embed HubSpot forms directly. Some form styling features need a HubSpot Marketing Professional or Enterprise plan, according to the listing.
  • Tracking code: add the HubSpot tracking code under Site settings > Custom code so page views and contact activity keep flowing into the CRM.
  • Chat: the same tracking code loads HubSpot chat on the Webflow site.
  • Landing pages: rebuild the ones you still use in Webflow, or keep a few on HubSpot under a subdomain while you move them across.

A worked URL mapping example

HubSpot blogs often live on a subdomain, while Webflow sites usually serve the blog from the main domain. Map both the path and the host:

  • blog.company.com/how-we-price-our-product redirects to company.com/blog/how-we-price-our-product
  • company.com/blog/how-we-price-our-product stays the same if the Webflow collection slug is also blog
  • company.com/blog/tag/product redirects to /blog/category/product, or to /blog if you drop tag pages
  • info.company.com/demo (a HubSpot landing page) redirects to company.com/demo once it is rebuilt

Webflow's 301 redirects work on paths for domains connected to the Webflow site, so a blog subdomain either gets connected to the Webflow site or has its redirect set up where its DNS is managed. Webflow's redirect guide covers the rules themselves.

Where each HubSpot SEO setting lives in Webflow

  • SEO title and meta description: page settings for static pages, and CMS fields bound in the collection template's settings for posts.
  • Open Graph title, description and image: the same settings panels, with an option to reuse the SEO values.
  • XML sitemap: generated automatically under Site settings > SEO.
  • Robots.txt: edited under Site settings > SEO.
  • Redirects: Site settings > Publishing > 301 redirects.
  • Schema: custom code in page settings, or an embed in the CMS template that pulls in CMS fields.

A realistic migration timeline

Most of our website projects take 2 to 6 weeks. For a startup marketing site with a blog, a migration usually breaks down like this:

  • Week 1: audit, URL inventory, content export, CMS structure.
  • Weeks 2 to 3: design of key pages and CMS templates.
  • Weeks 3 to 5: Webflow build, content clean-up and import, redirect map.
  • Final week: QA, SEO checks, launch and monitoring.

Hundreds of posts, several languages or content that has to be copied by hand add time. So does content that is rewritten rather than moved. We redesigned Itilite's website and rebuilt it on Webflow, and organic deals now land about 2.5x better.

Launch day and the first 30 days

  • Before DNS: publish to the staging domain, click through every template and test every form.
  • At cutover: add the 301 redirects first, then point DNS at Webflow, then publish to the custom domain.
  • Same day: submit the new sitemap in Google Search Console and test a sample of old URLs to check they land on the right page.
  • First 30 days: watch the Pages report for 404s and pages that drop out of the index, and fix redirects as they show up.
  • Keep the old site: leave the old plan running and a full copy of the content for at least a month before you cancel it.

Migration checklist

  • Every URL listed with traffic, backlinks, title and meta description
  • CMS collections and fields written down before the build
  • Content exported and a backup copy kept outside both platforms
  • Images downloaded, renamed and given alt text
  • Fonts licensed for use on Webflow
  • Five to ten items imported first and checked on the template
  • Forms rebuilt and test submissions received
  • Analytics and tag manager added in site settings
  • 301 redirect for every old URL with traffic or links
  • Staging site checked at desktop, tablet and mobile sizes
  • DNS TTL lowered a day before the switch
  • New sitemap submitted in Search Console on launch day
  • Blog post data and HTML exported
  • HubDB tables and existing redirects exported
  • HubSpot forms and tracking code reconnected and tested

What mistakes should you avoid?

  • Forgetting old redirects: import HubSpot's existing redirect list too, or old campaign links break.
  • Losing form data: test every form on staging and check the submission lands in HubSpot with the right properties.
  • Leaving the blog subdomain behind: plan its redirect before launch, because those URLs often carry the most backlinks.
  • Cancelling the CMS add-on before the move is checked: keep it until every page and redirect is confirmed.
  • Switching DNS before redirects are live: add redirects first, then point the domain at Webflow.

Migrate it yourself or bring in a Webflow partner?

A small site with a few pages and a short blog is a realistic do-it-yourself project if someone on the team knows Webflow. It gets harder with hundreds of posts, content that has to be copied by hand, several languages, or organic traffic you cannot afford to lose. That is when a team that has done it before earns its place, because the redirect map and the CMS structure are where most migrations go wrong.

We are a Webflow Certified Partner and design and build in Webflow for AI and SaaS startups. See our Webflow development service, or read what a Webflow partner does and the questions to ask before you sign.

Related reading: Webflow vs HubSpot, How to Migrate from WordPress to Webflow, Can marketers edit a Webflow site without developers?, How Do You Maintain a Webflow Site After Launch?, All Webflow and Framer guides

FAQ

Can we keep HubSpot CRM if we move the website to Webflow?

Yes. Only the website moves. Webflow forms can send submissions to HubSpot through the HubSpot app, and the HubSpot tracking code and chat run on the Webflow site.

Can you export HubSpot blog posts?

Yes. HubSpot exports blog post data as CSV, XLS or XLSX, and can export the HTML of all pages and blog posts. Combine them into one CSV for the Webflow import.

Can you export HubDB tables and redirects?

Yes. Each HubDB table exports as CSV from its Actions menu, and URL redirects export as CSV from the URL Redirects settings.

Will moving from HubSpot to Webflow hurt our SEO?

Not if you keep the content, carry over titles and meta descriptions, and redirect every old URL, including any blog subdomain. Expect some movement in rankings for a few weeks.

How long does a HubSpot to Webflow migration take?

A few weeks for most startup marketing sites. Many landing pages, smart content rules or HubDB tables add time.

What happens to HubSpot landing pages?

Rebuild the ones you still use in Webflow and redirect the rest. Some teams keep a few on HubSpot under a subdomain while they move them across.

How many CMS items does Webflow allow?

It depends on the site plan. As of November 2026 the free Starter plan allows 50 CMS items and the Premium site plan allows 20,000, with custom limits on Enterprise.

Do HubSpot forms work on Webflow?

Yes. Embed HubSpot forms directly, or connect native Webflow forms to HubSpot through the HubSpot app for Webflow.

Sources

  1. export web content and dataknowledge.hubspot.com
  2. HubDB guideknowledge.hubspot.com
  3. URL redirects guideknowledge.hubspot.com
  4. pricing pagewebflow.com
  5. CMS import guidehelp.webflow.com
  6. redirect guidehelp.webflow.com
  7. site move guidedevelopers.google.com

Facts in this post were checked against these pages on 22 November 2026. Prices and plans change, so confirm current details on each site.

Studio Huncho rated 4.9 on Clutch
Need a brand, website or launch video for your startup?
One studio in Bengaluru for funded AI and SaaS startups. A scoping doc and timeline follow within 48 hours of a brief.
Ask AI about Studio Huncho

Moving your site off HubSpot CMS? Talk to us about a redesign and rebuild through our Webflow development service.

Work with Studio Huncho

We're a creative studio for AI and SaaS startups. We design brands, websites, products and launch videos, and build sites in Webflow and Framer.

Link Copied Successfully
VIEW CASE STUDY