Drupal 10, 11 and 12 readiness check

Late 2026 is a practical checkpoint for Drupal sites. Drupal 10 reaches end of life, Drupal 12 arrives and it is better to know the real upgrade blockers before they become urgent.

When this helps

  • the site runs on Drupal 10 and the upgrade plan is unclear;
  • the move to Drupal 11 has stalled or was postponed;
  • PHP, Composer, modules or custom code may block the next upgrade;
  • you need realistic scope before budgeting, procurement or changing providers.

What we check

  • Drupal core and module support status;
  • PHP version, Composer workflow and dependency lock state;
  • custom modules, theme layer and deprecated API usage;
  • security update process, backups and test environment;
  • critical forms, roles, integrations and editorial workflows.

What you get

  • a short risk map;
  • a recommendation: maintenance update, Drupal 11 upgrade or larger migration;
  • an initial hour range and priorities;
  • a list of workflows that must be tested before release;
  • a clear view of whether the work is urgent or can be planned calmly.

Why WebPro

WebPro has worked with Drupal since the Drupal 6 generation. Our technical lead Kaido Toomingas has been active on Drupal.org for more than 18 years, maintaining projects and contributing to documentation and issue queues; the same team handles client maintenance, testing and development work.

Why late 2026 matters

Drupal core's official schedule says Drupal 10 reaches end of life on 9 December 2026 and Drupal 12 is planned for the same week. That does not mean every Drupal 10 site breaks on that date. It means security support and upgrade planning should not be left until December.

If the site is simple, the check may lead to a small maintenance upgrade. If the platform has custom modules, an old theme, integrations or no test environment, it is better to make those risks visible early.

How we start

To begin, send the website address and a short description. If access is available, we review the code, Composer files, module state and test environment. If access is not available yet, we start with public signals and prepare a list of what needs to be collected.

Related services: Drupal maintenance, Drupal upgrade, technical audit.

Next step: send the website address and known Drupal version. If you do not know the version, the website address is enough.

Fill in the contact form