WordPress still runs a huge share of the web, and for plenty of teams it is the right home. But a lot of marketing sites end up in the same place: thirty plugins, a theme nobody wants to touch, a page builder that slows every page, and a marketing team that files a ticket to change a headline. At that point the platform is no longer free. You are paying for it in developer hours, security patches and campaigns that launch late.
This guide is for the moment you start asking whether to leave. It covers why teams move, the signs that it is time (and the signs that it is not), the destinations worth considering, a step by step migration plan, how to keep your rankings with a proper redirect map, how to get your content out, what it costs, how long it takes, the mistakes we see most and a checklist you can work through. We are a website design and development studio, not an agency for any single platform, so the advice is about fit rather than a sales pitch for one tool.
Why Teams Leave WordPress
Nobody leaves WordPress because of the logo. They leave because the cost of running the site has crept up until it outweighs the cost of moving. These are the reasons we hear most often from marketing and founding teams.
Plugin debt. Every feature arrived as a plugin: SEO, forms, caching, sliders, redirects, custom fields, security, backups. Each one updates on its own schedule, some conflict with each other, and a few were abandoned years ago. Updating anything feels risky, so updates get skipped.
Security and maintenance. A public admin login, a database and a long plugin list make WordPress a common target. Someone has to apply core, theme and plugin updates, watch for vulnerabilities and restore backups when something breaks. On many teams that someone is a contractor billed by the hour.
Speed. Page builders, heavy themes and stacked scripts add weight to every page. Caching plugins help, but they treat the symptom. Slow pages hurt conversion and make it harder to pass Core Web Vitals.
Editing friction. The block editor, a page builder and a set of custom fields often live side by side. Marketers either avoid editing or break layouts when they try. New landing pages wait for a developer.
Design drift. Years of quick fixes leave a site that no longer matches the brand or the product. A rebrand on top of an old theme is often harder than building fresh.
The company has changed. A raise, a launch or a press moment puts more eyes on the site than ever before, and the site has become the weakest part of the story.
If two or three of these sound familiar, it is worth working through the rest of this guide. If none do, you probably do not need to move.
Signs It Is Time to Leave, and Signs You Should Stay
A migration is a rebuild plus a content move plus a redirect map. It is real work, so it should solve a real problem. Use these two lists honestly.
Signs it is time to leave
Your marketing team cannot publish a new page without a developer.
Plugin or theme updates regularly break something, so updates are put off.
You have had a security scare, or you pay someone each month mainly to keep the site patched.
Page speed is poor even after caching and image work, because the theme or builder is the bottleneck.
A rebrand or repositioning is coming and the current theme cannot carry it.
You are spending more on upkeep than on improving the site.
Signs you should stay
The site is stable, reasonably fast and your editors are quick in it.
You run a large WooCommerce shop or a membership system that would be expensive to replace.
You publish at high volume with a mature editorial workflow that works.
The problems are specific (a slow template, broken redirects, poor metadata) rather than structural.
If you are in the second group, a Tune-Up is often the better answer. It is a fixed $5,000 technical pass on the platform you already have, covering things like speed, redirects, metadata and indexing. Staying can be the cheaper, honest choice. If the platform itself is the problem, a Tune-Up will not fix that, and a migration is the next conversation.
Where to Go: Your Options Compared
The destination matters less than one question: who will edit the site after launch, and how? Answer that first and the shortlist gets short quickly. Here is how the main options compare for a marketing site.
Framer
Framer is a visual website builder with a built-in CMS, hosting, localisation and animation. It suits teams where a marketing lead or designer needs to ship pages on a canvas without engineering. Builds are fast and editing is genuinely easy once the site is set up as a component library. It is not built for ecommerce checkouts or very large, deeply related content models. Read Framer vs WordPress for the full comparison, then the WordPress to Framer route or the step by step WordPress to Framer article.
Astro
Astro is a web framework that builds pages ahead of time and ships very little JavaScript by default, so sites tend to be fast without much tuning. Content can live in Markdown files or come from a headless CMS. It suits teams who want speed and control and have a developer to own the code. Editors need a CMS layer on top unless they are comfortable working in files. See Astro vs WordPress and the WordPress to Astro route.
Next.js
Next.js is a React framework for sites that behave more like applications: logged-in areas, personalisation, product data, or a front end that shares code with your app. It is the most flexible option and the one that most needs an engineering team to run it. Read Framer vs Next.js and the WordPress to Next.js route.
Sanity or another headless CMS
A headless CMS such as Sanity, Storyblok or Contentful stores your content and serves it to whatever front end you choose, usually Astro or Next.js. You get structured content, flexible editing and the freedom to change the front end later without moving content again. The trade-off is more moving parts: a CMS, a front end and the glue between them. Read Sanity vs WordPress and the WordPress to headless CMS route.
AI-built sites
AI builders and coding assistants can now produce a working site quickly, as real code you own. That is useful for prototypes and simple sites. For a marketing site that has to rank and be edited by non-developers, someone still needs to own the code, set up the SEO basics properly, connect a CMS and handle redirects. Our WordPress to an AI-built site route explains when this works and when it does not.
Webflow, Squarespace and Wix
Webflow is another visual builder with a mature CMS and ecommerce, and a steeper learning curve for editors than most teams expect. Squarespace and Wix are simpler, template-led builders that suit small sites better than growing companies. Compare them in Webflow vs WordPress, Squarespace vs WordPress and Wix vs WordPress, or see every option side by side in our website platform comparison.
How to choose in one pass
Marketers edit, design matters, no shop: Framer.
Speed and control matter, a developer owns the code: Astro, with a headless CMS if non-developers publish.
The site behaves like an app: Next.js, usually with a headless CMS.
Content is complex and will outlive the front end: Sanity or another headless CMS, with Astro or Next.js.
The site is stable and the team is happy: stay, and consider a Tune-Up.
How a WordPress Migration Works, Step by Step
Every move we run follows the same shape, whatever the destination. The order matters more than the tools.
Step 1: Audit and crawl the current site
Crawl every URL the site serves, not only the ones in the menu. Pull search performance data for the last year, list the pages that earn traffic, conversions or backlinks, and note every integration: analytics, tag manager, CRM, forms, chat, consent. This audit is the baseline you will measure the new site against.
Step 2: Decide what moves, merges or retires
Build a content inventory. Every page and post gets one of four decisions: move as it is, rewrite, merge into a stronger page, or retire. Retired pages still need a destination in the redirect map. This is the moment to cut thin tag archives and outdated posts, not after launch.
Step 3: Model the content for the new platform
WordPress stores most things as posts, pages and custom fields. The new platform needs a clear content model: which collections exist (articles, case studies, authors, categories), which fields each one has and how they relate. Getting this right is what lets editors publish later without breaking layouts.
Step 4: Export the content
Pull posts, pages, custom fields, media and authors out of WordPress and clean them for the new model. The next section covers this in detail, because it is where most of the hidden work sits.
Step 5: Replace each plugin with something smaller
Every plugin needs a decision before you move. Most are replaced by a built-in feature or a small service.
SEO plugins (Yoast, Rank Math): titles, meta descriptions and structured data move into the new templates, field by field.
Forms (Contact Form 7, Gravity Forms): the platform's own forms, a form service or a serverless function, with the same notifications and CRM connections.
Redirects (Redirection): export the existing rules and merge them into the new map, so old redirects do not break.
Caching and speed plugins: usually unnecessary once pages are built ahead of time and served from a CDN.
Custom fields (Advanced Custom Fields): become fields in the new content model.
Security plugins: largely unnecessary once there is no public admin or database to attack.
WooCommerce: a separate decision. Stay, or move to a dedicated commerce platform.
Step 6: Design and build the templates
Design the page types first (home, product or service page, article, case study, landing page), then build them as reusable components. A component library is what lets the marketing team assemble page nine in an hour instead of a day.
Step 7: Build and sign off the redirect map
Map every old URL that carries traffic, links or conversions to its closest new equivalent, then have the business sign it off before launch. The SEO section below shows what a good map looks like.
Step 8: Rebuild technical SEO
Carry over titles, meta descriptions, headings and image alt text. Set self-referencing canonical URLs, rebuild structured data, generate a fresh XML sitemap and check robots rules so staging stays out of the index and production does not.
Step 9: Test on staging
Test every template on desktop, tablet and phone. Submit every form. Check analytics and consent fire correctly. Run the redirect map against staging, if your platform allows it, so you know every rule resolves in one hop.
Step 10: Launch
Switch DNS at a quiet time, confirm the redirects are live, submit the new sitemap in Google Search Console and spot-check your highest-traffic URLs by hand. Keep the old site available privately for a few weeks in case you need to recover anything.
Step 11: Monitor for 30 days
Watch crawl errors, index coverage, rankings for your important terms and conversions daily at first, then weekly. Most problems show up as 404s in Search Console within the first fortnight, and every one of them is a redirect you can still add.
Getting Your Content Out of WordPress
WordPress gives you several ways to get content out. None of them produces content that is ready for a new platform without cleaning.
The built-in export. Tools, then Export, produces an XML file (WXR) of posts, pages, categories, tags, comments and custom fields. Media is referenced by URL rather than included, so files must be downloaded separately.
The REST API. WordPress exposes posts, pages, media and taxonomies as JSON at /wp-json/wp/v2/. This is usually the cleanest route for a scripted import, and it handles custom post types that have API access enabled.
The media library. Download the uploads folder or pull files through the API, then re-host them on the new platform. Keep file names where possible, and redirect linked PDFs that people may have bookmarked or shared.
Custom fields and custom post types. Fields from Advanced Custom Fields and similar plugins come out as raw values that need mapping to the new content model. Repeaters and flexible content fields take the most work.
Authors and categories. Export them first so articles can reference them in the new CMS.
The cleaning is where time goes. Expect to strip shortcodes, remove page builder markup, fix inline styles, convert old embeds, rewrite internal links to the new URL pattern and decide what to do with comments. Budget for it in the plan rather than discovering it in week four.
How to Keep Your Rankings Through the Move
Rankings are rarely lost because of a new platform. They are lost because URLs change without redirects, content gets thinner, or metadata goes missing. A signed-off redirect map is the single most important document in a migration. Read our glossary entries on redirect maps and 301 redirects for the basics.
The WordPress URL patterns to plan for
WordPress creates more URLs than most teams realise. These are the patterns we map on almost every move.
Date-based post URLs such as /2022/05/your-post/
Category archives such as /category/news/
Tag archives such as /tag/anything/
Author archives such as /author/jane/
Paginated archives such as /blog/page/2/
Query string URLs such as /?p=123 and /?page_id=45
Uploaded files under /wp-content/uploads/
Feeds such as /feed/ and /category/news/feed/
A redirect map example
Here is part of an example map for a WordPress site moving to a new /blog structure. Each line is a permanent 301 from the old URL to the new one.
/2022/05/pricing-update/ goes to /blog/pricing-update (one to one, every post)
/category/news/ goes to /blog/news if it ranks, otherwise /blog
/tag/onboarding/ goes to the closest category or /blog, never the homepage
/author/jane/ goes to /blog/authors/jane, or /about if there are no author pages
/?p=4821 goes to the post's new URL, looked up by ID in the export
/wp-content/uploads/2021/03/brochure.pdf goes to the re-hosted file
/services/web-design/ goes to /services/website-design (slug tidied)
/feed/ goes to the new feed, so subscribers do not hit a 404
Three rules keep a map healthy. Every redirect should resolve in one hop, not a chain. Retired pages go to the closest relevant page, not the homepage. And the map should include the redirects your current site already has, so old links keep working.
Want the move planned for you? Plan my migration free. Enter your site and where it is moving, and the Migration Planner plans it for you: which URLs keep their address, which need a redirect and a realistic timeline. Or book a call and we will build the redirect map with you.
The rest of the SEO checklist
Keep URLs that already rank unchanged wherever the new structure allows.
Carry over titles, meta descriptions, headings, body content and alt text, then improve them after launch rather than during.
Keep internal links pointing at final URLs, not at redirects.
Rebuild structured data for articles, FAQs, breadcrumbs and your organisation.
Submit the new sitemap and watch index coverage in Search Console.
For the full process, see our SEO migration checklist, or run your current sitemap through the migration planner for a first read.
What It Costs to Leave WordPress
Cost depends on how many page types you need, how much content must be cleaned, how many integrations have to keep working and whether you need more than one language. Platform fees are a separate, usually much smaller line. Here is how our pricing works.
Tune-Up, $5,000 fixed: a defined technical pass if you are staying on WordPress.
Landing Page, from $2,500: one new page, built fast, without moving the whole site.
Migration or new build, from $10,000: audit, design, rebuild, content move, signed-off redirect map and 30 days of monitoring after launch.
Embedded Team, from $2,000 a month: ongoing design and build help after launch.
The things that push a project above the starting price are predictable: a large number of distinct templates, heavy content cleaning, several locales, complex integrations, or a full rebrand alongside the move. We scope all of that after the audit, so the number is agreed before the build starts. See our pricing page and the migration service for details.
How Long a WordPress Migration Takes
A full marketing site typically goes live in three to six weeks, depending on page count, how much content needs cleaning and how quickly feedback comes back. Large sites with many collections or locales take longer, and a single landing page is much shorter. A typical plan runs like this.
Week one: audit, crawl, content inventory and a first draft of the redirect map.
Weeks two to four: design, templates, component library and the content move.
The final week: staging review, redirect sign-off, testing and launch.
The 30 days after launch: monitoring rankings, crawl errors and conversions, and fixing anything that turns up.
A WordPress Move We Ran: Waste Logics
Waste Logics builds cloud software for waste and recycling businesses, and its website was the main source of new leads. The old WordPress site made a powerful product look generic and could not be edited by the marketing team. We migrated it to Framer as its own workstream: a full crawl of the WordPress site, URL mapping and redirects, technical SEO rebuilt in the new platform, and every article and customer story moved across.
The new site went live on 16 September 2026. No rankings were lost through the switch, and five weeks after launch organic search sessions were up 44%. Migrated articles kept ranking from their new URLs. Read the full Waste Logics case study.
Common Mistakes When Leaving WordPress
Moving for fashion. If the site works and the team is happy, a new stack will not fix a content or positioning problem.
Redirecting everything to the homepage. Search engines treat this like a missing page. Map each URL to its closest equivalent.
Forgetting the URLs nobody sees. Date archives, tag pages, /?p= links and PDFs in the uploads folder all carry links and traffic.
Dropping existing redirects. The Redirection plugin often holds years of rules. Export them and merge them into the new map.
Underestimating content cleaning. Shortcodes and page builder markup do not import cleanly. Plan time for it.
Redesigning and rewriting everything at once. Changing URLs, design and copy in one go makes it hard to see what caused a ranking change. Keep content stable through the move, then improve it.
Losing tracking. Analytics, tag manager, conversion pixels and consent need testing on staging, not discovering on day two.
Leaving staging indexable, or production blocked. Check robots rules and noindex tags on both before and after launch.
Choosing a platform the editors cannot use. The best stack is the one your marketing team will actually publish on.
Stopping work at launch. The first 30 days are when broken links show up. Watch Search Console and fix them quickly.
Your WordPress Migration Checklist
Before you decide
List the problems you want the move to solve, and check a Tune-Up would not solve them.
Agree who will edit the site after launch, and how often.
Shortlist destinations using the comparison above.
Before the build
Crawl every URL and export a year of search performance data.
Build the content inventory: move, rewrite, merge or retire.
List every plugin and decide what replaces it.
Export existing redirects from the Redirection plugin or your server.
Define the new content model and URL structure.
During the build
Export and clean posts, pages, custom fields, media and authors.
Build templates as reusable components.
Draft the redirect map and get it signed off.
Carry over titles, meta descriptions, alt text and structured data.
Rebuild forms, analytics, tag manager and consent, and test each one.
Launch day
Confirm staging is not indexable and production is.
Switch DNS, confirm redirects resolve in one hop and spot-check top URLs.
Submit the new sitemap in Search Console.
The 30 days after launch
Check crawl errors and add any missing redirects.
Track rankings for your important terms and conversions against the baseline.
Only then start improving content and design.
Keep Exploring
Compare platforms: Webflow vs WordPress, Squarespace vs WordPress, Wix vs WordPress, Framer vs Next.js and all website platforms.
Migration routes: WordPress to Framer, WordPress to Astro, WordPress to Next.js, WordPress to a headless CMS and WordPress to an AI-built site.
Further reading: Framer vs WordPress, Astro vs WordPress, Sanity vs WordPress and our guide to leaving Webflow.
Tools: the migration planner and the resources hub.
Leave for the Right Reason, Then Move Carefully
Leaving WordPress is worth it when the platform has become the bottleneck: when updates are risky, pages are slow and your team cannot publish without help. Choose the destination by who edits the site, plan the content move properly and treat the redirect map as the most important document in the project. Do that and the move protects what you have built rather than putting it at risk.
Ready to plan the move? You have two options. Plan my migration free: test your site in the Migration Planner and let it plan the move for you. Or book a call and we will tell you what we would do, including when staying or a Tune-Up is the better choice. Our work includes three clients that have each been acquired for over $1 billion.
Frequently asked questions
Should we leave WordPress?
When is a Tune-Up enough instead of a migration?
What is the best alternative to WordPress for a marketing site?
Will we lose SEO rankings if we leave WordPress?
How do we export content from WordPress?
How much does it cost to move off WordPress?
How long does a WordPress migration take?
What happens to our WordPress plugins?
Harish Malhi
Founder of Goodspeed
Harish Malhi is the founder of Goodspeed. He left Google in 2019 to build his own product, and started Goodspeed to give other founders the same head start. Today the studio designs and builds websites and the whole digital experience around them for funded tech companies, at the moments that matter: a raise, a launch, a press cycle. Goodspeed is a Framer Enterprise Expert, was Bubble’s Agency of the Year in 2024, and has shipped 300+ products, including launch pages for an NVIDIA-backed AI lab and a Webby-nominated site for a Boeing-backed aviation company. It holds a 5.0 rating from 46 reviews on Clutch.
