Contact us
-
Insights

Why we’re moving from WordPress to Payload

Jay · Senior Digital Producer / Platypus
6 · November 11th, 2026

Sod is adopting Payload as our preferred platform for the websites we build and support, and will phase out WordPress support by 31 December 2027. This page sets out why we’re making the change, how the two platforms compare, and what it means for your site.

Why we’re making the change

Keeping a WordPress site secure and stable takes more work every year. Core, plugin and theme updates arrive regularly, and each needs to be assessed and tested to avoid conflicts or unexpected issues. Urgent security vulnerabilities can also require a response within hours.

We manage all of this for you today, but a growing share of that effort goes into keeping sites patched rather than improving them. Moving to Payload reduces our reliance on third-party plugins and gives us greater control over how features are developed, updated and tested. This makes ongoing maintenance more predictable and allows us to focus more of our time on improving your site.

What Payload is and why we chose it

Payload is an open-source content management system built with TypeScript and React, and it runs natively inside Next.js, a modern framework designed for building fast, flexible websites. We already build and support Payload sites, so this is a platform our team knows well.

  • Fewer moving parts: we build and manage features within a more controlled codebase, reducing reliance on third-party plugins.
  • Content shaped around your business: we set up fields and page types to match how you work, so editors enter content into clearly labelled fields rather than a blank page.
  • Performance and search visibility: Next.js gives us greater control over page loading, rendering and technical SEO. Clean, structured content also provides a strong foundation for traditional search engines and AI-powered discovery.
  • Built-in essentials: Payload supports access control, drafts, version history, live preview and multilingual content without needing separate third-party plugins for each feature.
  • Content you can reuse: the same content can feed your website and any other channels or tools you add later, without being re-entered.

Payload has strong backing. Figma acquired it in June 2025 and committed to keeping it open and independently usable. Figma is also the design tool we already rely on, so our design and build work sit even closer together.

How WordPress and Payload compare

WordPress Payload
Security Relies on many third-party plugins, each a potential entry point that needs fast patching Reduces reliance on third-party plugins, with features developed and maintained within a more controlled codebase
Maintenance Frequent core, plugin and theme updates, with a risk that one update breaks another More controlled updates, managed by our team and tested before release
Editing Familiar page editor, but layouts can be inconsistent and plugins add clutter to the admin Clean admin with structured fields built for your content, plus drafts, version history and live preview
Performance Performance depends on hosting, caching, plugins and site configuration Modern Next.js front end, with pages that can be pre-built and served quickly
Flexibility Huge plugin library for quick add-ons Custom features built to fit, and content reusable across websites, apps and integrations
Long-term control Plugins can change, be abandoned or move to paid licences Open-source platform with greater control over the features and code we build and maintain for you

Things to consider

  • Your team will learn a new admin. It’s designed around your site’s content and workflows, and we’ll walk your editors through it at handover.
  • Some supporting services work differently. In WordPress, we use plugins for services such as forms, security and email delivery. Payload handles some of these features natively, while others require integration or configuration. We’ll account for these differences when planning your migration.
  • Your site needs to be migrated. We’ll review your existing content, features and integrations, then scope the work needed to move them to Payload. We’re developing migration tools to make this process more efficient, and we’ll plan the transition around your calendar to minimise disruption and protect existing search visibility.

More reading

About Jay
Senior Digital Producer / Platypus
More articles like this one