When You Shouldn't Move Off WordPress

I move people off WordPress for a living, so it’s worth saying plainly that a decent number of sites shouldn’t move at all.

I’d rather write that down than discover it forty minutes into a consultation call, and I’d rather you know before you book one. Here’s the list I actually check against.

You sell products through your site

If you’re running WooCommerce or anything similar — inventory, variants, shipping rules, tax by region, abandoned carts — stay where you are.

E-commerce is genuinely complicated, WordPress has spent fifteen years building the plumbing for it, and there’s an enormous ecosystem of things that already work with it. Rebuilding that is a much larger project than a website move, and nothing about it gets easier by leaving.

A separate checkout for one or two digital products is a different matter. That’s not a store, that’s a payment link, and it moves fine.

You host courses on it

LearnDash, LifterLMS, Tutor, or anything else where students log in, work through modules, and have their progress tracked.

Course platforms are software, not websites. The site around them can move; the course itself is a different product decision, and it’s usually better handled somewhere purpose-built than rebuilt from scratch.

You run a membership

Same reasoning. Recurring billing, gated content, member accounts, renewals, cancellations, dunning when a card fails. That’s a system with a lot of edge cases, and every one of those edge cases involves somebody’s money.

You have a forum or community

If members post to each other, reply to each other, and expect that history to persist, the discussion is the product. Moving it is a data migration with a social consequence — people notice immediately when their conversations have gone.

Your site is a searchable directory

Practitioner listings, resource databases, anything where the point is that visitors filter and search through many records rather than read pages.

That’s an application with a front end attached, not a website with a lot of pages. It’s buildable, but it’s a different project with a different price and a different timeline, and pretending otherwise would be dishonest.

You publish in more than one language

Multilingual sites carry duplicated content, language switching, per-language SEO and translation workflows. WordPress has mature plugins for this. Rebuilding it is a real undertaking and the benefit is smaller than usual.

What isn’t a hard stop

A few things sound disqualifying and aren’t.

A big blog. Under a hundred pages is standard. A hundred to two-fifty adds a few days. Beyond that I’d quote it separately — but volume is a scoping question, not a reason to stay.

A podcast. If your RSS feed is generated by WordPress, that feed is what Apple and Spotify point at, so it has to be moved deliberately rather than incidentally. It’s a few extra days and it goes in writing. Not a blocker.

Email running through your host. Common, and genuinely risky if handled casually, so it gets planned as its own step. Also not a blocker.

A theme or builder you paid for. The money is spent either way. That it cost something isn’t a reason to keep paying to renew it.

Why I’d rather tell you no

Two reasons, and only one of them is noble.

The honest self-interested one: a project that shouldn’t have started goes badly, and a bad project is worse for me than no project.

The other is that most people asking this question have already been sold something that wasn’t right for them, which is frequently how they ended up with a site they can’t change. Being told no by someone who could have taken the money is unusual enough to be worth something on its own.

If you’re on this list, I’ll say so on the call and point you somewhere better. That takes about ten minutes and costs you nothing.

A consultation that ends in “don’t do this” is still a useful consultation.