★★★★★ 4.5 CE

Webflow Migration & Switching Guide 2026

Q: How do I migrate to Webflow from WordPress?

There is no one-click importer. You export your WordPress content as XML, convert it to CSV with an XML-to-CSV converter, then import the CSV into a Webflow CMS Collection and map the fields. The design is rebuilt in the Designer, from a template, a Made in Webflow clone, or a Figma-to-Webflow import, and your 301 redirects can be carried over via CSV.

Q: Can I export my Webflow site?

Yes, and this is a differentiator. On a paid Workspace plan you can export the full HTML, CSS, JavaScript and assets as a ZIP and host it anywhere. There is no attribution and no need to keep a Webflow plan. Code export is not available on Site-only plans.

Q: What does not export from Webflow?

The dynamic layer. CMS, Ecommerce, User Accounts, code components, forms, site search, password protection and localized pages are not included in the code export and stop working on an exported static site. You can export CMS, Ecommerce and User data separately as CSV, but as raw data, not functioning features.

Q: Does Webflow lock me in?

Less than most builders for design, more for data. Your markup and styling are fully portable via code export, so you are not tied to Webflow hosting for a static site. But if your value is in a large CMS, a store or memberships, that dynamic layer is hosting-locked and comes out only as raw CSV.

Q: Will my redirects carry over when I migrate?

Yes. Webflow imports 301 redirects from a CSV up to 16MB, so you can bring your old URL map over in one file. Note that a new import overwrites all existing redirects rather than merging, so keep every rule in a single master CSV.

Webflow exports full HTML, CSS, JS and assets on paid plans, so design lock-in is low. But the CMS and store come out only as raw CSV, with no one-click import.

Website BuildersVerified today

Full review Pricing Official site ↗

Webflow Migration verdict

Verified today·5 sources checked

Webflow is the rare builder you can actually leave.

On a paid Workspace plan you export the full HTML, CSS, JavaScript and assets with no attribution and host them anywhere, so design lock-in is low.

How to plan the move

Webflow suits teams that want a hosted builder without permanent lock-in, since the design and markup export cleanly to any host. It is less ideal if your value is in the dynamic layer, a large CMS, a store or memberships. That layer is hosting-locked and exports only as raw data you would have to rebuild around.

Honest limits

There is no one-click importer, so content comes in as CSV into CMS Collections and the design is rebuilt.
Code export of HTML, CSS, JS and assets, with no attribution, is available, but only on paid Workspace plans. The dynamic layer, CMS, Ecommerce, User Accounts, forms, search, password protection and localization, does not survive export and comes out only as raw CSV.
A CSV 301 import overwrites all existing redirects, so keep one master file when migrating.

Import: CSV into CMS (no 1-click)
301 redirects: CSV carry-over (16MB)
Code export: HTML/CSS/JS (Workspace)
Dynamic layer export: CSV data only
Lock-in: Low design / high dynamic

View sources

This page covers migrating in and out of Webflow. SEO output and pricing live on their own pages.

What moves into Webflow, and can you leave?

Migration & portability receipt

Pick what you are bringing to Webflow, and see exactly what transfers.

Migration read2 transfer, 3 need hand work

Content (WordPress etc.): via CSV or API, export XML, convert to CSV, import into a CMS Collection.
301 redirects: via CSV or API, CSV import up to 16MB (overwrites existing).
Design / layout: manual rebuild, rebuilt from a template, Made in Webflow clone, or Figma import.
Forms & site search: manual rebuild, rebuilt natively in Webflow.
One-click full-site import: does not transfer, no automated importer.

Cutover steps, in order

1Export source (WordPress XML), native export.
2Convert XML to CSV, import to CMS, map Collection fields.
3Rebuild design in the Designer, template / Figma import.
4Carry redirects via CSV, one master file, <=16MB.
5Connect domain and publish, SSL auto.

Every row is a documented import/export capability from Webflow and the source platforms, not an effort estimate.

Webflow migration configuration

Carry your old URLs over by uploading a 301 CSV (old path, new path) up to 16MB under Site settings, Publishing. Webflow can also export your current redirects to CSV. Remember a new import overwrites all existing rules, so keep every redirect in one master file.

301 redirect CSV (import on the way in)csv

Old Path,Redirect to Page
/2024/06/old-post,/blog/old-post
/category/(.*),/topics/$1
/contact-us,/contact
# max 16MB; new import OVERWRITES all existing redirects

On a paid Workspace plan you can export the full site as HTML, CSS, JavaScript and assets and host it anywhere with no attribution and no need to keep a Webflow plan. This is Webflow's key anti-lock-in feature, your design and markup are yours.

Export your site code (the way out)bash

# Workspace plan > Project settings > Export Code > Prepare ZIP > Download
# ZIP contains: *.html (all pages), /css (custom + webflow.css + normalize.css),
#               /js, /images

# The exported static site runs on your own server with no Webflow plan:
unzip my-site.zip -d my-site && cd my-site && python3 -m http.server 8080

The code export is design-only. The dynamic layer does not survive it: CMS, Ecommerce, User Accounts, code components, forms, search, password protection and localized pages stop working on an exported site and export only as raw CSV data, not functioning features.

What the export does NOT includetext

# Excluded from code export (export these separately as CSV data):
- CMS Collections        -> CSV
- Ecommerce products     -> CSV
- User Accounts          -> CSV
# Stop working on the exported static site:
- forms, site search, password protection, localized pages, code components

What imports cleanly into Webflow

Content	Into Webflow	Detail	Source
WordPress content	Manual (XML -> CSV)	Export WordPress XML, convert to CSV, import into a CMS Collection and map fields	—
Content into CMS	CSV into Collections	Import CSV rows as Collection items, mapping fields; subject to per-plan item limits	—
301 redirects	CSV carry-over	Import your old redirects as a CSV up to 16MB so old URLs follow over	—
Design / layout	Rebuilt	Rebuild on a template, Made in Webflow clone, or a Figma-to-Webflow import	—
One-click site importer	None	There is no automated full-site importer; content is CSV, design is rebuilt	—
Media / assets	Re-uploaded	Images and files are added to the Webflow asset manager during the rebuild	—

Source-to-Webflow mapping

Element	Lands in Webflow as	Caveat	Source
WordPress posts / pages	CMS Collection items (CSV)	Export XML, convert to CSV, map fields on import	—
301 redirects	Redirect rules (CSV)	Up to 16MB; a new import overwrites all existing redirects	—
Design / theme	Rebuilt in Designer	Template, Made in Webflow clone, or Figma-to-Webflow; not imported	—
Collection item volume	Per-plan limits	CMS item counts are capped by Site plan	—
Dynamic features (forms, search)	Rebuilt natively	Recreated with Webflow forms/search, not migrated	—
Media / assets	Re-uploaded	Images and files are added to the Webflow asset manager	—

Webflow migration timeline and rollout

Phase	What happens	Effort	Source
1. Export source	WordPress XML export	Low; native export	—
2. Shape data	XML -> CSV, map to Collection fields	Medium; convert and map	—
3. Rebuild design	Template / Made in Webflow / Figma import	High; no design import	—
4. Carry redirects	CSV 301 import (<=16MB)	Low; one master CSV	—
5. Connect domain & publish	Custom domain to Webflow hosting, SSL auto	Low; SSL auto-provisioned	—

What to verify before you commit to Webflow

Design lock-in is low: on a paid Workspace plan you can export the full HTML, CSS, JavaScript and assets and host them anywhere with no attribution and no need to keep a Webflow plan
But the dynamic layer is hosting-locked: CMS, Ecommerce, User Accounts, forms, search, password protection and localization do not survive export and stop working on an exported static site
Code export is itself plan-gated: it is only available on Workspace plans, so a site-only plan cannot export its code at all
Coming in, there is no one-click importer: content is CSV into CMS Collections and the design is rebuilt, so plan for a manual rebuild even though redirects carry over by CSV

Webflow Migration FAQ

How do I migrate to Webflow from WordPress?

There is no one-click importer. You export your WordPress content as XML, convert it to CSV with an XML-to-CSV converter, then import the CSV into a Webflow CMS Collection and map the fields. The design is rebuilt in the Designer, from a template, a Made in Webflow clone, or a Figma-to-Webflow import, and your 301 redirects can be carried over via CSV.

Can I export my Webflow site?

Yes, and this is a differentiator. On a paid Workspace plan you can export the full HTML, CSS, JavaScript and assets as a ZIP and host it anywhere. There is no attribution and no need to keep a Webflow plan. Code export is not available on Site-only plans.

What does not export from Webflow?

The dynamic layer. CMS, Ecommerce, User Accounts, code components, forms, site search, password protection and localized pages are not included in the code export and stop working on an exported static site. You can export CMS, Ecommerce and User data separately as CSV, but as raw data, not functioning features.

Does Webflow lock me in?

Less than most builders for design, more for data. Your markup and styling are fully portable via code export, so you are not tied to Webflow hosting for a static site. But if your value is in a large CMS, a store or memberships, that dynamic layer is hosting-locked and comes out only as raw CSV.

Will my redirects carry over when I migrate?

Yes. Webflow imports 301 redirects from a CSV up to 16MB, so you can bring your old URL map over in one file. Note that a new import overwrites all existing redirects rather than merging, so keep every rule in a single master CSV.

Sources & verification

Verified by ComparEdgeMethod: Vendor docs, official pages, and selected independent sources

Source	What was checked	Last checked
Webflow Official	Official product page	July 10, 2026
Webflow Hosting	Hosting	July 10, 2026
Webflow Support	Articles 33961193662739 Migrate Your Site From Wordpress To Webflow	July 10, 2026
Webflow Support	Articles 33961211526291 Import Export 301 Redirects	July 10, 2026
Webflow Support	Articles 33961386739347 How Do I Export My Webflow Site Code	July 10, 2026

Every fact on this Webflow page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.