Every WordPress migration quote I have written starts the same way. Someone sends a plugin list, and I send back a question: which of these is the business?
That answer decides everything downstream. A site where the plugins are decoration moves in a fortnight. A site where one plugin is quietly running bookings, or invoicing, or a members area, is not a migration at all. It is a rebuild wearing a migration's clothes, and the two get priced as though they were the same job.
Should You Leave WordPress at All This Year?
Leave WordPress when its plugin surface costs more to maintain than the platform saves you, not because you heard the project had stalled.
It has not stalled. WordPress 7.1 shipped on 19 August 2026, on the closing day of WordCamp US, carrying client-side media processing: the browser now resizes an image before the upload ever reaches your server. The same release stabilized the Tabs and Playlist blocks and let you style :hover and :focus states from theme.json without writing CSS, per WordPress's own developer news. Version 7.2 is projected for 10 December on the public roadmap, which makes three majors in one calendar year after an earlier announcement had promised only one.
Half the migration sales pages you will read are still arguing against a WordPress that stopped existing around 2021.
The reasons that hold up are duller and more specific. Your update cycle has become a risk event rather than a chore. Nobody on the team can safely touch the theme because the person who built it left. Your hosting bill has a security add-on line item that exists purely to compensate for the plugin surface. Friday afternoon, a plugin update lands, and the checkout page comes back blank white with a 500 in the log while you page through wp-content looking for what changed.
How many of your active plugins could you name from memory right now? If the answer is under half, the maintenance argument has already been made for you.
Webflow or Custom Code: Picking the Exit
Webflow fits content sites where marketers must publish without a developer; custom code fits anything where the page is a product surface rather than a document.
The pricing under that choice moved this year, which matters because most migration tutorials still quote the old plans. Webflow restructured on 13 May 2026, documented in its own pricing update. The change people keep getting wrong: the $15 Basic plan carries no CMS at all, just 300 static pages. A blog needs Premium. Premium in turn absorbed the old item add-ons and now carries 20,000 CMS items across 40 Collections at $25 per month billed yearly, as The Small Square's 2026 breakdown of Webflow's CMS caps sets out.
| Exit path | Recurring cost | Who publishes content | Fits when |
|---|---|---|---|
| Webflow Premium | $25/mo billed yearly | Marketers, in the Webflow Editor | Content and marketing site, no server-side logic |
| Webflow Team | $2,500/mo | Marketers, with 10 seats and 100 Collections | Multiple brands or locales under one roof |
| Next.js plus Payload or Sanity | Build cost, then hosting | Marketers, in a headless studio | Programmatic pages, app-adjacent features, owned data |
| Trim WordPress instead | Existing hosting | Same as today | The plugin count is the problem, not the platform |
That last row is a real option and it gets skipped because nobody sells it. If your site is a hundred pages of content and thirty plugins, deleting twenty plugins is cheaper than any migration on this table and fixes the same pain.
Actually, let me qualify that. It fixes the maintenance pain. It does nothing for the editing experience, and if your marketing team has been waiting three weeks for a landing page, no amount of plugin pruning changes that queue.
For the fork between a hosted editor and a bespoke build, WordPress versus a custom website build covers the trade in more depth than a table row can, and my rundown of the best CMS platforms for marketing sites explains where each content model genuinely wins. If you want the wider field rather than these four, the WordPress alternatives worth shortlisting is the longer list.
What Actually Breaks During the Move
Redirect maps cover the URLs you remember to list; they never cover the links your content contains.
This is the failure that shows up in Google Search Console six weeks after launch, long after everyone has stopped watching. Every internal link an author ever typed into a WordPress post body ships across in the CSV as a raw href pointing at the old path. Nothing rewrites them. They land inside a Webflow Rich Text field looking perfect in the Designer and returning 404 to anyone who clicks, which Enaks documents as one of the recurring SEO failures in this exact migration.
Two more things arrive broken and quiet.
URL structure is the first. WordPress permalinks are arbitrary, so a site can serve /category/post-name/ or /2019/06/post-name/ or anything an editor invented in 2014. Webflow Collections generate a standardized pattern keyed to the collection slug. You cannot reproduce the old shape. You can only redirect to the new one, which means the redirect map is not an optional tidy-up at the end. It is the migration.
Schema markup is the second. Whatever your SEO plugin was emitting as JSON-LD stops existing the moment the plugin does, and Webflow will not regenerate it. Every template needs the markup added back by hand as a custom code embed. Rich results vanish quietly, and nobody notices until an FAQ block stops appearing in the SERP.
I hit a milder version of this working the CMS side of a Webflow fitness blog. The site was a collaborator's build and I owned the editorial and publishing. Publishing through someone else's collection schema means respecting their SEO fields and layout constraints rather than redesigning mid-stream, and the constraints you inherit on day one are the ones you live with for a year.
Keep the Old Site Alive
Do not cancel the WordPress hosting on launch day. Keep it running, unpublished but reachable, for at least ninety days.
You will need it to diff a page that renders wrong, recover an image nobody exported, or read a meta description that never made it across. Ninety days of shared hosting is the cheapest insurance in the project.
How Do You Migrate Without Losing Rankings?
Export the URL inventory before anything else, map every live URL to its destination, and launch the redirects in the same deploy as the site.
The order matters more than the tooling:
- Pull the full URL inventory from Search Console, your sitemap, and a crawl of the live site. Three sources, because each one misses different pages. Archives, tag pages, paginated series, and author pages are where the gaps hide.
- Record the title tag, meta description, and canonical for every URL that earns traffic. None of it migrates by itself.
- Build the content in the new platform with those fields populated as you go, rather than as a cleanup pass afterward.
- Rewrite in-body internal links to the new paths. Search the exported post bodies for your own domain and for href="/ and fix every hit.
- Re-add JSON-LD per template as custom code.
- Ship redirects with the launch, not after it. A 404 that lives for a weekend costs more than a redirect that was ready on Thursday.
- Watch Search Console coverage weekly for two months. Recovery on a clean migration usually settles inside eight to twelve weeks, and a redirect you missed shows up as a crawl error long before it shows up as lost traffic.
Budget for the transition window rather than pretending it does not exist. If you need the numbers behind that budget, what a website build actually costs is the honest version, and the practical advice for running a website project covers the process discipline that keeps a migration from sprawling.
What Replaces the Plugins?
Nothing replaces them one for one, and the sooner that is priced in, the better the migration goes.
Contact forms and basic marketing automation port fine. Both Webflow and a Next.js build handle those natively or through a service you were probably already paying for. The trouble is concentrated in the plugins that hold state. Bookings, membership tiers, order history, invoices, anything with a database table of its own.
Those become one of three things: a SaaS tool you subscribe to, a service you integrate, or code you own. Pizzeria Bestek is the third answer taken to its conclusion. The restaurant had been renting its ordering flow from an aggregator, and after the rebuild on React and Supabase it owns every credential and keeps 100% of each order instead of roughly 70% after commission. The system has been running since September 2025.
That is the real question underneath a WordPress migration. Not which platform, but which parts of your business you are willing to keep renting.
Open Search Console, sort your pages by clicks, and export the top fifty URLs. If more than a handful of them live at a permalink structure Webflow cannot reproduce, you have just found the first line item in the quote, and you found it before anyone paid for a discovery call.
