What changes after Drupal 10 end of life?
Drupal 10 will not stop working on 10 December 2026. The Drupal project will stop releasing Drupal 10 updates, including security fixes. Staying on this version will make security reviews, dependency updates and future development harder over time.
Let the audit determine the right upgrade path
You do not need to choose the project type before contacting us. The audit will show which path fits your codebase, infrastructure, business deadline and longer roadmap.
What we audit before planning your Drupal 11 upgrade
From audit proposal to Drupal 11 upgrade
Who should start with a Drupal 11 upgrade audit?
Still using Drupal 7, 8 or 9?
Start with our Drupal EOL migration service.
Drupal migration and platform care in practice
Why the upgrade estimate must be based on an audit
Why work with Droptica on the audit and upgrade?
Yes. We start with a scoped audit. It identifies blockers, risks, assumptions and the recommended delivery sequence before you approve the implementation scope.
We agree on NDA, access rules and the working-copy process before the audit begins. Your team knows which environments we use, who has access and how the review copy will be handled.
Yes. The plan, estimate assumptions and technical findings can support your internal decision and delivery process.
Yes. After stabilization, we can take responsibility for security updates, platform maintenance and a 12-month Care & Growth roadmap.
Frequently asked questions about the Drupal 11 upgrade audit
Drupal 10 reaches end of life on 9 December 2026. After that date, the Drupal project will stop publishing Drupal 10 releases, including security fixes.
No. The website will not automatically stop on 10 December 2026. It will remain on an unsupported core version, which increases security, compliance and dependency risk over time.
No. Supported Drupal upgrades move through consecutive major versions. A Drupal 10 website must move to Drupal 11 before it can later move to Drupal 12.
We check Drupal core, Composer, contributed and custom code, themes, PHP, database, hosting, deployment, integrations and critical user paths.
You receive a recommended upgrade path, prioritized blockers, scope assumptions, a tailored effort and cost estimate, and a testing and release plan.
The price depends on the website size, custom code, integrations and available documentation. Before work begins, we send a proposal that defines the audit scope, schedule and price.
The timeline depends on the platform and access. We confirm it in the audit proposal before work begins.
No. You can use the audit with your internal team. If you want Droptica to deliver the upgrade, we will prepare a separate implementation proposal.
We usually need read access to the code repository and Composer files, information about environments and hosting, and a list of critical integrations and business paths.
We check for a compatible release, an active issue or patch, and supported alternatives. If the module is essential, we include the required replacement or custom work in the plan and estimate.