-

Get a Drupal 11 upgrade audit, plan and estimate

Drupal 10 reaches end of life on 9 December 2026. Before you commit to an upgrade, we audit your website, identify blockers and prepare a plan and cost estimate tailored to your platform. If you want us to deliver the upgrade, we will prepare a separate implementation proposal after the audit.

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.

security

Security updates stop

Newly discovered Drupal 10 core vulnerabilities will no longer receive fixes from the Drupal project after end of life.

development

Platform constraints grow

PHP, database, library and contributed module support will continue to move forward. An unsupported core version will narrow the safe update path.

devices

Your internal deadline may be earlier

Testing, procurement, security review and deployment freezes need time. A production release planned for the last days before EOL leaves little room to fix unexpected blockers.

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.

Focused upgrade

The audit confirms that Drupal 10 is current, contributed modules support Drupal 11, custom code is limited and the release process works. The implementation can focus on compatibility changes, regression testing and deployment.

Stabilize, then upgrade

Legacy code, dependency conflicts, missing environments or weak release controls must be fixed before the Drupal 11 upgrade can proceed safely.

Upgrade with modernization

Performance, editor workflow, accessibility or SEO issues should be addressed around the upgrade. The audit separates work required before EOL from improvements that can follow in a Care & Growth roadmap.

What we audit before planning your Drupal 11 upgrade

We review the parts of the platform that can block the upgrade, change its cost or create risk during release. The audit 
covers Drupal core, the codebase, infrastructure and critical business paths.

Drupal core and Composer

We confirm the current Drupal release, Composer constraints, patches and packages that can block Drupal 11.

Contributed modules

We check Drupal 11 compatibility, available releases, active issue queues and modules that may need replacement or a patch.

Custom modules and themes

We identify deprecated APIs, removed dependencies and frontend code that requires manual changes.

PHP, database and hosting

We compare the target Drupal 11 requirements with the current runtime, database, web server and hosting limits.

Deployment and rollback

We review environments, configuration management, backups, CI/CD, deployment steps and the path back if release checks fail.

Forms and integrations

We identify external APIs, search, queues, cron jobs, forms and data flows that need regression tests.

Multisite and editorial workflows

We map shared code, site-specific configuration, languages, permissions and the tasks editors must complete after the upgrade.

SEO, accessibility and compliance

We include URL behavior, metadata, structured content, critical accessibility checks and requirements that affect release approval.

What you receive from the audit

You receive a decision-ready package prepared for your website. It gives management a budget basis and gives the delivery team a practical upgrade plan.

• A baseline of the current Drupal, PHP and dependency versions.
• A prioritized list of blockers and risks.
• A recommended upgrade path.
• A defined scope with assumptions and exclusions.
• A tailored effort and cost estimate.
• A proposed delivery sequence.
• A regression testing, deployment and rollback plan.
• A basis for a separate Drupal 11 implementation proposal.

You can use the audit with your internal team. If you want Droptica to deliver the upgrade, we will prepare a separate implementation proposal based on the approved plan.

From audit proposal to Drupal 11 upgrade

Tell us about the website

Send us the website URL, current Drupal version, business deadline and any known technical constraints.

Receive an audit proposal

We define the audit scope, required access, schedule and price before the work begins.

We run the audit

We review the codebase, modules, hosting, integrations, release process and critical user paths on a controlled copy.

Receive the plan and estimate

We present the blockers, recommended path, delivery sequence and cost estimate tailored to your website.

Choose the implementation route

You can use the documentation with your internal team or ask Droptica to deliver the Drupal 11 upgrade.

Request an implementation proposal

If you choose Droptica, we turn the approved audit scope into a separate upgrade proposal with implementation stages and a release plan.

Who should start with a Drupal 11 upgrade audit?

Custom Drupal platforms
Your Drupal 10 website includes custom modules, a custom theme, external integrations or editorial workflows that must keep working after release.

Multilingual sites and multisite portfolio

Shared code, country-specific configuration and many release paths require an inventory, common test plan and rollout sequence.

Security and compliance-driven organizations
Your internal policies, procurement process or sector requirements call for a supported platform and documented release controls.

Still using Drupal 7, 8 or 9?

Start with our Drupal EOL migration service.

Drupal migration and platform care in practice

These projects show that we can take responsibility for the implementation after the audit. They are not presented as Drupal 10 to 11 case studies.

MSDynamicsWorld: Drupal migration for a content and lead platform

We migrated MSDynamicsWorld from Drupal 7 to Drupal 10 while preserving existing data and functions. The work also covered a new user interface, Apache Solr search and integrations with Mautic, Amazon S3 and external video APIs.

Exide Group: platform updates and continued Drupal care

We removed legacy code, updated Drupal core and contributed modules, introduced Composer and Continuous Integration, and prepared dedicated development and test environments for Exide Group's multilingual Drupal platform and ongoing care.

Why the upgrade estimate must be based on an audit

The Drupal version alone is not enough to price the upgrade responsibly. The audit measures the work hidden in the codebase, infrastructure, integrations and release process.

Code and modules
The number and state of contributed modules, custom modules, themes, patches and deprecated APIs affect the amount of compatibility work.

Infrastructure and integrations
PHP, database, hosting, CI/CD, search, external APIs and scheduled jobs determine what must change outside Drupal core.

Testing and release scope
Multisite, languages, editorial roles, accessibility, SEO, compliance and critical user journeys define the regression and rollout effort.

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.

Request a Drupal 11 upgrade audit proposal

Send us your website URL, current Drupal version and target date. We will review the information and prepare an audit proposal with the scope, required access, schedule and pricing.
 
After the audit, you will receive a tailored upgrade plan and estimate. If you want us to implement it, we will prepare a separate Drupal 11 upgrade proposal.