WordPress to Craft CMS: what actually changes for the business

I get asked the technical question a lot. How do you move a WordPress site to Craft? The technical answer lives in a separate post on the WordPress to Craft migration guide. This piece is the other question. What actually changes for the business once the move is done.

I have walked enough teams through the before and after to know which changes matter and which sound dramatic but are quiet in practice. What follows is the honest version, including the trade-offs that nobody mentions in a sales pitch.

The editor experience changes the day-to-day for the content team

This is the change most stakeholders feel first and remember longest. WordPress and Craft both have a control panel. They are not similar inside it.

WordPress collapses several content concepts into one editor screen. The title, the body, the featured image, the categories, the SEO plugin fields, the page builder, the meta boxes from various plugins. It works, but the order of operations gets muddled and editors learn to scroll past blocks they do not need.

Craft separates the concepts. A section holds a kind of content. An entry type holds the field layout for that kind of content. Matrix blocks let editors compose page content block by block, with each block having its own field layout. Live preview shows the page as it will look while the editor is still writing.

For the team, this means less scrolling, fewer "which field do I edit?" moments and a clearer link between what they see in the control panel and what appears on the page. The trade-off is that editors need a short briefing to understand the difference between sections, entry types and Matrix blocks. WordPress feels familiar from the first click. Craft pays back over time but asks for an hour of attention upfront.

Training overhead is real but small

Most stakeholders ask how much training the team needs. The answer for a typical marketing team is around two hours of structured walkthrough, plus a one-page reference for the three or four things editors do most often, plus a follow-up session two weeks later once the team has hit real questions.

That is small. It is also non-zero. Teams that skip it expect editors to figure Craft out by clicking around, which works for the technically curious and frustrates everyone else. Plan the training as part of the launch, not as a thing to do later if there is budget.

For the editors who do the work, the most common feedback after a few weeks is that the field-by-field structure is easier than they expected and that they wish their WordPress site had been built this way.

Maintenance posture becomes calmer

A typical WordPress site has fifteen to forty plugins. Each one has its own update cadence, its own changelog and its own way of breaking something else. Plugin updates land weekly, sometimes daily. The maintenance posture is reactive. Something will break. The question is when.

A typical Craft site has five to fifteen plugins. The plugin marketplace is smaller and the plugins on it tend to be higher quality because the market does not support drive-by plugins the way WordPress does. Updates land less often and break things less often. The maintenance posture is closer to scheduled rather than reactive.

For the business, this means fewer surprise developer invoices. The maintenance retainer is a known number rather than a guess. I have written about how I structure ongoing maintenance separately. The shape is steadier on Craft.

Security risk profile shifts down

WordPress is the most attacked CMS in the world by a wide margin, mostly because it is the most installed. Most of the attacks target known vulnerabilities in third-party plugins rather than the WordPress core, which is well maintained. The risk on a WordPress site is proportional to the plugin count and the maintenance cadence.

Craft has a smaller attack surface for two reasons. The plugin ecosystem is smaller, so there are fewer abandoned plugins lying around as attack vectors. The platform is less attractive to opportunistic attackers because the install base is smaller and the scripts that target WordPress at scale do not work against Craft.

For the business, this does not mean Craft is invulnerable. Any site with poor hosting, no maintenance and bad passwords can be compromised. It means the baseline risk is lower and the maintenance cost of staying secure is lower. Both matter when the board asks about cyber risk on the next review.

Performance baseline gets better, then it depends on the build

A well-built Craft site tends to be faster than a well-built WordPress site out of the gate. The platform does less in PHP and more in efficient query patterns. Image transforms are first-class. Caching is built in and clean. The Core Web Vitals scores on Craft sites I have built come in green more often than not.

A badly built Craft site can still be slow. Performance is mostly a function of the build quality and the host. The platform raises the floor, but it does not guarantee the ceiling. If the team wants a faster site, the migration is the right moment to commit to that as a design constraint rather than hope the platform delivers it for free.

For the business, the performance change shows up in two places. Search rankings tend to nudge upward because Core Web Vitals improve. Bounce rates on slow connections drop because pages render faster on mobile. Neither change is dramatic. Both are real.

The developer pool is smaller, which has two sides

WordPress has the largest developer pool in the CMS world. You can hire a competent WordPress developer in any UK city within a week. Rates are wide. Quality is wider.

Craft has a much smaller pool. A modest number of UK agencies list Craft as a primary offer and there is a tight group of senior freelancers who use it day to day. Hiring is slower and the rate range is narrower because the people who do Craft well know what they are worth.

The two sides of this are worth being clear about. The downside is that you have less optionality when your current developer becomes unavailable. The upside is that the average Craft developer is more senior than the average WordPress developer because the platform attracts a more experienced audience. You get fewer options and the options are usually better.

I wrote a piece on how to choose a Craft CMS agency in the UK that covers this in more detail.

Vendor lock-in moves but does not disappear

WordPress is open source. Craft is source-available with a commercial licence. The distinction matters less in practice than it sounds. Both let you take your codebase and host it wherever you want. Both keep your content portable as a database export.

The real lock-in is in the content model. A WordPress site built around a specific theme and a specific page builder is genuinely hard to move, even within WordPress, because the body content is wrapped in shortcodes that only that page builder understands. A Craft site built around Matrix blocks is portable in a stricter sense because the content has explicit structure that travels with it.

For the business, the lock-in question is less about the licence and more about the structure of the content. Craft is structurally more portable than most WordPress builds. Whether that matters depends on whether you ever expect to move again.

Integration patterns become more deliberate

WordPress integrates with most third-party services through a plugin. The plugin handles the API call, the configuration screen, the data mapping. Convenient but inconsistent because every plugin author has different ideas about how it should work.

Craft tends to handle integrations through modules written in PHP. There are integration plugins too, but the cultural default is to write a small service class that talks to the external API and exposes it cleanly to templates and the control panel. The first integration costs more developer time. The fifth integration costs less because the pattern is consistent.

For the business, this means integration projects on Craft tend to feel more like engineering and less like installing software. The work is steadier and the result is easier to maintain. The trade-off is that you cannot bolt on a quick integration the way you can with a WordPress plugin.

Honest trade-offs to weigh

Three things tend to count against Craft in an honest comparison.

The community is smaller. Help on a niche problem takes longer to find. The Craft Slack and the Craft Stack Exchange are active, but the volume of indexed answers is a fraction of the WordPress equivalent. For developers working on standard problems this is fine. For unusual edge cases, it is slower going.

The licence is non-zero. WordPress core is free. Craft has a licence cost per installation. The cost is small in a five-year picture, but it is visible where WordPress is not.

The host pool is narrower. Craft runs well on a handful of hosts that understand it. Craft-specific managed platforms, mainstream PHP managed hosts or a managed VPS with a developer in the loop. You cannot run a serious Craft site on the cheapest shared host you can find. The hosting floor is higher.

None of these are dealbreakers for most teams. They are real. Worth weighing against the editor experience and maintenance gains rather than dismissing.

Who tends to benefit most from the move

Teams with a real editorial cadence and a content team that publishes regularly. The editor experience improvement pays back daily.

Teams whose WordPress site has accumulated forty plugins and an unstable maintenance posture. The maintenance shift is the biggest win.

Teams who care about content modelling and have hit limits with ACF or with a page builder. The Matrix and field-layout model is what they have been trying to build by hand.

Teams who want their developer time spent on features rather than on plugin firefighting. The platform shifts the work in that direction.

Teams for whom none of these apply will not see the value. A small WordPress site that works fine should usually stay where it is. I have written more about this in WordPress, Craft or Statamic for founders and marketing directors.

What to do next

If the trade-offs above sound like they fit your team, the next step is a serious comparison rather than a decision. Look at your current WordPress site honestly. Count the plugins. Add up the maintenance hours. Ask the content team where they get stuck. Compare against what a clean Craft build would do for those specific frictions.

See Craft CMS versus WordPress for a side by side, or Craft CMS development for what a senior freelance engagement looks like. If you want a second pair of eyes on whether the move is right for you specifically, get in touch and tell me about the site.