HubSpot CMS to Webflow migration, with HubSpot kept as your CRM
You can move your website from HubSpot CMS to Webflow and keep HubSpot as your CRM. We rebuild your pages, blog and templates in Webflow, add HubSpot's tracking code, reconnect your forms and redirect every URL that changes. Contacts, deals, workflows and marketing email stay where they are.
ActiveSet is a Webflow Premium Partner with 100+ Webflow projects, rated 5/5 on Clutch. HubSpot CMS moves are quoted after a URL inventory. This page covers what moves, what stays, what needs a decision, and how we protect the pages that bring in search traffic. For the wider method, see our Webflow migration agency page.
Why teams move from HubSpot CMS to Webflow
The common reasons are design control and editing speed. Teams want designers to build custom layouts and interactions without working inside HubSpot's module system. And they want marketers to publish pages in a visual editor without waiting on a developer.
Keeping HubSpot as the CRM is normal. Webflow's HubSpot app connects forms to HubSpot and can switch on HubSpot's tracking script, so page views and form fills still reach contact records. Our Webflow vs HubSpot Content Hub cost guide compares the two bills line by line.
When not to migrate
Some HubSpot sites are better left where they are. We will tell you on the scoping call if yours is one of them.
- Your pages change content for each visitor using smart content, and that personalization drives results. HubSpot says smart forms and smart modules only work on HubSpot pages.
- You run logged-in or members-only areas with HubSpot memberships. Webflow retired its own User Accounts feature on 29 January 2026, so gated content on Webflow needs a separate tool.
- Many pages are generated from HubDB tables that other HubSpot tools also read.
- One vendor, one login and one invoice matter more to your team than design control.
If one of these applies, the usual middle path is to move the marketing site and keep those pieces in HubSpot, for example on a subdomain connected to HubSpot.
What moves, what stays and what needs a decision
Webflow says there is no automated way to convert a site from another platform. A migration is a rebuild that uses your current site as the reference. So we sort every HubSpot feature into one of three groups before we quote.
Moves to Webflow
- Website pages, and the landing pages you want to keep.
- Blog posts, authors and tags, as Webflow CMS collections.
- Templates and modules, rebuilt as Webflow components.
- HubDB tables used for site content, as CMS collections. HubSpot exports a HubDB table as CSV, with images as URLs.
- Titles, meta descriptions, canonical tags and structured data.
Stays in HubSpot
- Contacts, companies, deals, lists and workflows.
- Marketing email.
- Forms, embedded on Webflow pages or connected through the HubSpot app.
- Chat. Webflow's HubSpot app has a setting to add the HubSpot chatbot.
- Traffic and contact reporting, once the tracking code is on every Webflow page.
Needs a decision
- Smart content: simplify it, or rebuild the parts that matter with Webflow Optimize personalization, a paid Webflow add-on. Smart CTAs can still run on Webflow pages with the tracking code installed.
- Memberships and private content: keep them in HubSpot or move to a third-party membership tool. We scope this separately.
- Blog subscription emails: HubSpot can send them for an external blog from an RSS feed, on Marketing Hub Professional or Enterprise. Webflow can generate an RSS feed for a CMS collection.
- Files in HubSpot's file manager that emails, PDFs or other sites link to: keep them in HubSpot or move them and redirect the links.
- Multi-language pages: plan the locales in Webflow Localization.
Which form route fits
| Route | What it is | Watch for |
|---|---|---|
| iframe embed | The HubSpot form, managed and styled in HubSpot | Changes in HubSpot go live without a Webflow publish |
| Developer embed | The HubSpot form, styled in Webflow | Needs HubSpot Marketing Professional or Enterprise, and forms built in HubSpot's new form editor |
| Webflow form | A native Webflow form sent to HubSpot through the non-HubSpot forms tool | Text inputs only; no dropdowns, checkboxes or text areas |
We pick a route per form and test every submission on staging and again after launch. Our guide to Webflow forms vs HubSpot forms goes deeper.
How we build the redirect map
HubSpot's redirects only work for domains hosted in HubSpot. Once your domain points to Webflow, every redirect you set up in HubSpot stops working. So we export HubSpot's redirects as CSV first and carry the rules that still matter into the new map.
- Crawl the site and pull the sitemap and Search Console pages, so pages that earn visits and links are on the list.
- Add HubSpot's exported redirects, and file links on your own domain that emails or other sites use.
- Keep slugs where we can. Webflow serves CMS items from a collection folder, so setting the blog collection's URL to your current blog path keeps post URLs the same.
- Map each changed URL one-to-one to its closest new page, never to the homepage by default.
- Remove chains and loops. Put specific rules before wildcard rules, because Webflow runs redirects oldest first.
- Import the map in Webflow's two-column CSV format. An import replaces every existing Webflow redirect, so we export and merge first.
- Test on staging and again on the live domain after cutover.
Google advises keeping redirects for at least a year. The full method is in our guides to building a Webflow migration redirect map and setting up Webflow 301 redirects.
How a HubSpot CMS move runs, step by step
- Scoping call and inventory. We crawl the site, record a Search Console baseline and use HubSpot's exports: HTML for pages, posts and templates, blog post data as CSV, redirects as CSV and HubDB tables as CSV.
- Feature audit. We list the modules each template uses and every live form, CTA, smart rule, membership and HubDB table, then sort them into moves, stays and decisions.
- Content model. Blog, authors, tags and HubDB tables become Webflow collections, checked against your plan's limits. Webflow's Premium plan lists 20,000 CMS items, 40 collections and 300 static pages.
- Rebuild. Templates are rebuilt as Webflow components to match your current design. A redesign is scoped separately.
- Import and clean. Content goes in through CSV import, then we fix headings, internal links, embeds and images.
- Reconnect HubSpot. Tracking code on every page, forms by route, chat and meeting links, all tested on staging.
- Launch and monitor. DNS change on an agreed date, redirect import, QA on the live domain, new sitemap in Search Console, then 30 days of monitoring and fixes.
Timeline
Every HubSpot CMS move starts with a scoping call and a URL inventory. The timeline is set after that, in writing. A site just over our 3-day caps typically takes 1 to 3 weeks. Larger sites, or sites with memberships, smart content or several languages, get a dated plan in the proposal. Your HubSpot site stays live until you approve the launch.
Price
Our fixed 3-day prices are published for small WordPress sites. A HubSpot CMS site gets a written quote after the URL inventory, because modules, forms and smart content vary more from site to site. For reference, these are the published 3-day tiers. USD prices are fixed; INR prices are plus GST.
| Tier | Scope | USD | INR |
|---|---|---|---|
| Express (Webflow) | Up to 5 pages, 1 CMS collection up to 50 items, 1 form | US$1,900 | ₹75,000 + GST |
| Standard (Webflow) | Up to 10 pages, 2 collections up to 150 items in total, up to 3 forms | US$3,200 | ₹1,40,000 + GST |
| Code (Astro static, not Webflow) | Up to 10 pages, a blog up to 150 posts, up to 3 forms | US$3,900 | ₹1,75,000 + GST |
| Custom quote | Anything over the caps or outside the fixed scope | Written quote after the URL inventory, typically 1 to 3 weeks |
The quote is agreed in writing before work starts. Details of the fixed tiers are on the 3-day migration page.
Risks, and how we handle them
| Risk | How we handle it |
|---|---|
| HubSpot redirects stop working after the DNS change | Export them before launch and merge them into the Webflow map |
| Forms stop sending to HubSpot | One route per form, test submissions on staging and on the live domain |
| HubSpot stops recording visits | Tracking code on every page, checked at launch |
| Smart content or gated pages disappear without a plan | Listed in the audit, each with an agreed decision |
| Rankings move while Google recrawls | 1:1 redirects, carried-over metadata, Search Console monitoring against the baseline |
| A launch problem we did not foresee | An agreed cutover window and a rollback plan |
No agency controls how Google ranks a moved site. Google says to expect temporary ranking changes during a move. What we control is the redirect map, the metadata, internal links and the sitemap.
Where this comes from
In November 2022 Keatech asked ActiveSet to redesign keatech.com, which was built on HubSpot. Pixeto, a design studio we partner with, did the design, and we built the site in Webflow with the CMS, HubSpot forms connected through Make, and the resource articles moved across. It went live in late January 2023. We worked together until November 2024, and keatech.com has since moved off Webflow. Read the Keatech case study.
Our HubSpot forms work on Webflow also includes CMS webinar templates with HubSpot forms for Privado, and HubSpot forms styled to match the site for mesoneer.
Disclosure: ActiveSet is a Webflow Premium Partner and earns a commission from Webflow on Webflow plans. Plan limits on this page are Webflow's own, checked 7 Nov 2026.
Frequently asked questions
Can we keep HubSpot as our CRM after moving to Webflow?
Yes. Contacts, deals, workflows and marketing email stay in HubSpot. Only the website moves. Forms on the Webflow site send submissions to HubSpot, and the tracking code ties page views to contacts.
How do HubSpot forms work on a Webflow site?
Webflow's HubSpot app offers three routes: an iframe embed, a developer embed styled in Webflow, and a native Webflow form sent through HubSpot's non-HubSpot forms tool. The developer embed needs HubSpot Marketing Professional or Enterprise. We test every form before and after launch.
Will HubSpot still track visits on the Webflow site?
Yes, once the tracking code is installed. HubSpot says pages hosted outside HubSpot need it added by hand. Webflow's HubSpot app has a setting that turns it on, and we confirm at launch that visits and form fills are recorded.
What happens to smart content?
HubSpot's smart modules and smart forms only work on HubSpot pages. We list where you use them, then simplify them or rebuild the ones that matter with Webflow Optimize personalization, which is a paid Webflow add-on.
What about memberships and private content?
Webflow no longer has its own membership feature; it was retired on 29 January 2026. Gated areas either stay in HubSpot or move to a third-party membership tool. We scope this as a separate item.
Do our HubSpot redirects carry over?
Not by themselves. HubSpot's redirects only work while your domain is hosted in HubSpot. We export them as CSV and merge the ones that still matter into the Webflow redirect map before launch.
How much does a HubSpot CMS to Webflow migration cost?
It is quoted in writing after the URL inventory, priced on pages, templates, CMS content and integrations. Our only published fixed prices are the 3-day tiers for small WordPress sites, from US$1,900 / ₹75,000 + GST to US$3,900 / ₹1,75,000 + GST.
How long does it take?
We set the timeline after the scoping call and URL inventory. A site just over our 3-day caps typically takes 1 to 3 weeks. Your HubSpot site stays live until you approve the launch.
Will we lose rankings?
No one can promise that. Google decides how a moved site ranks and says rankings can fluctuate while it recrawls. We control the 1:1 redirects, carried-over metadata, internal links and the sitemap, and we monitor Search Console for 30 days after launch.
Can our blog subscription emails keep working?
Yes, with a new source. HubSpot can send subscription emails for a blog hosted outside HubSpot from its RSS feed, on Marketing Hub Professional or Enterprise. Webflow can generate an RSS feed for the blog collection.