By Vlad Levun, co-founder of Waves Creative · Updated November 11, 2026
In this article
Yes, you can move from HubSpot to Webflow and keep HubSpot as your CRM (customer relationship management) and marketing tool. Webflow runs the website. HubSpot keeps your contacts, form data, email and sales workflows. Forms and tracking connect the two.
The migration is a structure and tracking job. You map every URL, rebuild every form, reinstall every tracking script and test them before launch. Leads then keep flowing into the same CRM.
Nobody can guarantee your rankings or revenue after a move, including us. This guide is for B2B marketing leads and founders whose site runs on HubSpot CMS. It does not cover moves to other platforms or rebuilding HubSpot-only features in depth.
The main reason to consider Webflow is control over design and the front end. In Webflow, designers build pages visually and publish from that build. Marketers edit content without a developer through Webflow's Content editor role on limited or client seats, while building new pages from components needs the Marketer role.
With HubSpot's CMS (content management system), your website lives in the same platform as your CRM and marketing tools. Webflow treats the site and the CRM as two systems, and forms and tracking connect them. Webflow's editing model has also changed: it fully retired the legacy Editor on October 5, 2026, so plan Content editor seats for the people who update the site.
Page speed depends on how you build the site as well as the platform. Webflow says its hosting combines AWS infrastructure with Cloudflare's global CDN. A lean build makes it easier to keep Core Web Vitals in a healthy range. Core Web Vitals are Google's metrics for loading, responsiveness and visual stability.
When not to move: your site depends on features that only work when HubSpot hosts the pages. Examples are personalized smart content, private member pages or workflows tied to CMS pages. You would need to rebuild or replace each one. Which of these features you have depends on your HubSpot plan, so check your plan on HubSpot's site first.
The keep, move or rebuild check. Find your situation in this table before you decide:
| Your situation | Our advice |
|---|---|
| Mostly pages, blog and forms | Move to Webflow |
| Custom layouts or theme changes need a developer (HubSpot's drag-and-drop editor covers simple edits) | Move to Webflow |
| Smart content drives key pages | Stay, or plan a rebuild |
| Member pages or CMS-tied workflows | Stay on HubSpot CMS |
If your team runs personalization and member areas inside HubSpot daily, one platform can be simpler than rebuilding those parts elsewhere.
Most of the site moves, and the marketing engine stays in HubSpot. The table shows each part:
| Item | What happens | Note |
|---|---|---|
| Pages and blog posts | Migrate | Static pages and CMS collections |
| Forms | Rebuild and reconnect | Submissions still go to HubSpot |
| Smart content and CTAs | Rebuild or replace | HubSpot-only features |
| Email, CRM, workflows | Stay in HubSpot | Contacts unchanged |
| Tracking code and GA4 events | Reinstall and test | Test before launch |
Blog posts usually move into a Webflow CMS collection, with fields for title, author, date, summary and body. Static pages are rebuilt from shared components, so the layout stays consistent. Multilingual sites need a plan per language: Webflow Localize is billed per locale on site plans (see Webflow pricing).
A CTA (call to action) is the button or link that asks the visitor for one next step, such as booking a demo. If you created your CTAs in HubSpot, rebuild them as buttons or components in Webflow. Then track each one as an event.
GA4 (Google Analytics 4) is Google's current analytics product. GA4 events record actions such as form submissions and CTA clicks. You must set these events up again on the new site, because they depend on the page code. For form leads, Google lists generate_lead as a recommended event name.
Work in this order. Each step depends on the one before it.
Timing depends on scope. A one-page site takes 3-4 business days. A full website runs in sprints of three weeks or longer. We set the exact timeline after the first call, once we see your scope.
You have three options:
Webflow's Apps Marketplace has a HubSpot app, approved by Webflow. It covers the first two options and adds HubSpot tracking, without custom code.
Choose embedded HubSpot forms when your marketing team changes forms often, because the team keeps editing them in HubSpot. Choose native Webflow forms when the form must match your design exactly, and map each field to a HubSpot contact property: for example, work email to Email, company name to Company, and a hidden field for the UTM source.
Test whichever option you choose. A test submission should create a contact in HubSpot and carry the source data your sales team relies on. Our Webflow and HubSpot integration guide walks through the setup.
B2B website design. We plan, design and build Webflow sites for B2B companies that need the site to explain the offer and turn visits into enquiries. See how we work
Keep URLs where you can, and redirect where you cannot. Google's guide to site moves with URL changes describes the process: map old URLs to new ones and set up permanent redirects.
SEO (search engine optimization) depends on details. For every page, carry over the title, meta description, heading structure, image alt text and canonical tag. Then publish an XML sitemap.
After launch, submit the sitemap in Search Console. Then watch the indexing reports for pages Google cannot reach.
Test SEO, CRM and consent together at launch. A redirect that drops UTM parameters, a form that sends no source data to HubSpot, or a GA4 tag that fires before consent: each one means fewer leads in your reports. Check them in one test run, and remember that tracking covers consenting visitors only.
Rankings can dip for a while after a move, while Google recrawls and processes the new URLs. Google's own site move guide expects temporary ranking fluctuation.
Cost depends on page count, content volume, integrations and tracking. Landing pages (one-page sites) typically start at €1,000. Larger migrations get a custom offer after a first call. These are our own typical starting points, not a market benchmark.
We are a two-person, senior-led studio in Warsaw, co-founded by Vlad Levun and Maria Fedosenko. Vlad leads design. Maria leads marketing, creative ideas and creative strategy. You get senior design and marketing without hiring both roles in-house. Already have a designer or developer? We work alongside them, or build from a design you already have. See our B2B website design service for the scope.
We built Simca's Webflow site from a finished design. The goal was a fast, maintainable site that the Simca team updates themselves, without calling a developer for every change. Both cases are Webflow builds, not HubSpot migrations.
For FBA, we built a multilingual Webflow site. We rewrote the positioning and copy, redesigned the site architecture, and built the site with SEO setup and conversion tracking.
Our hands-on work is Webflow design, development, CMS set-up and QA. The HubSpot-side steps in this guide follow HubSpot's, Webflow's and Google's own documentation.
We are a senior studio in Warsaw that joins your team and handles brand, website and marketing end to end. You work directly with the founders. There are no account managers in between.
After the first call, we get to know your business, goals and audience. Then we send a custom offer, not a fixed package. In the first phase, we:
We set the timing after the first call. The founders show you progress every week. After launch we stay on for SEO, campaigns and site improvements.
We do not guarantee revenue, rankings or conversion numbers. We commit to structure: clear positioning, a deliberate CTA hierarchy with one primary action per page, and tracking, so you can measure results and improve them.
Want a team to do this for you? Waves Creative handles brand, website and marketing for growing B2B and SaaS companies. Book a 30-minute call.
Yes. Only the website layer changes. Your forms keep sending submissions to HubSpot contacts, and your email, workflows and sales pipeline stay where they are.
Not necessarily. 301 redirects, preserved metadata and a clear page structure limit the risk. Rankings can fluctuate for a while after the move, and nobody can guarantee them.
A one-page site takes 3-4 business days. A full website runs in sprints of three weeks or longer, depending on page count, content volume and integrations. We confirm the timeline after the first call.
Yes, once you install the HubSpot tracking code and your GA4 events and test them before launch. Tracking covers consenting visitors only. Consent rules apply across the EU/EEA, the UK and Switzerland, and ad blockers and cross-device B2B journeys also leave gaps.
Moving from HubSpot to Webflow works when you keep HubSpot as your CRM, rebuild forms and tracking deliberately, and redirect every old URL. The next step is an audit of your URLs, forms and tracking, which you can talk through with us using the call link above.
How we checked this. Plans, prices and limits come from the vendors' official pages, checked on October 9, 2026: Webflow pricing, Webflow hosting, Webflow: legacy Editor FAQ, Webflow: legacy Editor deprecation, Webflow: HubSpot app, Webflow: Salesforce integration. Feature descriptions come from each vendor's documentation and our own Webflow work; features change often, so check the vendor's site before you buy. Spotted an error or an outdated price? Email hello@wavescreative.co and we will correct it.
About the author. Vlad Levun is co-founder of Waves Creative, a senior studio in Warsaw that joins growing companies' teams and handles brand, website and marketing end to end. Waves designs and builds client websites on Webflow, from design and development to CMS set-up and QA.
Next step