Drupal 10 End of Life: Upgrade or Rebuild? A Decision Framework for December 2026

Drupal 10 reaches end of life on 9 December 2026. Organisations still running Drupal 10 need to decide whether to upgrade or rebuild before security support ends. For some, a Drupal 11 upgrade will be the right investment. For others, years of customisations, growing technical debt, and changing business requirements make a rebuild the better option.

The challenge is that the same deadline leads to two very different outcomes. An upgrade extends the life of an existing website. A rebuild addresses structural issues that a version upgrade cannot.

In this article, we explain what Drupal 10 end of life exactly means, what your options are, and the factors that should drive the decision to upgrade or rebuild.

A few things worth knowing before you read further:

• Drupal 10's last supported minor release, 10.6.x, loses all security coverage on December 9, 2026.
• Drupal 12 arrives the same week, but you can't jump to it directly from Drupal 10.
• Already on Drupal 11? Your next move is 11.5, not 12.
• The audit that decides upgrade versus rebuild almost always takes longer than teams plan for.

What Actually Happens When Drupal 10 Reaches End of Life?

End of life is a specific term. It marks the point at which a software version no longer receives official security support from its maintainers. For Drupal, this means the Drupal Security Team stops releasing security updates for that version, and the ecosystem gradually shifts its focus to supported releases.

For Drupal 10, end of life falls on 9 December 2026. From this date, organisations running Drupal 10 should expect the following changes:

• Drupal 10 core will no longer receive security updates.
• Drupal 10-compatible branches of contributed modules will gradually stop receiving security fixes as maintainers move to supported versions.
• Organisations may face compliance challenges, as many regulatory frameworks and procurement standards require supported software.

Reaching end of life does not affect the availability of a Drupal website. The site will continue to operate, but it will do so without official security support. Any vulnerabilities disclosed after 9 December 2026 will not receive official security fixes for Drupal 10 which increases security risk and the long-term effort required to maintain the platform.

The impact extends beyond technology. For example, a hospital using Drupal to manage patient-facing services may continue to operate its website after Drupal 10 reaches end of life. But, because the platform no longer receives official security updates, the organisation could face compliance concerns during a HIPAA audit despite the website functioning normally.

Is Your Drupal 10 Site's End-of-Life Date Really December 9, 2026?

Not necessarily. While 9 December 2026 marks the end of life for the Drupal 10 release line, the exact date depends on the minor version your website is running. Each minor release has its own support lifecycle, which means some Drupal 10 websites lose security support well before the final end-of-life date.

December 9, 2026, full Drupal 10 end of life. This is the hard stop for Drupal 10.6.x, the last minor release in the 10.x line, confirmed on Drupal's official core release schedule.

June 17, 2026, Drupal 10.5.x security cutoff. If you're on 10.5, you lose security support nearly six months before the headline deadline. Update to 10.6 or move to Drupal 11 before this date.

Already past end of life. Drupal 10.4.x and earlier minor releases stopped getting patches on December 10, 2025. If you're still here, you're exposed right now, not in December.

Here's the fuller release sequence as per Drupal's official release schedule:

Should You Jump Straight to Drupal 12, or Upgrade to 11 First?

No. Drupal does not support skipping major versions. If your website runs on Drupal 10, the next supported upgrade path is Drupal 11. You cannot upgrade directly from Drupal 10 to Drupal 12.

Your current Drupal version determines the appropriate next step.

Drupal 11.5 and Drupal 12 ship in the same release window, so if you're already on Drupal 11, getting current on 11.5 is a smaller, lower-risk step before the major version jump. There's no direct path from Drupal 10 to Drupal 12.

Every Drupal 10 to Drupal 11 upgrade plan has to pass through Drupal 11 first, which is exactly why teams still on Drupal 10 need to start now rather than waiting to see what Drupal 12 looks like. 

Upgrade or Rebuild? How to Actually Decide

Drupal 10 end of life does not automatically require a rebuild. For many organisations, upgrading to Drupal 11 is the fastest and most cost-effective approach. However, if the website has accumulated significant technical debt or no longer supports business requirements, rebuilding may provide better long-term value.

Before deciding, evaluate your website against the following questions:

• Does the website still support your current business goals?
• Do editors and developers work efficiently, or are workflows becoming increasingly difficult to maintain?
• Does the current architecture support future integrations, features, and growth?

If the answer to most of these questions is yes, a Drupal 11 upgrade is usually the right choice. If the website struggles to meet business needs or has become expensive to maintain, a rebuild may deliver a better return on investment.

The table below summarises the Drupal upgrade vs rebuild cost and timeline differences between the two approaches.

How Do You Know if Your Site Is Actually Ready to Upgrade?

Let's say you decide to go down the upgrade path, how do you decide if your website is even ready for this upgrade. Follow this Drupal 11 readiness check to confirm your upgrade.

• Run the Upgrade Status module to identify deprecated APIs and Drupal 11 compatibility issues.
• Review contributed modules to confirm they are actively maintained, not just marked as compatible.
• Validate hosting and PHP requirements to ensure your infrastructure supports Drupal 11.
• Audit custom code to identify legacy implementations, unsupported dependencies, and areas that require refactoring.

What Does a Drupal 10 to Drupal 11 Upgrade Actually Look Like?

A Drupal 10 to Drupal 11 upgrade plan follows a structured process, but the scope and timeline depend on the complexity of the website, the volume of custom code, and the health of its dependencies. Completing each phase before moving to the next reduces project risk and minimises disruption during deployment.

A typical Drupal 10 to Drupal 11 upgrade includes the following stages:

• Audit. Run Upgrade Status, catalog every deprecated call in custom code, and cross-reference contributed modules against current core support.
• Remediate. Fix flagged deprecations, replace or patch modules that haven't caught up, and confirm PHP and hosting requirements are met.
• Staging upgrade. Run the Composer upgrade and database updates on a staging copy, not production.
• Test. Bring in the people who actually use the site daily. Automated checks catch code problems; they don't catch a broken editorial workflow.
• Cutover. Schedule production deployment during low-traffic hours, with a rollback plan ready before you start, not improvised after something breaks.

A well-scoped Drupal 10 six-month upgrade plan may need additional time for remediation and testing if the project involves extensive customisations or legacy code. Also, keep in mind that if your assessment indicates that a rebuild is more appropriate than an upgrade, the project will follow a different timeline.

The Bottom Line

Every Drupal 10 website does not require the same approach. Some websites only need a well-planned upgrade to Drupal 11, while others benefit more from a rebuild. The right choice depends on the current state of the website, not assumptions or deadlines.

DrupalFit helps you make that decision with a comprehensive Drupal website audit covering security, accessibility, performance, SEO, compliance, and overall platform health.

Run an audit before planning your Drupal 11 migration and use the results to determine the right path for your website.

Run an audit now!

FAQs

Can I skip Drupal 11 and go straight to Drupal 12?

No. Drupal doesn't support skipping major versions. If you're on Drupal 10 today, you have to upgrade to Drupal 11 before you can move to Drupal 12.

Is Drupal 11 stable enough for production use?

Yes. Drupal 11 has been in general release since 2024, and most actively maintained contributed modules already list Drupal 11 compatibility.

What happens if we miss the December 9, 2026 deadline?

Nothing breaks immediately. Your site keeps running. But any vulnerability disclosed against Drupal 10 core or contributed modules after that date has no official fix coming, and compliance audits will flag the site as unsupported.

Can I upgrade directly from Drupal 8 to Drupal 10?

No. Drupal upgrades are sequential. Drupal 8 sites need to pass through Drupal 9 before reaching Drupal 10, and Drupal 10 sites need to pass through Drupal 11 before reaching Drupal 12.