Webflow to WordPress: what the export carries, and the alternatives.

What transfers from Webflow to WordPress, and what does not?

Your exported HTML, CSS, and JavaScript transfer as static files, and your CMS Collections export as CSV. Server-side features stay behind. Your code export leaves out CMS content and dynamic logic, User Accounts, Ecommerce, form submission processing, site search, reCAPTCHA elements, password protection, and code components. And locales need attention. If your site has locales, you get only the primary one.

Expect empty states. You see them where your Collection lists were, because your Collection pages drop anything bound to Collection fields. You cannot export part of a site, so you get every exportable file on each run. Your component classes carry a "w-" prefix, and your manual edits can break Webflow components (a quiet way to lose an afternoon). Forms need new handling. Your forms need a new backend handler, though you can export past submissions separately. Treat your export as a reference build of your design, then rebuild it as WordPress theme templates you host yourself.

How do you plan the URL map and redirects so your search traffic survives?

Plan the move carefully. You map every old URL to a single replacement URL, then serve permanent server-side redirects before launch. Google treats URL path changes as site moves, so migrating to WordPress counts even if your domain stays the same. Keep the path clean. Use 301 or 308 status codes, avoid redirect chains, and keep redirects live for at least a year. A year is the floor, not the target.

Your Webflow 301 table exports as a CSV, giving you a baseline list of old paths. Webflow's generated sitemap.xml gives you a second list to audit against. If your slugs change, WordPress needs exact rewrite rules or pattern matching, and you test each path before updating DNS records. Check the new site closely. After launch, you check canonical tags, noindex rules, and robots directives on the new site, and you monitor traffic across old and new URLs. And where your host cannot redirect, a canonical tag is only a hint.

How is content moved from Webflow: export, API or crawl?

You migrate content by exporting CSV files for CMS Collections and crawling pages that exist only as rendered HTML. Do both. You export each Collection as a CSV, which includes archived items when you export the entire Collection, but only for the locale currently open in your view. Your CSV carries an Item ID for matching records during re-import, but restoring a backup from before March 25, 2024 assigns brand-new IDs to every item (so any matching you built on the old IDs breaks).

In WordPress, you map CSV headers to database fields, or you lose data. Field mapping is not optional. WP All Import parses CSV, XML, and Excel files, but the free version only creates new posts, so you need the pro version to update records you have already loaded. Webflow's own migration walkthrough found relative image paths and unsanitized rich text breaking imports, so expect those same defects in your own files. For your largest Collections, fetching records through the API fits better, though you should verify rate limits before you begin. Nobody enjoys a throttled import at midnight.

What do your editors get on WordPress compared with Webflow?

Your editors get a self-hosted WordPress dashboard with posts, pages, custom post types, and plugins. They lose Webflow's visual canvas. Your CMS Collections become custom post types, and your Collection fields become custom fields and taxonomies, which tools like WP Ultimate CSV Importer Pro populate from your header mappings. So you lose on-canvas editing, and you decide whether developers or editors handle layout updates going forward.

You also take on hosting, software updates, and plugin maintenance that Webflow handled behind the scenes. That work moves to you, and it never fully goes away. Your sitemap, page titles, and Open Graph tags, which Webflow generated per page and CMS item, now depend on theme files and plugins, so you check raw public HTML. Your team controls the code and the server, but you trade away the visual editor and the managed infrastructure.

How long does a Webflow to WordPress migration take, and what drives the effort?

Your timeline depends on technical factors, not an arbitrary calendar estimate: URL count, content types, media assets, integrations, and locales. Count the work first. Your URL count sets the size of the redirect table and parity audits, and Google advises moving large sites in sections. Your content types determine how many custom post types and custom fields you configure, while your media volume determines how many image URLs you rewrite.

Your integrations carry the hidden work. You rebuild form handling, site search, User Accounts, and Ecommerce, because none of them leave Webflow in the export. Each locale requires its own CSV download, since you export only your active locale view, alongside hreflang audits and a redirect set per language. You can run the free assessment on your homepage and sampled pages first: it shows you your script weight and image weight. It also shows structured data, and the archive read shows how many unique pages and images are archived for your site, plus PDFs.

When should you not move from Webflow to WordPress?

You should not move when your plan costs fit, your CMS limits leave you headroom, and nobody on your team wants to patch and maintain a server. Staying can be right. Your May 2026 Webflow plan change merges CMS and Business Site into a Premium plan at $25 a month yearly, with 20,000 CMS items, so your costs may be lower than you think. If your site is on legacy pricing or in a Freelancer or Agency Workspace, you see the new price at your renewal on or after November 16, 2026.

I plan and run migrations like this, moving legacy setups to Astro and Next.js, while WordPress development goes to agency partners. The stack matters. If you run a marketing site, Astro with a headless CMS serves you better than WordPress: you get static pages, though your editors give up a visual canvas and plugins. But choose Next.js with Sanity or Contentful when you run web applications, personalized content, or large editorial teams; your team gives up a hosted admin.

Questions, answered.

Your next read.

1. 01Webflow alternativesWhere the limits bite and what replaces it.
2. 02WordPress alternativesStay, go headless or move: judged by your pages.
3. 03Astro SEO checkIslands, content collections, schema, vitals.