So, in the past few weeks several business owners asked me the same question: “Can we move our site off Webflow to WordPress?”
Not a coincidence. In May 2026 Webflow restructured its pricing — merged two plan tiers into one, changed how bandwidth is counted, added AI credits into the bill. For some sites the new math works out fine. For others the monthly cost went up, and the owners started doing what owners do: asking what it would take to leave.
Short answer: yes, you can move. But the move is bigger than most people expect, and the reason is worth understanding before you decide anything.
Price is the trigger, rarely the whole reason
One of my clients recently wrote an internal memo to convince management to move. The pricing barely featured in it. What featured instead — and this matches what I hear from others — was a list of ceilings the team kept hitting:
- No real staging. Changes in Webflow happen on the live site’s designer and then get published. There’s no proper dev/staging environment where you test before anything touches production. For a simple brochure site that’s fine; once the site is business-critical, it becomes a source of incidents.
- Relational content limits. CMS collections work well until the content structure gets complex — multi-level references, filtering by several criteria, dynamic structures. Then the workarounds start.
- Gated content and membership — possible, but through third-party tools stitched on top.
- Marketing stack integrations. HubSpot, Salesforce, Marketo, analytics, personalization — most of these connect to WordPress natively through plugins and SDKs. On Webflow the same connections often run through Zapier, Make, or custom JS. Each extra link in that chain is something that can break.
The client’s own summary was the sharpest version: “a lot of basic things need R&D on Webflow, where in WordPress they’re just natural.” That’s the moment the platform stops fitting — not when the invoice arrives, but when routine tasks turn into projects.
None of this makes Webflow bad. It makes it a tool with a defined shape, and businesses sometimes grow past the shape.
The export button doesn’t do what you think it does
Webflow has a code export feature. People assume it means “I can take my site and go whenever I want.” That assumption is worth checking before you rely on it.
What the export actually gives you: static HTML, CSS, and JavaScript files. A snapshot of your pages.
What it doesn’t give you:
- Your CMS content as working dynamic pages — blog posts, case studies, product listings, team pages. The structure that generates them stays on Webflow.
- Your forms. They stop working the moment they leave Webflow’s hosting.
- Site search.
- Localization, if you use it.
- E-commerce data, if you sell anything.
In other words: the export gives you the brochure part of the site. The parts that made you pick Webflow in the first place — the dynamic parts — don’t come with you.
This isn’t Webflow being sneaky. It’s how all-in-one platforms work: the convenience and the lock-in are the same feature, viewed from two sides. You just want to know which side you’re standing on before the renewal notice arrives.
What a real migration involves
A Webflow → WordPress migration is not “press export, press import.” It’s a rebuild with your existing site as the specification. The honest list:
- Content model mapping. Webflow CMS collections become WordPress custom post types and fields. This is the architectural part — get it wrong and you’ll be fighting your own site for years.
- Content transfer. Collections export to CSV, which covers the text. Images, rich-text formatting, and references between collections need handling one by one. This is where the tedious work lives.
- Design rebuild. The exported HTML/CSS can serve as a reference, but a maintainable WordPress site is built as a proper theme, not as pasted static files.
- URL and redirect map. Every old URL gets a 301 to its new home. Skip this and your Google rankings pay the bill for the whole migration.
- Forms, integrations, tracking. Everything that touched Webflow’s infrastructure gets rewired.
- Testing before switching DNS. The old site keeps running until the new one is verified. Nobody should notice the move except you.
Done properly, visitors and search engines see the same site, just served from infrastructure you own.
When you should NOT migrate
Not every Webflow site should move. A few honest cases:
- If your site is small, mostly static, and the new pricing didn’t hurt you — stay. Migration costs more than a year of hosting fees, and you’d be solving a problem you don’t have.
- If your marketing team lives in the Webflow Designer and ships landing pages weekly without a developer — that workflow has real value. Price it before you give it up.
- If the only complaint is one specific limit, sometimes there’s a narrower fix than a full platform move.
Migration is a project, not a fix. It should solve a structural problem, not a bad month.
What you get on the other side
The case for moving isn’t that WordPress is “better.” It’s about what you own afterwards:
- The code is yours, on hosting registered in your name.
- The content lives in your database. Exportable, backupable, portable.
- Proper staging and development environments — you test changes before they touch the live site, not after.
- No per-item limits, no bandwidth tiers, no plan restructuring that lands in your inbox as someone else’s decision.
- Costs shift from a growing platform subscription to hosting (modest) plus development when you actually need something.
WordPress has its own maintenance obligations — updates, security, hosting choices. That’s the trade: platform convenience for ownership. Some businesses are at the stage where ownership matters more. Usually it’s the ones who just got a renewal email they didn’t like.
Before you decide
Whatever you do, don’t start with a quote. Start with an inventory: what’s in your CMS, which integrations exist, what the URL structure looks like, and whether anything can be simplified during the move instead of copied as-is. Half the migration cost hides in that list, and you can build most of it yourself in an afternoon.
Let’s see how this wave develops. My guess is these pricing resets won’t be the last ones…
