Service
Drupal 10 → 11 readiness review
Drupal 10 reaches end of life in December 2026. This is a scoped version of our audit that answers one question: what does moving this platform to Drupal 11 actually cost?
For most Drupal 10 sites this is a minor upgrade rather than a project, and an agency telling you otherwise is selling you something. What decides it is the code around the core: contrib modules with no Drupal 11 release, patches applied to core, and custom modules written against APIs that have since been removed. The review tells you which case you are in before you budget for it.
Scope
How the work is delivered
-
Core and contrib readiness
Every installed module checked against its Drupal 11 status: released, patched, abandoned, or replaced by something now in core. Anything with no path forward is named, with what replacing it takes.
-
Custom code against removed APIs
The modules and theme written for this site, checked against the APIs Drupal 11 dropped. This is the part that turns a small upgrade into a large one, and the part scanners do not catch.
-
Patches applied to core
Core patches get lost in an upgrade unless somebody knows they are there. We find them and say which are still needed and which the version you are moving to has already absorbed.
-
Effort and sequence
Hours against each blocker and the order to clear them in, so the upgrade becomes a line in a budget instead of an open question.
-
Timing against December 2026
After the end-of-life date Drupal 10 stops receiving security advisories. We say how long the work needs and when it has to start to land before then.
Talk through the build
Send the platform, constraints, and timeline. We'll reply with the engineering questions that decide scope.
- Reply within one business day, weekday hours UA / EU.
- 30-minute discovery call when it is useful.
- Scope written around deliverables, risks, and ownership.