HTML to Webflow

Migrate from HTML to Webflow

A static HTML site is usually easy to understand and hard to maintain. I rebuild it in Webflow so the public site still feels familiar, but edits stop depending on the person who knows the old files.

Start a project

A migration like this usually takes 2–3 weeks

Why people move

What changes when you move from HTML to Webflow.

What is being compared	HTML	Webflow
Making a change	HTML Edit the file, upload it	Webflow Edit the page
Who can do it	HTML Whoever has the files and the FTP details	Webflow Whoever writes the copy
Repeated content	HTML Copied into every page	Webflow One collection, one template
Consistency	HTML As consistent as the last person was	Webflow Enforced by the component system
Hosting	HTML Wherever it ended up	Webflow Managed, with SSL and a CDN
What you give up	HTML Whatever the build and the host were doing	Webflow Webflow's publish, and its constraints Usually little, and not nothing: a static site can carry edge rules, headers, a deploy pipeline or a script that has no Webflow equivalent. Worth listing before it is called clean.

Once you have decided

What actually migrates.

What you have	What happens	Why
Pages	Rebuild	Rebuilt properly, but the content is all there and readable.
Text and images	Move	Everything is in the files, which is the whole advantage here.
Repeated sections	Rebuild	Become components and collections rather than copies.
URLs and redirects	Reconfigure	Often unchanged, since file paths and page paths line up.
Forms	Rebuild	Usually replacing a mail script nobody has touched in years.
Custom scripts	Depends	Some carry directly. Some were doing what Webflow now does natively.

Before you budget it

Where this migration gets complicated.

01

Repeated markup has to be recognized before it can be reused

Six pages with the same card markup are six pages until somebody names the pattern. Finding the components and the collections inside a flat codebase is analysis work that happens before anything is built.
02

JavaScript falls into three piles, and they need sorting

Some of it Webflow does natively and the code goes away, some of it is genuinely custom and carries across, and some of it was working around a limitation that no longer exists. Every script needs a decision.

How it runs

How the migration works.

01

Plan

What HTML will actually hand over, what has to be rebuilt, and what each thing becomes: a page, a collection, a field, or nothing.
02

Build

The repeated markup becomes components and the hardcoded content becomes collections, with the scripts that earn their place kept as code.
03

Migrate

Content in, assets rehosted and checked against the source, and every address that changes given a rule pointing straight at its replacement.
04

Launch

Forms at the record, every template at three widths and every old address requested, all before anything is switched. Then typically 2–3 weeks from start to live, and a week of watching what the old addresses return.

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.