Webflow to HubSpot CMS migration.
Collections become HubDB. Webflow sites move to HubSpot for one reason: the forms, the CRM and the content should be the same system. The honest part of the conversation is which interactions get rebuilt in CSS and which get dropped.
The site is beautiful and knows nothing.
Webflow builds a good-looking site quickly. What it does not do is put the form submission, the page view and the deal on the same record without a chain of integrations. Teams migrate when the reporting gap starts costing more than the design flexibility is worth.
The form submitted. The CRM never heard.
Webflow — the gapWhat does not survive the move.
Interactions do not carry
Webflow interactions are a proprietary timeline format with no export. Each one is rebuilt in CSS or scoped JavaScript, or dropped. Deciding which is a design conversation to have before the build, not during.
Symbols are not modules
A Webflow symbol is a reusable block of markup. A HubSpot module is a component with typed fields an editor can fill. The rebuild is an upgrade, but it is a rebuild rather than a paste.
Collections become HubDB or blog
CMS collections map to HubDB tables with dynamic page templates, or to the HubSpot blog if they are really posts. Nested references and multi-reference fields need modelling rather than importing.
Form handling changes entirely
Webflow forms post to Webflow. HubSpot forms post to the CRM. Everything downstream — notifications, integrations, thank-you logic — is rewired, which is usually the reason for the move.
Custom code embeds
Most Webflow sites carry embeds in page settings and before the closing body tag. They are invisible in the designer and load-bearing in production, so they get inventoried explicitly.
Hosting, redirects and the domain
The redirect map, DNS and SSL move on a plan. Webflow redirects need exporting before the site is decommissioned, because afterwards they are simply gone.
The sequence, start to cutover.
Discovery
Object counts, custom fields, automation and the integrations that will break on the way out, read from the source system rather than from a questionnaire.
Mapping
Field by field, including what will not carry across, agreed and signed before anyone exports anything.
Dry run
A complete rehearsal into a sandbox portal, reconciled against source counts so the gaps surface a month early rather than on cutover night.
Automation rebuild
Workflows, sequences and routing rebuilt to the new model rather than transliterated from the old one, which is how a migration inherits a decade of workarounds nobody remembers writing.
Cutover
A dated switch with the legacy system read-only for a defined window, and a rollback that was tested rather than assumed.
Post-migration support
A named engineer through the first full reporting cycle, which is when the questions actually arrive.
Pixel parity is the wrong goal.
Chasing an exact reproduction of a Webflow site in HubSpot spends the budget on the last five per cent of visual fidelity and leaves nothing for the module system underneath. We rebuild to the design system rather than to the pixel, and the team gets a site they can actually extend.
What people ask before they commit.
Can HubSpot do everything Webflow can visually?
Close, and the gap is narrower than people assume, because both end up as HTML and CSS. The genuine difference is Webflow interactions, which have no equivalent and get rebuilt in code or cut.
What happens to our CMS collections?
They become HubDB tables with dynamic page templates, keeping the URL structure so nothing loses its ranking. Multi-reference fields need a modelling decision, which we make in discovery.
How long does it take?
Three to eight weeks for most marketing sites. Page count matters less than how many genuinely distinct templates exist behind them.
Will our team still be able to edit it?
Yes, and usually more safely than in Webflow. Modules with typed fields mean a marketer can build a page from approved pieces without being able to break the layout.
Can we keep Webflow and just connect it to HubSpot?
Yes. Tracking code, HubSpot forms embedded in Webflow and a CRM sync get you most of the reporting benefit without a rebuild. We will tell you when that is the better-value answer.
Where people go from here.
One system for the site and the record.
Tell us what you are running
What the system does today, where it breaks, and when it has to work. An engineer reads it — you get an answer inside one business day, not a sequence.