By Mehdi HassanShould you migrate from WordPress at all?
You should migrate from WordPress when the platform costs you more in maintenance, speed or editing friction than it gives you in flexibility. If your site works, your team edits it happily and plugins run important parts of the business, staying is often the better call.
WordPress is open source, runs a large share of the web and has a plugin for almost everything. That flexibility is also the reason teams leave: plugin updates, security patches, theme conflicts and page builders that slow pages down. The question isn't whether WordPress is good. It's whether your site still needs what only WordPress gives you.
Our guide to the signs you've outgrown WordPress covers this honestly, including the signs you haven't. If you're still unsure after reading it, the rest of this guide helps you pick where to go.
Sign | Points to leaving | Points to staying |
|---|---|---|
Who edits | Marketers wait on a developer for small changes | Editors are fluent in your WordPress setup |
Maintenance | Plugin and theme updates break things regularly | Updates are managed and rarely cause problems |
Speed | Page builder output stays slow after optimization | Pages are already fast in real-user data |
Plugins | You use a handful of simple plugins | Membership, LMS, ecommerce or booking plugins run the business |
Content | A marketing site with a modest blog | Thousands of posts with complex taxonomies and workflows |
Where should a business move its site when leaving WordPress?
A business leaving WordPress should move to the platform that fits its team, content volume and integrations. In practice that's one of four destinations for a marketing site: Framer, Webflow, a code build in Next.js or Astro, or WordPress kept as a headless CMS behind a new front end.
Platform loyalty is the wrong starting point. We build in Framer, Webflow and Next.js, so we have no reason to push one. What we've learned is that the right choice comes from three questions, not from feature lists.
- Who will edit the site every week? Marketers, developers or both.
- How much structured content is there? A few dozen pages, or hundreds of posts, case studies and resources with references between them.
- What does the site connect to? Forms and analytics only, or logins, product data, pricing logic and custom APIs.
Destination | Best for | Watch out for |
|---|---|---|
Framer | Page-led marketing sites edited by designers and marketers who want speed | CMS limits and fewer relational CMS features |
Webflow | CMS-heavy sites with blogs, resources and case studies edited visually | Plan limits and pricing changes; check the current plan page |
Next.js | Sites with product logic, scale, custom integrations or a design system | Needs developers for changes and ongoing maintenance |
Astro | Content-heavy sites that want static speed and developer control | Developer-led editing unless paired with a CMS |
Headless WordPress | Teams that love the WordPress editor but want a modern front end | Plugin rewrites, preview and two systems to maintain |
Shopify | Stores moving off WooCommerce | Different data model and app ecosystem |
The comparison of Webflow, Framer, WordPress and Next.js for marketing sites goes into each platform in more depth. The sections below give the decision tree and point to the detailed guide for each route.
When is Webflow the right move from WordPress?
Webflow is the right move from WordPress when you have a meaningful amount of structured content and want non-developers to manage it visually. Its CMS handles collections, reference fields and templates well, and its designer gives fine control over layout without code.
Webflow suits B2B sites with a blog, case studies, resource libraries or integration directories, where content types relate to each other. It also suits teams that want hosting, security and updates handled for them, which removes most of the maintenance burden WordPress carries. Webflow merged its CMS and Business site plans into a Premium plan in May 2026 with a 20,000-item CMS limit, according to our research, so check the current plan page for your item count.
- Read our SEO-safe WordPress to Webflow migration guide for the URL mapping and launch steps.
- See WordPress to Webflow migration cost for pricing by site size.
- Moving a big blog? Use how to migrate a WordPress blog to Webflow CMS for posts, authors and categories.
- Want to see the process end to end? Read our hypothetical WordPress to Webflow walkthrough.
When is Framer the right move from WordPress?
Framer is the right move from WordPress when the site is mostly designed pages, the team wants to ship changes fast, and motion and visual polish matter. Framer feels closer to a design tool than a CMS, which is why designers and marketers often pick it.
The trade-off is CMS depth. Our research notes Framer's CMS has item and collection caps (sources disagree on the exact numbers) and no multi-reference fields, so very large or relational content libraries can hit limits. A startup site with a product story, pricing, a careers page and a modest blog usually fits comfortably. A publisher with thousands of interlinked posts usually doesn't.
- Our WordPress to Framer migration guide compares the import plugins and CSV route.
- WordPress to Framer migration cost and timeline gives a week-by-week plan.
When is Next.js worth it when leaving WordPress?
Next.js is worth it when the site carries product logic, needs to scale to many pages or integrations, or should share a design system with your app. For a brochure site, it's usually more power and more maintenance than you need.
A code build gives you full control over performance, rendering, data fetching and integrations. It also means every new layout, and many content changes unless you add a CMS, goes through a developer. Pair Next.js with a headless CMS like Sanity or Payload if marketers need to publish on their own.
- Our WordPress to Next.js migration guide explains when it pays off and when Astro or Framer is cheaper.
- For content-heavy sites that want static speed, see WordPress to Astro migration.
What about headless WordPress?
Headless WordPress keeps WordPress as the editing back end and puts a modern front end, often Next.js, in front of it. It's a good fit when your editors are deeply invested in WordPress workflows and you want better speed and design freedom on the front end.
It isn't the cheap middle path it's often sold as. Many plugins that render on the front end stop working and must be rebuilt, previews need extra setup, forms move to a separate service, and you now maintain two systems. Agencies in our research quoted £13k to £30k and 6 to 12 weeks for a WordPress to headless Next.js move, and ranges vary widely.
Pros
- Editors keep the WordPress interface and workflows they know.
- The front end can be fast and fully custom.
- Content stays in place, so there's less to import.
Cons
- Front-end plugins (forms, SEO output, sliders, page builders) need replacing.
- Previews and draft workflows take extra setup.
- You maintain WordPress hosting, security and the front end.
Read headless WordPress with Next.js for the hidden costs in detail before you commit.
How do you migrate from WordPress without losing SEO?
To migrate from WordPress without losing SEO, inventory every URL, keep slugs identical where you can, map every changed URL to a permanent redirect, and carry over titles, descriptions and structured data. URL structure is the main risk, because WordPress often adds category prefixes or dates to post URLs.
Export and inventory
Export posts, pages, media and taxonomies, and crawl the live site so you catch archives, attachments and old URLs. Our guide to exporting WordPress content covers the options.
Audit the content
Decide what to keep, merge, rewrite or retire, using traffic and backlink data.
Model the new CMS
Define collections and fields for posts, authors, categories and any custom post types before importing.
Match URL patterns
Recreate existing slugs where the platform allows; where it can't, such as date-based paths, plan redirects.
Build the redirect map
One row per old URL with its new destination, reviewed by someone who knows the content.
Replace plugins
List every plugin and decide its replacement, rebuild or removal.
QA and launch
Test templates, metadata, forms, analytics and every redirect, then monitor Search Console daily.
Forms are where leads go missing. Contact Form 7, Gravity Forms and similar plugins need a replacement wired to your CRM and tested end to end; see migrating forms and lead capture. Our website redesign checklist has the full launch list.
Which WordPress plugins will you need to replace?
You'll need to replace every plugin that adds a feature visitors or editors rely on: SEO, forms, redirects, caching, sliders, galleries, popups, membership and multilingual tools. Some become built-in platform features, some need a third-party service and some you can drop.
Plugin type | In Webflow or Framer | In Next.js |
|---|---|---|
SEO (titles, schema, sitemaps) | Mostly built in; schema via custom code | Built in code with framework metadata APIs |
Redirects | Platform redirect settings | Config or middleware redirects |
Forms | Native forms or an embedded form tool | Form service or custom API route |
Caching and performance | Not needed; hosting handles it | Handled by the framework and host |
Multilingual (WPML, Polylang) | Platform localization or a translation tool | i18n routing plus translated content |
Membership or ecommerce | Often a separate service | Custom build or a dedicated platform |
Our full list of WordPress plugins to replace maps common plugins to their equivalents. For translated sites, read moving WPML or Polylang sites before you choose a platform, because localization pricing and structure differ a lot.
Special cases: WooCommerce, Multisite and moving back
WooCommerce stores are a different migration. You're moving products, variants, customers and orders, not just pages, and Shopify is the usual destination for smaller brands; see WooCommerce to Shopify migration.
WordPress Multisite networks often hold many brand or regional sites. Consolidating them into one site on a new platform can simplify things a lot, but the URL mapping grows with every site; see WordPress Multisite to Webflow or Next.js.
And sometimes the right move is the reverse. If you left WordPress and miss plugins and full control, read Webflow to WordPress: when moving back is right.
How much does it cost to migrate from WordPress?
The cost to migrate from WordPress depends on unique templates, CMS content, plugins to replace, languages and integrations. Our research found agencies quoting $1.5k to $25k for migrations depending on size, with headless WordPress rebuilds quoted higher, and prices vary widely.
Designify works at fixed prices. Our website package is $8,000 for up to six pages plus $500 per extra page, with custom design, a CMS and animation, built in Next.js. Migration work such as content import and redirects is scoped on the intro call, and we include redirects and SEO checks in any migration we take on.
- Website: up to 6 pages, custom design, Next.js, CMS
- $8,000
- Per extra page beyond six
- +$500
- Trial week before committing
- $1,000
- Range of migration quotes in our research, by size
- $1.5k–$25k
For destination-specific numbers, see the WordPress to Webflow and WordPress to Framer cost guides.
Who should run your WordPress migration?
Have the migration run by someone who builds on the destination platform and treats SEO as part of the job, not an add-on. The build is the visible part; the URL inventory, redirects, plugin replacements and launch QA are what protect your traffic.
Look for a provider who asks about your editors and integrations before recommending a platform, sends a URL inventory and redirect map with the proposal, and is clear about who owns the site afterward. Our guide to hiring a Webflow or Framer migration agency lists the questions to ask, and the website design process explains what each stage should produce.
If your site has to persuade both technical evaluators and business buyers, plan that into the rebuild rather than bolting it on later; see selling to technical and non-technical buyers on one page.
