Drupal 10 end of life and Drupal 11 readiness
A Drupal 10 site does not break overnight. The risk appears when the upgrade plan is left too late and dependencies are not ready.
Why this already matters
Drupal.org publishes the official Drupal core release schedule. According to that schedule, Drupal 10 reaches end of life on December 9, 2026.
This does not mean every Drupal 10 site must be rebuilt immediately. It means site owners should know whether their site is ready for Drupal 11 before the deadline becomes close.
A weak plan is to wait until support has ended. A better plan is to check:
- which Drupal 10 minor version is running;
- whether PHP and the database match Drupal 11 requirements;
- whether contributed modules support Drupal 11;
- whether custom code uses deprecated APIs;
- whether the upgrade can be tested without touching the live site.
Once these points are clear, a Drupal 11 upgrade is no longer an unknown risk. It becomes a list of specific tasks.
Modules often decide the real effort
Upgrading Drupal core is only part of the work. On many sites, contributed modules and custom code decide the actual scope.
If a module does not support Drupal 11, there are three options. It must be updated, replaced or removed from the workflow. The worst time to discover this is when the launch date is already fixed.
The same applies to custom modules. Older code may use deprecated APIs, old service definitions or dependencies that still work on Drupal 10 but block the next step.
Readiness checks do not have to be large
The first check can be quite practical. Review versions, modules, PHP requirements, logs and the main user flows. For a business-critical site, this should be followed by a trial upgrade in a staging environment.
That gives answers to three questions:
- is the upgrade small;
- does the site need cleanup first;
- does any part need replacement or a separate decision.
When WebPro reviews Drupal readiness, we usually connect the result to a Drupal migration or Drupal maintenance plan. That way the review does not remain a separate document. It becomes action.
When to start
If a Drupal 10 site is simple and well maintained, the upgrade may be straightforward. If the site is old, has many modules or supports business-critical work, readiness should be checked months before the end of support.
A practical rule is simple: if the site supports sales, service or public information, the version upgrade should not be last-minute work.
A Drupal 11 readiness check is cheaper than rushed repair work. It helps decide whether the site needs an upgrade, light cleanup or a wider technical plan.
Kaido Toomingas
WebPro Company OÜ
Need Drupal help?
If the article describes your situation, you do not have to read everything first. A real person will help you choose the next step.