When to move off WordPress, and how to do it without losing your search traffic
Short answer: WordPress is free website software that you install on your own hosting, run by you or a helper, and widely used for business sites. Move off it when slowness, security problems or editing pain keep costing you money after you have tried the cheaper fixes: remove unused plugins (add-on programs), update, add backups and better hosting. If you do move, keep your page addresses, forward the ones that change with 301 redirects (permanent forwards), rebuild forms and tracking, and test before launch. A move cannot promise to keep every ranking.
Your WordPress site is slow, was hacked or is too hard to edit, and you are deciding whether to fix it or leave.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Move off WordPress only after you have tried to fix the specific problem, and only if the cost of fixing is higher than the cost of moving. Many slow, insecure or painful sites are caused by too many plugins, weak hosting or no maintenance, not by WordPress itself. If the fixes are done and you still lose money, or nobody will keep it updated, a move is reasonable. The move is a project with a plan, a redirect list and a test, not a switch.
This guide gives signs it is time, what to try first, the destinations (with prices as of November 2026, so check each vendor page), a step by step plan, a plugin inventory template, a test plan and what you lose and keep. One destination is Ploy, an AI marketing platform that rebuilds a site from its public address and hosts it. It is one fair option, not the default, and the plan works for any destination.
This page may contain affiliate links from which Blur Studio earns commissions.
Signs it is time, and what to try first
| Problem | Fix first | Move if |
|---|---|---|
| Slow | Remove unused plugins, compress images, use a caching setup, check the hosting plan, test the home page on a phone | You did all that and key pages still load slowly, or the host cannot handle your traffic and a better plan costs more than a new platform |
| Hacked | Restore a clean backup, change every password, update everything, delete plugins and themes you do not use, ask your host for help | It happens again, nobody will do updates, or you cannot say who has admin access |
| Hard to edit | Simplify the theme, train the editor, use fewer page builder add-ons, set up editing roles | Every change still needs a developer, or staff avoid editing because they fear breaking the site |
| Costs too high | List real costs: hosting, premium plugins, themes, care plan, developer hours | The yearly total is more than a simpler platform with fewer parts |
How bad is the security risk?
Patchstack, a company that sells WordPress security protection, reports in its State of WordPress Security in 2026 that 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025, 42 percent more than in 2024. It says 91 percent were in plugins, 9 percent in themes and only 6 in the WordPress core software. It also says 46 percent were not fixed in time for public disclosure. Because the seller has an interest, read this as a reason to keep few plugins and update fast, not as proof that WordPress cannot be secured. The WordPress software itself is free and open source under the GPL licence (a licence that lets anyone reuse the code), which means you can keep your files and database wherever you host.
Upkeep has a price. GoDaddy, which sells hosting, shows ranges for maintaining a small to medium business site at $50 to $500 a month, which is $600 to $6,000 a year. See what website care plans cover. If you can pay for real upkeep, staying may be the cheapest answer.
Where you can go, with prices
These are dollars as shown on each vendor's page in November 2026. Pages sometimes do not name the currency, and sale prices are left out. Check each page before you decide.
| Destination | What it is | Price shown | Trade-off |
|---|---|---|---|
| Stay and fix | Same site, better hosting and a care plan | SiteGround's (a web host) StartUp hosting plan renews at $17.99 a month | You still own the update work, or pay for it |
| WordPress.com Business | Hosted WordPress run by WordPress.com; plugin installs allowed on this plan | US$25 a month billed yearly, US$40 monthly | Still WordPress, with a host-controlled setup |
| Webflow | A visual builder with hosting | Basic site plan $15 a month billed yearly; Premium $25 yearly, $39 monthly | Priced per site. Export gives HTML, CSS and JavaScript, but forms stop working and CMS content is exported by collection. |
| Framer | A design-led builder with hosting | Basic $10, Pro $30 a month, per site | No HTML export for self-hosting |
| Ploy | AI platform that rebuilds a site and hosts it | Free $0; Starter $50 a month or $480 a year; Pro $300 a month or $2,880 a year | Credits (points for AI work) reset each month and have no published price per action; ads and outreach pages are waitlists |
| Static site on a host like Netlify (a service that hosts plain site files) | Plain files with no database | See Netlify vs WordPress hosting | Best for sites that change rarely; editing needs a tool or developer |
| Hire a specialist | A freelancer or agency does the move | Sellers quote $1,500 to $35,000 by scope | Check what the quote includes |
Goodspeed, an agency that does migrations, says its work starts from $10,000 and takes about 5 weeks plus 30 days of monitoring, and that very low quotes usually cover only a content transfer and not a rebuild with redirects, on-page SEO, tests and monitoring. All migration price sources are sellers. See how much a website migration costs. For more on options, read WordPress alternatives for business websites and Ploy vs WordPress.
What you lose and what you keep
| Keep | Lose or rebuild |
|---|---|
| Your domain and email (if you handle DNS with care) | Plugin features: forms, SEO plugin settings, caching, membership, booking, popups |
| Page text, images and blog posts, if you export them first | The exact theme and page builder layout |
| Page addresses, if the new site uses the same ones | Shortcodes (small tags that plugins turn into content) and embeds |
| Your analytics and Search Console (Google's free search report tool) history | Custom code in the theme |
| Your WordPress backup, as a fallback | The WordPress admin screen your team knows |
The move is a rebuild, not a file copy. Ploy's own docs call it "a rebuild, not an identical copy" and tell you to review every page before you switch. They also say forms, plugins, shortcodes, embeds, interactions, custom code, private pages and live data may need separate work.
Step by step
- Back up everything. Take a full backup of files and database, and export your content (Tools, then Export in the WordPress admin). Store both somewhere other than the old host.
- Benchmark. Export 16 months of pages, clicks and queries from Google Search Console (Google's free tool that shows how your site appears in search), plus top pages and leads from your analytics.
- Inventory the plugins. Use the template below. For each plugin write what it does, whether you still need it and what replaces it.
- List every URL. Use the sitemap and a crawler (software that follows links and lists pages, such as Screaming Frog). Mark each page keep, merge or drop.
- Choose the destination using the decision rule near the end.
- Build on a private test address. Block search engines on the test copy and note that the block must be removed at launch.
- Carry over the SEO basics. Titles, meta descriptions (the summary shown in search results), headings, image descriptions, internal links, canonical tags (tags that name the preferred address for a page) and structured data (markup that describes a page to search engines).
- Rebuild forms and tracking. Test each form end to end.
- Write and load the redirects. Keep old addresses if you can. Google says that when addresses change you should map old URLs to new ones and redirect on the server, and that 301 and other permanent redirects do not cause a loss in PageRank. On WordPress the redirects are in server rules or a plugin, so copy them out before you leave. On the new host, load them there.
- Test, then launch. Point the domain to the new host. See how to point your domain at a new website without breaking email.
- Submit the new sitemap in Search Console and monitor for 8 weeks. Google says showing new URLs can take a few weeks or more for a medium-sized site.
- Keep the old site as a backup for at least a quarter before you cancel hosting.
Plugin inventory template
| Plugin | What it does | Still needed? | Replacement on new site |
|---|---|---|---|
| Contact form plugin | Sends quote requests to email | Yes | Built-in form, tested |
| SEO plugin | Titles, descriptions, sitemap | Yes | Platform settings or built-in sitemap |
| Caching plugin | Speeds pages | No | Not needed on a hosted platform |
| Slider plugin | Home page banner | No | Single image |
| Redirect plugin | Old 301 rules | Yes | Copy the rules into the new host |
Moving to Ploy: what its docs describe
Ploy's WordPress migration page describes four steps. First, give Ploy's Agent your public address (the pages must load without a login), in the app or from an AI tool connected to Ploy through its MCP server (a standard way for AI tools to connect to other software). Second, the Agent lists your site and shows a plan. On a large site it builds key pages first while WordPress keeps serving the rest, and it publishes only with your approval. Third, review the migration report to see where each form sends mail. Fourth, switch traffic after Ploy's Migration Readiness Checklist: keep URLs the same where you can and add 301 redirects in its path routing for any that change. You can move the whole domain, or move one path at a time with route rules. A WordPress plugin called Ploy Connect serves chosen Ploy pages through WordPress, keeps your home page on WordPress and needs a paid plan.
Blog and other collections import into Ploy's built-in database. The docs say a re-import replaces the tables instead of syncing them. They also say moving a site uses AI credits and larger sites use more. Check usage in the settings before a full build. Ploy's case study of Sengo, a Quebec City agency, says about 600 WordPress pages were migrated in one night, its Agent found about 50 existing mistakes on the live site, and the site went live after a few evening sessions over about a week. That is Ploy's own story and gives no search results or redirect detail.
On ownership, Ploy's FAQ says you can get your site's full source on every plan, including Free, by installing its command line tool and running a Git clone (a copy of the code). Ploy's terms say your data is available for export for 30 days after termination, while its privacy policy says it retains data for 60 days after account termination to allow export. Check both pages. On review, remember that AI-written or AI-rebuilt pages need a person to check every fact. Google's spam policies target many pages made mainly to rank, however they are made, so do not let a tool multiply near-identical pages.
Who should skip Ploy for this move
- Your site depends on plugins for membership, booking or store rules. Check Ploy's docs for each feature before you plan, and consider keeping WordPress for those paths.
- You want your current design copied exactly. It rebuilds on its own design system.
- You need a fixed monthly cost. Credits are not priced per action and unused credits do not roll over.
- You need a long vendor track record. Ploy was founded in 2025.
- You need a SOC 2 report for a client. Ploy's Trust Center lists a Type 1 report and a feature page mentions Type II controls (as of November 2026), so ask for the report.
- Your problem is only a bad plugin or weak host. Fix that first.
A worked example with made-up numbers
These numbers are invented to show the method.
A 55-page WordPress site for a physiotherapy clinic has 14 plugins and a $29 a month hosting plan. Pages take about 6 seconds to load on a phone, one plugin was flagged as vulnerable and the receptionist avoids editing because the page builder broke the layout twice. Search Console shows 2,400 clicks a month. First they try fixes: remove 6 unused plugins, compress images and move to better hosting at $45 a month. Load time falls to 3 seconds but the editing pain stays. They decide to move. The inventory shows 5 plugins are still needed (forms, booking link, SEO, redirects, reviews). The new platform covers 4 of them. Booking stays as an embedded link to their existing booking tool. They keep 41 addresses and redirect 14. After launch, clicks dip 15 percent in week 1 and are at 98 percent of baseline in week 7. The lesson is the order: fix cheap things first, decide by what still hurts, and measure against a baseline.
Test plan with pass and fail marks
- Redirect test. Request every old URL. Pass: a 301 to the right page in one hop. Fail: a 302, chain, loop or unintended 404.
- Noindex and canonical test. Pass: no noindex on pages you want found, and canonicals point to the new addresses. Fail: either left from staging.
- Forms and bookings. Submit each three times. Pass: all arrive. Fail: any lost.
- Tracking. Pass: your own visit appears in analytics within minutes.
- Speed. Pass: key pages are no slower on a phone than on the old site.
- Content check. Pass: every page has been read by a person, with prices, hours, names and claims correct.
- Accessibility basics. Pass: contrast, image descriptions and keyboard use do not block a task. WCAG 2.2 AA is the usual target. Check local law.
- Week 4 check. Pass: clicks within about 20 percent of baseline and rising. Fail: more than 30 percent below and flat. These are my working marks, not a Google rule. Investigate redirects first.
Recovery studies in this area are about moves to a new domain: an average of 523 days across 892 migrations (Search Engine Journal, a search industry news site), and a median of 304 days across 1,052 migrations (SALT.agency, an SEO agency, 2026). A same-domain platform move that keeps addresses is a lower-risk case with no published dataset, so measure your own.
How I'd approach this
My decision rule: fix first if the problem is a plugin, a host or a missing backup. Move if the site is simple enough to rebuild, nobody will do upkeep, or editing is the real cost. Choose the most portable destination if owning your files matters. Choose a hosted one if time matters more.
My first week would be:
- Day 1: back up files and database. Export Search Console and analytics baselines.
- Day 2: crawl the site and build the URL sheet with keep, merge or drop.
- Day 3: fill in the plugin inventory. Delete plugins you do not need on the live site and note the result on speed.
- Day 4: list forms, tracking codes, embeds and custom code that will not copy.
- Day 5: shortlist two destinations. If Ploy is one, try Ploy's plan step on your live address without publishing, then compare the result to your real pages.
- Day 6: price both routes, including hours, credits or subscriptions, and what happens if you want to leave later.
- Day 7: decide, set a launch date early in the week and write the redirect table.
If you want someone to take this on, Blur Studio builds custom versions too: AI agents that use your business knowledge, CRM and calendar connections, finishing a half-built move, and ongoing care. You can see what that includes. If your site is mainly a lead source, read keeping SEO rankings when you rebuild or move a site before you start. If you choose Ploy, try the free plan on a copy of your key pages first and set a credit limit before you build the rest.
Questions people ask
Is WordPress too slow or insecure for a business?
Not by itself. Speed and security depend on hosting, plugins and updates. Patchstack, a security seller, reports 91 percent of 2025 WordPress vulnerabilities were in plugins. Remove unused plugins, update fast, keep backups and test again before deciding to move.
What do I do first if my WordPress site was hacked?
Restore a clean backup, change all passwords, update everything and remove unused plugins and themes. Ask your host for help. If it happens again or nobody can maintain the site, that is a stronger reason to move. See what care plans cover.
Will I lose my Google rankings if I leave WordPress?
You may see a dip. Google says 301 redirects do not cause a loss of PageRank, but showing new URLs can take a few weeks or more for medium-sized sites. Keep addresses where you can, redirect the rest, remove staging noindex tags and measure against a baseline. No one can promise a result.
Can I export my WordPress site?
Yes. WordPress is free open source software and your files and database sit in your hosting account. You can export content from the admin screen and take a full backup. Plugins, forms and theme layouts will not move on their own, so list them first.
How much does it cost to move off WordPress?
Sellers quote $1,500 to $35,000 depending on scope, and Goodspeed says its migrations start from $10,000. All of those are sellers, so ask each quote to list redirects, forms, tracking, testing and monitoring. A do-it-yourself move costs your time plus the new platform's plan.
Does Ploy move WordPress sites?
Its docs describe rebuilding a site from its public address, with your approval before anything goes live, and path by path switching. It uses AI credits, and forms, plugins and custom code may need separate work. See Ploy's WordPress migration page.
Should I keep WordPress for part of the site?
It can make sense. Ploy's docs describe a plugin called Ploy Connect that serves chosen pages from Ploy through WordPress while the home page stays on WordPress, and it needs a paid plan. A gradual move lowers risk but means you still pay for and maintain both.
How long should I keep the old WordPress site?
Keep a full backup indefinitely and keep the old hosting live for at least a few months in case something is missing. Keep your domain registered. Redirects should stay in place for as long as old addresses still get visits.
More in this topic: Websites: build, move and cost for small business (8 guides) →
Sources
- Ploy: move a WordPress site to Ploy (Ploy docs)
- Ploy FAQ: source code access (Ploy docs)
- Ploy pricing (Ploy)
- Sengo moved a 600 page WordPress site to Ploy (Ploy customer story)
- State of WordPress Security in 2026 (Patchstack)
- WordPress license (WordPress.org)
- Site move with URL changes (Google Search Central)
- Spam policies for Google web search (Google)
- WordPress.com pricing (WordPress.com)
- Webflow pricing and export FAQ (Webflow)
- Website maintenance cost (GoDaddy)