Gemin
Start a project

HubSpot CMS to Webflow

Migrate from HubSpot CMS to Webflow

Your website moves to Webflow. HubSpot keeps what it is strongest at: the CRM records, the forms behind them, the automation and the attribution. The two stay connected, and the work is the seam between them.

Start a project

A migration like this usually takes 3–4 weeks

Why people move

What changes when you move from HubSpot CMS to Webflow.

What is being compared HubSpot CMS Webflow
Content and CRM HubSpot CMS One platform, genuinely joined up Webflow Two systems, separated deliberately HubSpot's real advantage, and the thing to weigh hardest.
Design control HubSpot CMS HubL templates and modules Webflow Components built directly in the site
Personalization HubSpot CMS Smart content, native Webflow Another implementation, in the browser or in front of it HubSpot wins this. If smart content is load-bearing for you, think carefully before moving.
Which one fits HubSpot CMS When the website and the CRM benefit from staying one system Webflow When marketing wants the website without replacing HubSpot

Once you have decided

What actually migrates.

What you have What happens Why
Pages and landing pages Rebuild Made again in Webflow. The old version is a reference rather than something that can be imported. HubSpot exports the rendered HTML and the template files, which is useful to build against. HubL templates and modules are HubSpot-specific and get rebuilt, so the source is exportable and the implementation is not portable.
Blog content Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. Exportable, and mapped into a collection with the dates, authors and addresses carried rather than reset.
Forms Reconfigure The same thing, set up again. Nothing is recreated, but it has to be pointed at the new site by hand. HubSpot stays the system that receives the lead. Per form it is an iframe embed, a developer embed styled inside Webflow, or a native Webflow form connected back to HubSpot, and the fields and the tracking decide which rather than the design.
Smart content and HubDB Rebuild Made again in Webflow. The old version is a reference rather than something that can be imported. Neither is only content. A HubDB table, its relationships and the routes it generates get mapped before anybody decides where they land, and personalization needs a decision rather than a translation. Usually the largest single piece of the job.
URLs and tracking Reconfigure The same thing, set up again. Nothing is recreated, but it has to be pointed at the new site by hand. Public routes are mapped, including the HubSpot-hosted ones, and the tracking code is reinstalled on the new domain and then verified rather than assumed.

Before you budget it

Where this migration gets complicated.

  1. 01

    Smart content and HubDB are not just content

    A HubSpot template can carry conditionals, loops and module logic that looks like static content in the browser, and a HubDB table generates routes as well as holding rows. Each one needs a new implementation decided on purpose rather than a translation, and finding them is the first task.

  2. 02

    A form that submits is not the thing being checked

    After the move the contact, the attribution and the workflow all have to arrive correctly in HubSpot. A form creating a contact does not prove the source, the campaign and the browsing context came with it, so what gets checked is the record in HubSpot rather than the button turning green.

How it runs

How the migration works.

  1. 01

    Plan

    Pages, HubL, HubDB, smart content, forms, tracking and every address that currently resolves.

  2. 02

    Build

    The website and its CMS move into Webflow, and HubSpot stays connected the whole time.

  3. 03

    Migrate

    Forms, tracking, attribution, redirects and whatever the dynamic pages were doing, reconnected one at a time.

  4. 04

    Launch

    Real submissions checked at the HubSpot record, workflows fired, old addresses requested, then the domain switches. Typically 3–4 weeks.

What you are buying

What is included.

  • Design rebuild

    Rebuilt directly against the existing site.

  • Responsive development

    Desktop, tablet and mobile, built and checked.

  • CMS architecture

    Collections and fields mapped before build.

  • Content migration

    Migrated and checked against the source.

  • Asset migration

    Collected, compressed and rehosted.

  • Forms and integrations

    Tested through to the final record.

  • Redirects

    Changed URLs mapped directly to replacements.

  • Metadata and canonicals

    Preserved wherever possible.

  • Search footprint preservation

    URLs inventoried before and checked after.

  • Pre-launch QA

    Forms, templates and old URLs verified.

  • Post-launch support

    One week of indexing and traffic checks included.

Search visibility can move during a migration. The goal is to preserve what search engines already understand, and to catch what changed quickly after launch.

Other migrations

Coming from somewhere else?

Reach out and see if we are a good fit.

Start a project

Currently booking two to four weeks out.