Migrating from HubSpot to Webflow
From HubSpot CMS to Webflow, without losing your search rankings or your CRM. Content migrated, redirects handled, and forms still arriving in HubSpot.
You end up paying for a Marketing Hub package primarily to host a site, and you still need a developer for any deviation from the theme.
Does this sound familiar?
Tell me what isn't working or what's taking up too much of your time, and I'll let you know what I would do and roughly what it would cost. You'll be speaking directly to me, not an account manager.
A HubSpot migration means moving your website from HubSpot CMS to Webflow, while continuing to use HubSpot for what it does best: your CRM, email, and lead nurturing. You gain design freedom and a lower monthly bill, without your marketing team losing the tools they rely on.
When you need this
You're on an expensive HubSpot plan primarily for the website, even though you barely use the CMS features. Every deviation from the theme requires a developer. Your design is limited to what the modules allow. You want a platform where your marketing team can build pages themselves that look consistent with the rest of the site. Or, you're paying for a Marketing Hub tier just to host your site.
What stays and what goes
Moving to Webflow: your pages, blog, landing pages, images, documents, metadata, and URL structure. Staying in HubSpot: your contacts, deals, workflows, email, and reporting. The forms are the most critical part. They remain HubSpot forms, embedded or called via API from your Webflow pages, ensuring every submission lands in your CRM and your existing workflows keep running. You maintain tracking and visitor contact history using the HubSpot tracking code.
Why this goes wrong without a plan
HubSpot CMS handles URLs in its own way, especially for blogs and landing pages. These change during a migration. If an old URL leads nowhere, Google sees a dead page and your ranking drops. The same applies to links in your old newsletters and ads, which continue to be clicked for years. Lost rankings after a move are almost always due to missing redirects, not the new platform.
Our approach
First, the inventory: all URLs, which ones drive traffic, their current rankings, and where every form is located. Then, the new structure in the Webflow CMS, kept as flat as possible. Next, the redirect list: every old URL gets a 301, or a 410 if the page is intentionally removed. We import content via the API rather than manually. We reconnect the forms and tracking to HubSpot and test with real submissions, including the associated workflows. We test on staging, go live, and monitor Search Console and your CRM in the weeks that follow: ensuring leads are still coming in and landing in the right place.
Costs and timeline
A small site can be moved in two to three weeks. For hundreds of pages, a blog with years of history, and many forms, it can take months, primarily due to the preparation phase. The price is fixed and based on the inventory, as that is the only way to determine the number of content types and URLs. Afterward, your HubSpot CMS subscription ends and you pay for Webflow hosting, starting at around twenty euros per month for a CMS site. What you pay HubSpot for CRM and marketing remains unchanged.
When not to do it
If you use HubSpot features deeply integrated into your pages, such as extensive personalized content or smart content based on contact lists, these cannot be replicated easily. It is possible, but first consider if it's worth the move. And if your entire marketing and sales organization is built around a HubSpot workflow that everyone is happy with, a migration might be solving a problem you don't have.
Where we've done it
The site of Mitsubishi Turbochargers & Engines Europe was on HubSpot and has moved to Webflow. Product data is now pulled from a dedicated source and synced to the site via API, something that wasn't possible in the old CMS.
Read more
Is your site coming from WordPress: WordPress migration. Maintaining rankings: SEO. Connecting forms and CRM: system integrations. The platform: Webflow development. Include your URL when you get in touch, and we'll first assess the actual scale of the migration.
How can we help?
Cases
Projects
Get more out of your website
DeDigitaal Clients
Questions about
HubSpot migration
Will I lose my HubSpot CRM if I move my website to Webflow?
No. In a migration, only your website moves from HubSpot CMS to Webflow. Your contacts, deals, workflows, email, and reporting stay in HubSpot. The forms on your new site remain HubSpot forms, embedded or called through the API, so every submission lands in your CRM and your existing workflows keep running. You also keep visitor tracking per contact.
Will it be cheaper if I move from HubSpot CMS to Webflow?
The HubSpot CMS subscription ends, or you can move to a lower tier if you only needed it for the website functionality. In its place comes Webflow hosting, which starts at around twenty euros per month for a site with a CMS. What you pay HubSpot for CRM, sales, and marketing does not change. Whether it works out cheaper overall depends on which HubSpot tier you currently use and why.
Will I lose search rankings when migrating from HubSpot to Webflow?
Only if the redirects are not in order. HubSpot CMS structures URLs in its own way, especially for blog posts and landing pages, so they almost always change during a migration. If every old URL gets a 301 to the right new page, your traffic is preserved. That is why every migration we do starts with an inventory of all URLs and a complete redirect list, before anything goes live.
How long does a HubSpot migration take?
A small site moves in two to three weeks. With hundreds of pages, a blog with years of history, and many forms, that grows to months. Most of the work is in the preparation: the URL inventory, the new structure, and the redirect list. The price is fixed and follows from that inventory, because only then is it clear how many content types and pages there are.
What content is migrated from HubSpot to Webflow?
Pages, blog posts, landing pages, images and documents, metadata, and where possible the URL structure. We pull content in through the API instead of retyping it by hand. What doesn't carry over automatically are HubSpot features embedded deep in the page, such as personalized or smart content per contact list. That can be rebuilt, but first consider whether it is worth it.