# How to Leave WordPress: The Complete Exit Checklist (2026)
Author: Sai Krishna
Author URL: https://superblog.ai/blog/author/sai-krishna/
Published: 2026-08-10
Meta Title: How to Leave WordPress: The Exit Checklist | Superblog
Meta Description: The complete checklist for leaving WordPress: pre-exit audit, migration sequence, DNS cutover, and the decommissioning steps most guides skip.
URL: https://superblog.ai/blog/exit-wordpress/

![The WordPress Exit Checklist](https://prod.superblogcdn.com/site_cuid_ckox4in4f002nl8lhcib41g2u/images/wordpress-exit-checklist-1786106697503-compressed.png)

Here is how to leave WordPress in five phases: audit what you actually have, pick a destination, move the content, cut over redirects and DNS, then decommission the old install properly. Most guides stop after phase three. The phases that cost people money are the first and the last: the audit that catches the data no export file contains, and the shutdown that accidentally takes your domain, your email, or your redirect history down with it.

This is the operational checklist for someone who has already decided. If you are still weighing the decision, [the evidence behind the switch](/blog/switching-from-wordpress/) makes that case separately.

## How to leave WordPress: the five-phase sequence

PhaseWhat happensOur planning assumption1\. AuditContent inventory, plugin-function inventory, traffic baseline3 to 5 hours2\. DecidePick the destination platform and hosting shape1 to 2 hours3\. MoveImport content, images, taxonomy, metadata1 hour to 1 day4\. Cut overRedirects, DNS, SSL, verification2 to 4 hours, plus propagation5\. DecommissionDomain safety, licenses, backups, 30-day watch2 hours, then 30 days of monitoring

Those estimates are our own assumptions for a blog of roughly 100 to 500 posts with a normal plugin stack. Scale them to your size. What matters is the order: phases 1 and 5 hold the irreversible mistakes, and both sit outside the part of the job people think of as "the migration."

## Phase 1: Audit before you touch anything

You cannot safely move what you have not counted. This phase produces three artifacts, all of them files on your disk, not tabs in a dashboard.

### Content inventory

Pull your URL list from three sources and merge them, because no single source is complete:

1. Your `sitemap.xml`, which shows what WordPress thinks it publishes.
2. The Search Console Pages report for the last 12 months, which catches URLs still earning impressions after falling out of your sitemap.
3. The WordPress admin post and page lists, including drafts and custom post types.

Then classify every URL as keep, redirect, or drop. The rule: anything with impressions in the last 12 months is keep or redirect, never drop.

The URLs that break migrations are never the blog posts. They are the ones nobody thinks about: category and tag archives, paginated archives ( `/page/2/`), author archives, attachment pages, and whatever your plugins generated. Walk the list and decide what each one becomes on the other side.

### Plugin-function inventory: what gets replaced, what gets dropped

List your active plugins, then write down the **job** each one does rather than its name. Mark each job as replaced by the new platform, replaced by a separate tool, or dropped entirely.

Most of the list drops. Caching, security scanning, image compression, backups, sitemap generation, and schema markup all become unnecessary the moment you move to a platform that pre-builds pages and handles SEO natively. That is most of the [recurring WordPress maintenance cost](/blog/wordpress-maintenance-cost/) leaving your budget in one go.

The dangerous plugins are the ones holding data that no post export contains:

- **Redirect plugins.** Years of accumulated 301s live in the Redirection plugin's own table. Export that CSV. Those redirects carry link equity from URLs you retired long ago, and failing to recreate them loses it permanently on cutover day.
- **Form plugins.** Submissions sit in a separate table.
- **Comment data and subscriber lists.** Not in the WXR export.
- **Advanced Custom Fields.** Values may export, but the field group definitions describe structure your new platform has to reproduce.

Export each to its own file before anything else moves.

### Traffic baseline snapshot

Take the snapshot **before** cutover, not after something looks wrong. Export and save as files:

- GSC Performance data, queries and pages, for the full 16 months available. Search Console only retains 16 months on a rolling basis, so this window closes behind you.
- GA4 landing page report for the last 12 months.
- Your current PageSpeed scores for three representative URLs.

Without a baseline you cannot distinguish a migration problem from ordinary seasonality, and you will spend week three of your move arguing about it.

## Phase 2: Pick your destination

One paragraph, because this is a decision, not a task. The realistic destinations are a managed blog platform, Ghost, a site builder you already pay for, HubSpot Content Hub, or a static site generator. Match the destination to whoever owns the blog on day 31. A marketing team with no developers and a static site generator is a bad match no matter how fast the output is. We compare all five paths with real costs in [how to run a blog without WordPress](/blog/blog-without-wordpress/), and if Ghost is your front-runner, [the WordPress to Ghost migration guide](/blog/wordpress-to-ghost-migration/) covers that route.

Decide the hosting shape now too. Subdirectory ( `yoursite.com/blog`) keeps authority on your root domain. A subdomain is quicker to point but Google treats it as a separate property. This choice determines how much of phase 4 you have to do.

## Phase 3: Move the content

The mechanics vary by destination and we cover the full walkthrough in the [step-by-step WordPress migration guide](/blog/migrate-from-wordpress/). What matters at checklist level is the acceptance test. Before you call this phase done, confirm:

- Post count on the new platform matches your inventory count.
- Featured images and inline images resolve, and are hosted on the new platform rather than hotlinked back to WordPress. Hotlinked images break the day you cancel hosting.
- Categories (the first one per post), tags, and publish dates carried through. Authors do not: every imported post is attributed to the account that ran the import, so multi-author archives need bylines reassigned afterward.
- Meta titles and descriptions transferred rather than regenerating from scratch.
- **Slugs are identical.** The highest-value item on the whole list. If `/my-post-title/` stays `/my-post-title/`, phase 4 shrinks to almost nothing.

Do this on the new platform's staging or default subdomain while WordPress still serves live traffic. Nothing in phase 3 should be publicly visible.

## Phase 4: Redirects and DNS cutover

Rebuild the redirect table you exported in phase 1, add 301s for every URL that changed shape, and only then move DNS. Use 301, not 302. Verify a sample of 10 redirects with `curl -I` before cutover rather than clicking them in a browser, because browser caching will lie to you.

Then the part of the cutover that has nothing to do with your blog.

### Copy your DNS records before you change anything

Your DNS zone holds more than the A record pointing at your blog. Before you touch nameservers, screenshot or export the full zone, specifically:

- **MX records.** Your business email.
- **TXT records.** SPF, DKIM, and DMARC, plus domain-verification strings for Google Workspace, Microsoft 365, and any SaaS tool that verified ownership.
- **CNAMEs** for tools like your help desk, status page, or email marketing platform.

If your nameservers point at your WordPress host and you move them, every one of those records disappears unless you recreate it. Email failure is silent. You get no error, you just stop receiving messages, and you find out when a customer mentions you never replied.

## Phase 5: Decommission WordPress without losing something

This is the phase nobody writes about, and it is where the expensive mistakes happen. Do not start it until the new blog has been serving live traffic cleanly for at least a week.

### Check where your domain actually lives before you cancel hosting

Read this one twice. **Cancelling your hosting plan can take your domain registration with it.**

Many hosts bundle a free domain with the first year of hosting. That domain is registered in your name, but it is billed through the hosting invoice and managed in the hosting control panel. Cancel the plan and the renewal stops. Depending on the host, you get either a domain quietly expiring on its next anniversary or one dropping into a redemption period with a recovery fee attached.

Before you cancel anything:

1. **Run a WHOIS lookup on your domain.** Note the registrar of record. If it names your hosting company, your domain and your hosting are entangled.
2. **Check the renewal billing.** Find out whether the domain renews on its own invoice or as a line item on the hosting bill.
3. **Transfer the domain to a standalone registrar first.** Unlock it, get the auth code, and start the transfer. ICANN rules impose a 60-day inter-registrar transfer lock after an initial registration or a previous transfer, and most registrars apply a 60-day lock after a registrant-contact change by default (some let you opt out before making the change). The transfer itself starts a fresh 60-day lock, so start early rather than the week you plan to cancel.
4. **Move DNS off the host** to your registrar or a dedicated DNS provider, using the record export from phase 4, and let it propagate for 48 hours.

Only when the domain is at a registrar you control, with DNS answering from somewhere other than the host, do you cancel the hosting plan.

### Kill the recurring licenses

Paid plugin and theme licenses renew on the anniversary of purchase, not on your hosting date, so cancelling hosting does nothing to stop them. Some renew at full price after a first-year discount, so the invoice arrives larger than you remember.

Work through your phase 1 plugin inventory and turn off auto-renew at each vendor's account page rather than waiting to request a refund. Deactivate the license key inside WordPress before you delete the install, since many vendors count activations against a seat limit.

Do not forget the services beside the plugins: offsite backup subscriptions, security and malware scanning, uptime monitoring pointed at the old URL, and any CDN account you opened for WordPress.

### Export a cold backup for retention

Before deletion, take a complete archive and store it in two places:

- A full database dump ( `.sql`).
- The entire `wp-content/uploads` folder. The WXR export from Tools then Export references media, it does not contain the files.
- The active theme folder, if it holds custom work.
- The WXR export itself.

Then make an actual retention decision rather than keeping it forever by default. That archive holds comment authors, form submissions, and user accounts, which is personal data. Set a deletion date matching your retention policy and put it in a calendar.

### Watch Google Search Console for 30 days

Redirects and rankings settle over weeks, not hours. Our monitoring cadence:

- **Days 1 to 3.** Watch the Page Indexing report for a spike in "Not found (404)". That means a redirect gap, and it is the one thing worth fixing immediately.
- **Day 7.** Compare clicks and impressions week over week against your phase 1 baseline, matching days of the week. Expect a wobble. Do not act on it yet.
- **Day 14.** Spot-check that new URLs are indexed using URL Inspection.
- **Day 30.** Full comparison against baseline. This is the number that means something.

Resist intervening during the first fortnight. A move with matching slugs and 301s in place recovers on its own, and reacting to week-one noise usually means changing something that was working.

### What to do with the old wp-admin

Two options, in order of how often they are right.

**Take it offline.** Once the archive is stored and the 30-day watch is clean, delete the install. An unpatched WordPress site nobody updates is a liability that grows every month, and the vulnerabilities sit in exactly the third-party plugin layer that is now unmaintained.

**Keep it up temporarily, but noindexed.** If you want a safety net for 30 to 90 days, your WordPress install now lives at a temporary URL that is a crawlable duplicate of your entire blog. Password-protect it or serve `noindex` and block it in `robots.txt`, then delete it on schedule.

Either way, close the loose ends: revoke API keys and integration tokens the site held, remove admin users, take the old site out of your team password manager, and delete the temporary property from Search Console only after the 30-day watch closes.

## Where Superblog fits

If your blog is a growth channel and the reason you are leaving is that maintenance was eating the time you wanted to spend writing, Superblog is built for that job specifically. It is the lowest-friction destination for phase 3: the WordPress import pulls posts, images, categories, tags, and metadata straight through your WordPress REST API, so there are no export files to clean up. One caveat worth knowing: image re-hosting runs on paid sites, so a trial import brings your posts across with images still pointing at your old media library, and they move onto Superblog's CDN once the plan is active. Slugs are preserved identically, which is what shrinks phase 4 from a project into a checklist item. Pricing is $49/month for Pro and $99/month for Super, with a 7-day free trial and no credit card required. For the direct head-to-head, see the [WordPress blog alternative](/wordpress-blog-alternative) page.

## Frequently asked questions

### How do I move away from WordPress?

In five phases: audit your content, plugins, and traffic baseline; pick a destination; import content while WordPress is still live; cut over redirects and DNS; then decommission the old install. The first and last phases are the ones that get skipped. Audit first to catch data living outside your post export, such as redirect tables and form submissions, and decommission carefully so cancelling hosting does not take your domain or email with it.

### Will I lose SEO if I leave WordPress?

The redirect table you exported in phase 1 is what protects you. Recreate it on the new platform first, then keep slugs identical wherever possible and set 301s for anything that had to change, and resubmit your sitemap after cutover. Rankings follow the URLs, so a move that preserves them reads to Google as the same pages on faster infrastructure. Expect a short wobble in week one and judge the result at day 30 against the baseline you captured before moving.

### Can I cancel my WordPress hosting without losing my domain?

Yes, but only if you check first. If your host is also your registrar, or the domain came bundled free with your hosting plan, cancelling the plan can stop the domain renewal. Run a WHOIS lookup to confirm the registrar of record, transfer the domain to a standalone registrar, move DNS off the host, and let everything settle before you cancel. Start early: ICANN rules lock domains against transfer for 60 days after an initial registration or a previous transfer, and most registrars apply the same lock after a registrant-contact change.

### How long should I keep my old WordPress site running?

Long enough to prove the move worked, which in practice means 30 days of clean Search Console data. If you keep it live during that window, it now sits at a temporary URL that duplicates your entire blog, so password-protect it or serve `noindex` and block it in `robots.txt`. Keep the backup archive longer than the running site.

### What data do I lose if I only use the WordPress export file?

More than most people expect. The WXR export from Tools then Export covers posts, pages, and taxonomy, but it references media rather than containing it, and it does not include form submissions, subscriber lists, plugin redirect tables, or plugin configuration. Export each of those separately before you shut anything down.

* * *

Leaving cleanly is mostly a sequencing problem. If your destination is a platform that imports your posts and keeps your slugs, [start a free Superblog trial](https://superblog.ai) and get phase 3 done today.


---
This blog is powered by Superblog. Visit https://superblog.ai to know more.
---