Drupal 10 reaches end of life on December 9, 2026. After that date, the Drupal project will no longer release updates for Drupal 10, including security fixes. That deadline is confirmed in the official Drupal core release schedule.
If your organization still runs Drupal 10, now is the time to confirm your upgrade plan, identify anything that could delay it, and reserve time for testing.
Your website will not automatically switch off on December 9. The concern is continuing to rely on a platform that no longer receives updates from the project. A working website and a supported website are different measures of readiness.
Check your actual version first
“Drupal 10” alone does not tell you whether your site is currently supported. Drupal 10.6 is the final minor release, and earlier branches have already left security support. For example, Drupal 10.5 reached the end of its security support in the week of June 29, 2026. The release schedule lists the supported branches.
Ask your development partner for the exact installed core version, the status of contributed modules and the hosting platform’s supported software versions. If those answers are unclear, start with an inventory rather than assuming that routine hosting maintenance covers the whole application.
Does this mean you need a new website?
An end-of-life date does not, by itself, mean you need a redesign.
Drupal provides an upgrade path from Drupal 10 to Drupal 11. The amount of work depends on your site’s modules, theme, custom functionality and integrations. A site with well-maintained dependencies may need less work than one relying on abandoned modules or undocumented custom code. The official upgrade guide explains the preparation required.
We recommend separating the essential upgrade from optional improvements. Keep the existing content, URLs and workflows wherever practical. Put a redesign, new functionality or a larger content project into a separate scope unless there is a clear technical reason to combine them.
That gives your team a more useful question to answer: what must change to keep this website supported, and what can wait?
What should a Drupal upgrade assessment cover?
A useful assessment should produce a plan your team can act on, not just a list of outdated packages.
Modules and custom code. Identify compatible releases, custom code that uses deprecated APIs, patches and modules that need an alternative. Drupal’s Upgrade Status module helps identify compatibility issues, but the findings still need interpretation and testing.
Theme and editorial workflows. Review templates, components, content editing, media handling and permissions. Your editors should be able to do their everyday work after the upgrade.
Hosting and dependencies. Confirm that PHP, the database, Composer and other services meet the requirements of the target Drupal release. The Drupal 11 upgrade guide currently specifies PHP 8.3 or later; the exact supported combination should be checked for your target version and hosting environment.
Business-critical integrations. Include forms, CRM connections, search, authentication, payments, analytics and any scheduled data exchanges. A homepage loading successfully does not prove that a lead reaches your sales team or an order completes correctly.
Release and recovery. Define the deployment steps, maintenance window, verified backup, rollback approach and named people responsible for acceptance.
A practical plan for the weeks ahead
If you are starting in November, avoid leaving discovery until the final week before the deadline. Holiday schedules, approval cycles and third-party dependencies can reduce the time available.
- Establish the starting point. Confirm versions, access, backups and the important user journeys. Agree who owns the upgrade and who can approve the release.
- Resolve the blockers. Update compatible dependencies and address custom code or module gaps in a controlled development environment. Turn unknowns into a prioritized work list with estimates.
- Rehearse and test. Use a protected test environment with representative content. Check desktop and mobile layouts, editing, forms, integrations and the journeys that matter to your organization.
- Release with time to verify. Schedule deployment before the support deadline, leaving room to investigate issues. Check the live site afterward and record what was tested, what passed and anything still outstanding.
If the work cannot be completed before December 9, document the remaining exposure and discuss a specific interim plan with your technical partner. Do not assume a hosting upgrade or a generic security service replaces Drupal core support.
How One Cloud can help
One Cloud brings more than 20 years of Drupal experience to websites that organizations depend on every day. We can help assess your Drupal 10 site, identify upgrade blockers, scope the work and carry it through development, testing and a controlled release.
We can also help separate immediate maintenance needs from longer-term improvements, so you have a clear view of the priorities, cost and decisions ahead.
Still running Drupal 10? Let’s review your path forward. Talk to One Cloud about your Drupal upgrade. Tell us what your website supports, who maintains it today and any deadlines or concerns. We can help you work out the next practical step.