Leaving WordPress Without Handing Your Client a Codebase

By Mykhailo Sokolov
Leaving WordPress Without Handing Your Client a Codebase

A popular argument doing the rounds among developers this month goes like this: skip the WordPress agency and hire a student developer instead. The student builds on a modern framework, the site loads faster, and nobody has to babysit forty plugins. The replies split down the middle. Half agreed that the plugin pile has become unmanageable. The other half pointed out that a student goes on holiday, ships broken SEO, and leaves the client with code nobody else understands.

Both halves are right, and that is the problem for agencies. If the choice is between a fragile WordPress build and a custom codebase the client can't touch, the agency loses either way. This piece is about the third option: leaving WordPress without handing your client a codebase.

Why are agencies being told to leave WordPress?

Because the maintenance load sits in the plugin layer, and it keeps growing. Patchstack's State of WordPress Security in 2026 report counted 11,334 new WordPress-ecosystem vulnerabilities in 2025, and most of them live in plugins and themes rather than in WordPress core. Every client site with a long plugin list is a list of separate vendors, each with its own update schedule, and an agency carries the risk of all of them.

The cost rarely shows up on an invoice. It shows up as update windows, broken layouts after a plugin release, and support tickets that have nothing to do with the work the client is paying for. We covered the day-to-day side of this in our WordPress plugin maintenance playbook.

Why did clients stay on WordPress for so long?

Because they could edit their own site. For most small and mid-sized businesses, the deciding feature was never the theme or the plugin directory. It was a backend they understood, where they could change a price, publish a post or swap a photo without calling anyone.

That is the part the "hire a student" argument skips. A hand-built site on a modern framework can be faster and cleaner, but unless someone also builds and maintains an editing interface, the client loses the one thing that kept them on WordPress in the first place.

Is a custom codebase the answer?

For some projects, yes. For most agency clients, it moves the maintenance problem instead of removing it. AI tools have made custom code quick to produce, but producing it was never the expensive part. Someone still has to host it, patch its dependencies, fix it when it breaks, and answer the client's call when the original developer has moved on.

An agency that swaps forty plugins for a custom codebase has traded many small vendors for one large dependency: the person who wrote the code. That is a fair trade for a product company with its own engineers. It is a poor one for a business that just wants to update its opening hours.

What should replace WordPress for an agency's clients?

A platform that keeps what clients valued in WordPress and removes what agencies had to carry. In practice that means five things:

  • The client edits content in a real admin. Pages, products, posts and forms, without touching code.
  • No plugin layer to patch. Core features are part of the platform and are updated centrally, not site by site.
  • One system for the site and the business around it. CMS, Ecommerce, CRM and email in one place, so there are no connectors to break.
  • The agency stays in front of the client. White-label admin and billing, so the platform doesn't compete with the agency.
  • The content belongs to the client. Moving off a platform should never mean losing your own data.

How does that work on WebinOne?

WebinOne is an all-in-one digital experience platform for agencies, built and run by Upgrade Parade Corp on AWS. CMS, Ecommerce, CRM, email marketing and hosting come in one white-label platform, and features that would be plugins elsewhere are native extensions that we build and maintain ourselves.

AgentOne, the platform's built-in team of AI agents, gives agencies the speed that makes custom code tempting, without the codebase. It designs, builds and manages websites inside WebinOne, using the platform's own pages, modules, forms, CRM and Ecommerce. The only code it writes is front-end code (HTML, CSS, JavaScript and Liquid templates), which the agency can see and edit in Code & Assets. WebinOne runs the back end, so there is no separate application to own or maintain. The client keeps a full admin, and so does the agency. You can see how that works on the AgentOne page.

What does moving a WordPress site actually involve?

An inventory, a content map and a redirect plan, in that order. You list every page, post, product and form; you decide where each one lives on the new platform; and you map every old URL to its new address so search engines and bookmarks follow. Our WordPress migration checklist walks through the steps, and this guide covers what to ask of a migration service.

Size matters less than preparation. One of the larger moves we have handled was a client site with roughly 10,000 events, articles and posts, about 15 GB of content, in two languages. It moved off WordPress with a redesign, came out faster on mobile and desktop, runs with no third-party plugins, and kept its search rankings. That move was done by hand, before AgentOne existed.

For agencies moving client sites, TeamOne, our in-house delivery team, runs migrations as fixed-price packages: $500 for a brochure site of up to 10 pages, $1,500 for a marketing site of 11 to 30 pages, and $3,000 for an Ecommerce site with products and payments. Custom projects are quoted separately. Across the platform's history, more than 3,000 websites have been migrated onto it.

What is the first step for an agency?

Pick one client site, not the whole portfolio. Choose a site where the plugin list causes real work, move it, and compare the next three months of maintenance with what you are used to. If the numbers hold, the rest of the portfolio follows the same path.

Agencies can join the WebinOne Partner program to run client sites under their own brand, and hand the first migration to TeamOne if they would rather not spend their own team's time on it.

Mykhailo Sokolov

Mykhailo Sokolov

Here at WebinOne, me and my team designs, develops and updates all of the WebinOne's free templates. You can send your feedback/ideas/questions to my email or Facebook. For WebinOne partners we have a separate #templates channel where we discuss new designs, frameworks, ideas, challenges etc.