Release information checked September 29, 2026. Drupal 10 reaches end of life on December 9, 2026, according to the official Drupal core release schedule. Drupal 12’s stable release is currently planned for the week of December 7, 2026. Treat the deadline as a reason to begin an upgrade assessment now.
End of life does not mean a Drupal 10 website suddenly stops loading. It means that Drupal core will no longer issue Drupal 10 releases after that date. Continuing to operate an unsupported version leaves the site without ongoing community core maintenance and security releases for that version.
Use Drupal 11 as the next supported step
For a production Drupal 10 site, plan the move to supported Drupal 11 first, then prepare for Drupal 12. Do not assume changing a Composer version constraint can skip an entire major-version upgrade. Drupal publishes separate guidance for Drupal 10 to 11 and Drupal 11 to 12.
As of this review, Drupal 12 is still a pre-release target. Use its release notes and developing upgrade documentation for readiness testing. Confirm the final supported source version, hosting requirements, and extension compatibility before scheduling a production move to Drupal 12.
Find the blockers before estimating the upgrade
A website with a small set of maintained modules can have a different upgrade path from one with custom integrations and abandoned extensions. Create an inventory that explains what each dependency does for the business.
- Record the installed core version, modules, themes, and custom code.
- Identify unsupported dependencies and choose replacements where needed.
- Review deprecated APIs and configuration with compatibility tools and code review.
- Check PHP, database, command-line, and deployment requirements for each step.
- List the editorial workflows and integrations that must pass acceptance testing.
Prioritize uncertainty. A module that owns an important business process deserves investigation before a deployment date is promised. A compatibility scanner helps find technical gaps, but it cannot confirm that customers can still complete a task or that editors understand a changed interface.
Rehearse, test, and keep a recovery option
Perform the upgrade on an isolated copy with representative data. Test login, permissions, content editing, media, search, forms, scheduled jobs, and integrations. Review mobile layouts, metadata, and key URLs alongside the technical checks.
Prepare matching database, files, and code backups, then rehearse the deployment sequence. Define who makes the go/no-go decision and how new content will be handled if a rollback is needed. Avoid making the first full rehearsal the production launch.
How Druproid Support can help
Druproid Support can help assess your Drupal 10 site, plan the move to Drupal 11, and prepare its code and infrastructure for Drupal 12. The assessment should produce a dependency inventory, a list of blockers, a testing plan, and a proposed scope and timeline.
Request your Drupal upgrade assessment and share the site URL, installed Drupal version, hosting details, and important integrations. Start before the support deadline so there is time to resolve compatibility work and choose a tested release window.