How to Prepare Your Drupal 10 Website for a Smooth Upgrade to Drupal 11

Staff Reporter

Duncan Worrell of Zoocha outlines why organizations should start preparing for Drupal 11 now, despite Drupal 10’s support continuing into 2026. He emphasizes that early, incremental work—like installing the Upgrade Status module and updating to PHP 8.3—can reduce future risks and unlock D11’s new features sooner. Zoocha clients are already beginning these readiness steps.

The article breaks the upgrade process into three key stages: readiness analysis, upgrading the Drupal 10 site for compatibility, and finally switching core code to Drupal 11. Tools like Drupal Rector and AI assistants help modernize custom code, and contributed module updates are often straightforward. The infrastructure shift to PHP 8.3 is critical and can be tackled now.

Worrell argues for a phased approach to avoid last-minute rushes and testing gaps. Zoocha’s process includes layered QA, peer reviews, and client validation. While tailored to Zoocha’s services, the guide provides broadly useful advice for planning a Drupal 11 upgrade.

Source Reference

Title

Thinking about Upgrading to Drupal 11?

Byline

Duncan Worrell

Date of Publication

05 June 2025

Organization

Zoocha

Drupal 11

Drupal Upgrade

Drupal 10

Website

PHP 8.3

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.