What is a HubSpot to Webflow migration?
It means your public website is rebuilt in Webflow and hosted there, while the HubSpot portal keeps doing CRM, automation and email. It is a change of front end, not a change of customer database.
HubSpot does let you export pages, posts and templates as HTML, and its own help page says those files can be used to bring content to another platform. In practice we use the export as source material. HubL templates cannot run in Webflow, so the design is rebuilt.
When staying on HubSpot is the better call
- Marketers build pages and emails happily in one tool
- Smart content or built in A/B tests drive real results for you
- You rely on HubSpot memberships or gated content
- Nobody would own the join between two systems
There is also a smaller step: move the main site, and leave campaign pages on a HubSpot subdomain. Read Webflow vs HubSpot CMS first.
What to export, and from where
Website pages, landing pages, blog posts and templates come out as an HTML archive from the Actions menu, sent to you as a download link. Blog post data also exports as CSV, XLS or XLSX, which is what we import from. URL redirects download as their own CSV.
Exporting needs Super Admin or Publish permission, so check that early. We also pull a traffic report per page, so the busiest URLs get the most checking.
Keeping forms and tracking intact
You have two choices for each form. Embed the HubSpot form so nothing changes in the portal, or build a Webflow form and map it through the HubSpot app listed on Webflow, which gives more control over styling.
The tracking code goes into site settings. Then we run real test submissions and trace them through to the contact record and the workflow. See HubSpot and Webflow for how the two connect.
What does not carry over
Smart content rules, built in A/B tests, HubDB dynamic pages, memberships and CTA tools belong to HubSpot CMS. Each one needs a decision: rebuild it in another way, keep that page on a HubSpot subdomain, or let it go.
Files are easy to miss. If a past email links to a PDF on a /hubfs path, plan how it stays available before you make any changes.
Redirects and launch
HubSpot says its URL redirects only work on domains connected to and hosted in HubSpot. So the moment the domain moves, those rules stop. We export them, drop any that are dead, and rebuild them in Webflow with a 301 for each changed path.
- We lower the TTL the day before.
- On a call, we change only the records that point the website. Email sending records stay.
- We test forms, redirects and tracking on the live domain.
- The new sitemap goes to Search Console, and we check it daily for two weeks.
Every old URL is mapped to protect your rankings. Some movement in the first weeks is normal, and no one can promise it will not happen.







