Webflow exports HTML and CSS, which sounds like most of a migration and is not. The Collections, the interactions and the forms are the site, and none of them come out.
You can export static markup. You cannot export the CMS behind it, the interactions layered on it, or the forms wired into it.
A Collection is a structured content model with typed fields and references. It maps onto custom post types and fields, and that mapping is a decision rather than an import.
Scroll animations and hover states are authored in the designer and emitted as Webflow's own JavaScript. Recreating the effect is design work, not a file copy.
Webflow's Collection URLs follow its own pattern. Adopting WordPress defaults instead silently changes every address the site has ever ranked for.
Images in exported markup point at Webflow-hosted URLs. They keep working right up until they do not, and by then nobody remembers why.
Webflow forms post to Webflow. After the move they submit into nothing unless each one is rewired, which is the single most commonly missed step.
The visual design is the easy half and the half everyone starts with. The content model and the forms are what decide whether the site works a month later.
Webflow served pre-built pages from its edge. WordPress builds them, so page caching is not an optimisation here — it is what restores the behaviour you already had.
These differ from a standard WordPress site on the same plan, and each follows from replacing a hosted design tool with a database-backed CMS.
| Setting | What we do | Why |
|---|---|---|
| Collection mapping | Each Collection assigned a post type and field set before importing | A Collection is a typed content model with references between items, and importing it as plain posts discards the structure that made it editable. |
| Page caching | Enabled and warmed from day one rather than added later | Webflow served pre-built pages from its own edge, so an uncached WordPress site is not slightly slower than the old one — it is a different class of thing entirely. |
| Asset hosting | Every referenced file pulled local before DNS moves | Exported markup points at Webflow-hosted asset URLs, which keep working until the account lapses and then fail with nothing in the site explaining why. |
| Form endpoints | Rewired individually and test-submitted before launch | Webflow forms post back to Webflow, so after a move they accept a submission and deliver it nowhere, with the visitor seeing a success message. |
| URL structure | Collection URL patterns reproduced with rewrites | Webflow's Collection paths do not match what WordPress generates, so accepting the defaults changes every ranking URL on the site at once. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Free migration, Collections mapped by a person, forms that actually deliver, and every URL preserved.