End of support for Drupal 10

After 9 December 2026, Drupal 10 gets no more security fixes.

Your site doesn't switch off that day and keeps running as before. Moving it to Drupal 11 is usually an update, not a rebuild from scratch.

Email me about your site Is your site on Drupal 10?

I'm Emanuel Greucean. I checked these facts against drupal.org on 25 October 2026.

What changes on 9 December

Drupal 10's end of life is 9 December 2026, and no new Drupal 10 release comes out after that date.
A security problem found after that day stays unfixed in Drupal 10.
Drupal 10.6 is the last minor release of Drupal 10, and its security support ends in that same week, the week starting 7 December 2026. So 9 December is the date that counts.
Drupal 12 comes out that week too. There is no direct road from 10 to 12, so a Drupal 10 site goes through 11 either way, and there is no reason to wait for 12.

Why it matters beyond security

Beyond security, a site left on 10 has more work ahead.

A site still on 10 after December faces two updates, 10 → 11 and then 11 → 12. A site already on 11 has just one.
drupal.org has announced that a site on 11.3 or older must first move to 11.4 or newer, and only then to 12.

How to tell if your site is on Drupal 10

You can find out yourself, in two ways.

In your site's admin, open Reports → Status report, at /admin/reports/status. It shows the Drupal version.
If you can't get into the admin, open the source of the home page and look for the Generator meta tag. It shows the major version, for example Drupal 10. Or ask whoever looks after your site.
If you see 10, the December deadline applies to you too. If you see 9, 8 or 7, read further down for what comes next for your site.

10 → 11 is an update, not a new site

Drupal 11 is built from the last version of Drupal 10, with the old code taken out. That is why 10 → 11 is an in-place update with Composer, once the site's code and modules are ready. The site isn't rebuilt, and no content gets migrated. The four points below are what I check for you, so you don't need to follow every detail.

First, the version

A Drupal 10 site has to run at least 10.3.0 before it can move to 11. A site on 10.6 has to land on 11.3.0 or newer.

Hosting

Drupal 11 needs PHP 8.3 and at least MySQL 8.0, MariaDB 10.6, PostgreSQL 16 or SQLite 3.45. If your hosting is older, it has to be brought up to date before the update.

The modules

Every module taken from drupal.org and every patch applied needs a version for Drupal 11. Six modules left core in Drupal 11 (Actions UI, Activity Tracker, Book, Forum, Statistics and Tour). If you use one and want to keep it, you install its drupal.org version before the update and don't uninstall it, because you would lose its configuration.

Your custom code

Your site's custom modules have to stop using the APIs that Drupal 10 marked as deprecated. Upgrade Status finds them, and Drupal Rector fixes some of them automatically.

I can't tell you how hard your update is until I've seen your site's code.

If your site is on 9, 8 or 7

Drupal 9

Drupal 9 lost support on 1 November 2023. A site on 9 has two updates to make before it reaches 11. The first, 9 → 10, includes the move from CKEditor 4 to 5, which drupal.org says needs a human watching it, and a check of themes built on Classy or Stable.

Drupal 8

Support for Drupal 8 ended on 17 November 2021. A site on 8 goes through three updates on its way to 11.

Drupal 7

Drupal 7 ran out of security support on 5 January 2025. Leaving it is a migration to a new site, not an update.

How a Drupal 7 migration works

How I would run the update

First I look at your site in a short, free readiness check, so we both know what needs doing before we agree on the work.

The readiness check. I start from the code repository and composer.json, with no access to the server your site runs on. I look at an Upgrade Status report, the custom modules and the hosting.
A fixed scope. I tell you what has to change and what stays the same, before the work starts.
The update and the tests, on a copy. I run the update on a copy of the site, never on the one your visitors see, and test it there until we agree it's ready.
Go-live. Before the new version goes online, I take a backup of the database and the code, so the site can go back to how it was if it needs to.

What you get from the check

The versions your site runs on today, of Drupal, PHP and the database.
What blocks the move to 11, in order of priority.
The road I recommend to Drupal 11.
The fixed scope for the update.
How we test the site, and how we take it back to the old version if something doesn't work.

The plan stays yours. If you want, you can give it to another developer, who runs the update instead of me.

I've worked with Drupal since 2009, on versions 5 to 11. From 2014 to the end of 2025 I was a Drupal architect and backend lead, on contract, for the US agency Kalamuna. There I did the Drupal 7 → 8 migration of a US media platform myself. After Drupal 8, my work at Kalamuna was mostly version upgrades, and after each one the site worked as before. More about me

If your agency has clients on Drupal 10

If you have more Drupal 10 clients than people to update them, I take on part of the work, under your name. I can also take on migrations of sites still on Drupal 7, and I run the readiness check the same way I would for a direct client. I work from Timișoara, in Romania, on Eastern European Time. I can start now.

Questions about Drupal 10

Will my site stop working on 9 December?

No. It goes on running exactly as it does today. The difference is that from then on, nobody publishes security fixes for Drupal 10.

Can I skip straight to Drupal 12?

No. Each major update starts from the major version before it, so the road to 12 runs through 11.

Do I need a new site?

For 10 → 11, usually not. You keep the same site, with the same content, and it gets updated in place. You only need a new site when you're leaving Drupal 7.

How long will the update take?

It depends on the site, which is why I start with the readiness check. After it I can tell you how long the work takes and what it covers, before you decide.

What if I do nothing?

You stay on a version of Drupal that nobody fixes any more. Any security problem announced after 9 December stays unfixed on your site.

How long is Drupal 11 supported?

drupal.org hasn't put an end date for Drupal 11 on its release schedule yet.

What access do you need?

For the check, the code repository and the composer.json file are enough. I only need access to the production server when the site moves to the new version, because until then I work on a copy.

What if a module isn't ready for Drupal 11?

The check first finds every module that has no Drupal 11 version yet, for example with the command composer why-not drupal/core ^11. We decide together what to do about each one and put it in the fixed scope, before the update.

Do I have to hire you for the update after the check?

No. The plan from the check is yours. You can run the update with me, with your own team or with another developer.

Email me about your Drupal 10 site

Send me your site's address and its Drupal version, if you know it. That's where the readiness check starts.

emanuel@webbership.dev