How to Move a Webflow Site to WordPress
Webflow lets you export your code, but not your site: the export leaves out the CMS content, the forms and the translated pages, and there is no export to WordPress. This guide shows how to move a Webflow site to WordPress: your AI agent, connected to WordPress through Fabrement, rebuilds the design as native Gutenberg blocks, fills post types from Webflow’s CSV exports, and keeps the addresses and SEO, so the site keeps its search history after the switch. If you are still deciding, the short version is on our Webflow alternative page, and the platforms are compared on Webflow vs WordPress.
Key takeaways
- There is no official Webflow to WordPress converter. Your AI agent rebuilds the design as native Gutenberg blocks with editable fields, on one design system, from the live site or from Webflow’s code export.
- Code export needs a paid Workspace plan, and it holds static pages only: no CMS content, forms, site search, password protection or translated pages.
- CMS Collections export as CSV, one file per Collection and per language. Images come as links to Webflow, so they are copied into your media library before the Webflow site goes offline.
- Keep every address. Collection items live under paths such as /blog/your-post. WordPress can keep them, and Webflow’s existing 301 redirects export as a CSV too.
- Switch the domain before you cancel. Cancelling a Webflow site plan unpublishes the site at the end of the billing period.
Hand this to your AI first: fabrement.com/AGENTS.md. One link, and your agent knows what Fabrement can do on your site and how to connect to it.
Requirements
| What | Needed |
|---|---|
| Hosting | Webflow includes hosting, WordPress does not. Choose a host first and install WordPress there. |
| WordPress | WordPress 6.9 or newer with HTTPS, and Fabrement installed and signed in. |
| PHP | PHP 8.0 or newer for the plugin. Use 8.2 or newer: older branches no longer get security fixes. |
| AI agent | Claude, ChatGPT, Codex or Cursor, connected to the site over MCP. Step by step: Claude, ChatGPT, Codex, Cursor. |
| The Webflow site | Still published, and access to the project. Keep the site plan active until the domain has switched. |
| Code export (optional) | A paid Workspace plan, if you want to hand the agent the exported HTML and CSS as well as the live site. |
| AI plan | Enough usage for a long session. A whole site is several hours of agent work. |
The steps
1. Map the Webflow site
Before anything is built, ask the agent to list every static page and every Collection item with its address, SEO title and description. Webflow publishes a sitemap at your-site.com/sitemap.xml, so the agent can start there. Each Webflow Collection becomes its own post type in WordPress, with the same fields. Export your existing 301 redirects too: in Webflow they live in Site settings → Publishing → 301 redirects and download as a CSV.
2. Get the content out of Webflow
- CMS Collections. Export each Collection as a CSV from the CMS panel. Rich text comes out as HTML, references as text, and multi-references as a comma-separated list. On a site with several languages, export once per locale.
- Images and files. In the CSV they are links to Webflow’s servers, including the images inside rich text. The agent uploads them into your WordPress media library and rewrites the links, so nothing breaks when the Webflow site goes offline.
- The code export, if your plan has it. It gives the HTML, CSS and images of the static pages. Collection pages come out empty, but the export is a good reference for the agent: the same classes, spacing and breakpoints the designer used.
- Form submissions. Export earlier submissions from Webflow if you need them: they do not come with the site.
3. Give the agent the address and the request
Start a new session with your connected agent, and attach the CSV files and the code export if you have them. An example request:
I have a Webflow website at https://your-site.com. Rebuild it on this WordPress site.
The design stays the same: build a design system from the site's colours, fonts and buttons, one header and footer, and a native block for each section with fields the team can edit. Use the attached code export as a reference for spacing and breakpoints.
Create a post type for each CMS Collection, with the same fields, and fill it from the attached CSV files. Upload every image to the media library, including the ones inside rich text.
Keep every address, including the Collection paths such as /blog/, and add a 301 redirect for any address that has to change. Import the redirects from the attached CSV. Copy every SEO title and description word for word.
Before you start, check the website and tell me what you understood. Keep new pages as drafts. Check every page on desktop and mobile against the live Webflow site, and finish with a report: what you built, your decisions, and what could not be carried over and why.
4. Replace what Webflow ran for you
Some things work only on Webflow hosting, so the WordPress site sets them up itself. Forms are rebuilt with Contact Form 7, or placed from WPForms, in the site’s design. Webflow Interactions run on Webflow’s own scripts: the important animations are rebuilt in the blocks’ own CSS and JavaScript, so ask the agent for a list first and decide which are worth keeping. Site search, password-protected pages, translations (Webflow Localize, moved to WPML) and a Webflow store (moved to WooCommerce) each need their own plan, and analytics and tracking codes move across as scripts.
5. Review, then switch the domain
Read the agent’s report first: it lists every decision it made and every gap. Check the drafts on desktop and mobile, compare them with the live Webflow pages, then publish. Point the domain at your new host, and only then cancel the Webflow site plan: cancelling removes the custom domain and unpublishes the site at the end of the billing period. After the switch, submit the new sitemap in Google Search Console and watch for addresses that return 404.
After the move: run the site with your AI agent
Once the move is done, the same MCP connection keeps working. You manage the site by asking your AI agent in plain language: pages built from the blocks you already have, Collection items as posts, texts and images, menus, SEO titles and descriptions, redirects, and new sections from a screenshot. New pages wait as drafts, and every block change can be rolled back. Your team edits the same blocks in the WordPress admin whenever they prefer, and adding an editor does not add a seat to the bill.
Fabrement: the workplace for your AI agent
A free plugin for WordPress 6.9 or newer. Connect your AI agent over MCP, and do all of this on your site from its chat.
What comes over, and what stays in Webflow
The design comes over as a custom WordPress theme: a header, a footer and a native Gutenberg block for every section, with real fields, on one design system. Static pages, Collections and their items become WordPress pages, post types and posts the team edits in the block editor, with their addresses and SEO titles kept. What stays behind are the things that run only on Webflow: its forms backend, site search, Interactions as they were built, Localize and the Webflow store, each replaced on the WordPress side.
Other sources work the same way: Wix to WordPress for a Wix site, HTML to WordPress for static sites and code exports, and Lovable to WordPress for a Lovable project.
Frequently asked questions
Is there a Webflow to WordPress converter?
There is no official one: Webflow has no WordPress export. Third-party tools such as Udesly turn Webflow’s exported code into a WordPress theme, which needs the code export of a paid Workspace plan. With an AI agent and Fabrement, the design is rebuilt as native Gutenberg blocks with editable fields, and the CMS content comes over from Webflow’s CSV export.
Can I export my Webflow site?
Partly. On a paid Workspace plan you can export the HTML, CSS, JavaScript and images, but not the CMS content, forms, site search, password protection or translated pages. CMS Collections export separately as CSV files, one per Collection and per language.
Will my Webflow forms work on WordPress?
Not as they are: Webflow forms work only on Webflow hosting and stop working in exported code. On WordPress the agent rebuilds them with Contact Form 7 in the site’s design, or places a WPForms form, and they send email from your own site. Export earlier submissions from Webflow before you cancel the plan.
Will I lose my Google rankings when I leave Webflow?
Not if the addresses stay the same. Map every page and CMS item first, keep the same paths, for example /blog/your-post, copy the SEO titles and descriptions, and add a 301 redirect for any address that has to change. Webflow can export your existing redirects as a CSV, so they can move too.
What happens to Webflow Interactions?
They don’t move on their own. Webflow’s animations run on Webflow’s own scripts, so on WordPress the important ones are rebuilt in the blocks’ own CSS and JavaScript. Ask the agent for a list of every animation first, and decide which ones are worth keeping.
How much does it cost compared with Webflow?
The Fabrement plugin is free, with a free Fabrement account, and the agent runs on your own Claude, ChatGPT, Codex or Cursor plan. You pay for WordPress hosting instead of a Webflow site plan, with no CMS item limits and no per-editor seats. Webflow site plans with a CMS start at $25 a month billed yearly.
Sources
Webflow facts were checked on 19 November 2026 against Webflow’s help center: code export, CMS Collection export, 301 redirects and cancelling a site plan, and its pricing page. Fabrement steps come from our own AGENTS.md, and follow the same workflow as our Wix and HTML rebuilds. If a step has changed, tell us and we will correct it.