Drupal 10 reaches end of life on 9 December 2026, and Drupal 12 is scheduled for release that same week. Drupal 10 sites can't jump straight to 12, and Drupal 11 sites need to be on 11.3 or later before they can upgrade. Here are the dates, the requirements and the route for each version.
drupal_10: end of life 9 Dec 2026 drupal_11.3: security support ends week of 7 Dec 2026 drupal_12: release scheduled week of 7 Dec 2026 drupal_11: supported until at least Drupal 13 (mid to late 2028) upgrade_to_12_from: 11.3.0 or later
From the Drupal core release schedule. "Week of" dates are scheduled release weeks and can move. Drupal 12 already missed its June and August 2026 release windows, so check drupal.org before you plan around a specific day.
Drupal 7 stopped receiving security support from the Drupal security team.
Security support ended for Drupal 11.2.x and 10.5.x.
12.0.0-alpha1 on 2 September, beta1 on 30 September and beta2 on 14 October, for testing modules and sites.
Drupal 12.0.0-rc1 and 11.5.0-rc1 scheduled.
Scheduled. Security support ends for Drupal 11.3.x and 10.6.x the same week.
No more security releases for Drupal 10. Drupal 10.6 is its last minor version.
Drupal 11 is supported at least until Drupal 13 is released. No exact date has been set.
Not sure which version you're on? Ask your developer, check Reports → Status report in the Drupal admin, or run drush status.
Deadline: 9 December 2026
You can't go straight to Drupal 12. Update to the latest Drupal 10.6 release, then upgrade to Drupal 11, ideally the latest 11.x minor. That keeps you supported until at least 2028, and Drupal 12 can come later.
10.611.4 / 11.512 later
Security support already ended
Drupal 11.2 lost security support when 11.4.0 came out at the end of June 2026. Update to the latest 11.x minor now. That's usually a routine update, not a project.
11.x11.4 / 11.512 when ready
Security support ends week of 7 December 2026
11.3 is the minimum version you can upgrade to Drupal 12 from, but its security support ends the week Drupal 12 comes out. Move to 11.4 or 11.5 first and update your contributed modules while you're there.
11.311.4 / 11.512 when ready
Plan Drupal 12 at your own pace
You're on a supported version. Keep up with monthly security releases, start replacing modules that are leaving core, and plan the move to Drupal 12 once the contributed modules you rely on support it.
11.4 / 11.512
End of life 5 January 2025
Two options. Migrate to Drupal 11 now, while the tools are still in core: Drupal 12 removes the Migrate Drupal module, and it won't move to a contributed project. Or, if you need more time, keep the site supported with a certified extended support provider while you plan the move.
Drupal 7 extended support options ↓
711 (migration)12 later
Drupal 7 gets no official security fixes any more, but the Drupal Association certifies commercial providers that keep releasing them. I can work with the provider you choose to keep your site patched, monitored and documented for auditors until you're ready to migrate.
| Provider | What it covers | How it's delivered | Good to know |
|---|---|---|---|
| HeroDevs NES for Drupal ↗Certified by the Drupal Association | Security updates for Drupal 7 core and contributed modules. Custom modules, modules that depend on third-party APIs, and closed-source modules aren't covered. | A drop-in replacement for Drupal 7, installed with Composer, Drush or a download, with no code changes. | HeroDevs says its patch SLA supports SOC 2, PCI DSS and HIPAA requirements. Priced on a quote. Support for end-of-life PHP is an add-on. |
| Tag1 D7ES ↗Certified by the Drupal Association | Security updates for Drupal 7 core and the contributed modules and themes its customers use. | A module that alerts you to new patches. Self-service plans apply them yourself; premium plans have Tag1 apply them to a non-production environment. | Published per-site monthly prices, monthly or annual, cancel any time. Patches work on any host. |
| Zend PHP LTS ↗by Perforce, also offered through HeroDevs | Security patches for end-of-life PHP 7.2, 7.3, 7.4, 8.0 and 8.1. Not PHP 5, 7.0 or 7.1. | Patched PHP builds delivered from a secure repository. | For Drupal 7 sites that can't move to a supported PHP version yet. Older PHP needs an upgrade first. |
Extended support covers patches, not the whole site. Someone still has to apply them, test them and look after your custom code, hosting and PHP. That's the part I take on.
It's a bridge, not a destination. Each year on Drupal 7 costs a subscription and makes the eventual migration no smaller, so pair it with a migration date.
I'm independent of these providers. You subscribe with them directly, and their terms decide what's covered and what it costs. Their compliance statements are their own claims, so check them against your auditor's requirements.
Drupal 12 needs PHP 8.5 and newer database versions. If your host can't provide them, that's the first thing to sort out, and it may mean a hosting move.
| Drupal 11 | Drupal 12 | |
|---|---|---|
| PHP | 8.3 or later | 8.5 or later |
| MySQL | 8.0 | 8.0 |
| MariaDB | 10.6 | 10.11 |
| PostgreSQL | 16 | 18 |
| SQLite | 3.45 | 3.45 |
| Web server | Apache or nginx | Apache 2.4.7 or nginx 1.1 minimum. IIS not supported |
| Composer | Composer 2 | Latest secure release recommended |
| Upgrade from | Drupal 10 | Drupal 11.3.0 or later only |
These core modules and themes are removed in Drupal 12. Most continue as contributed projects you can install while still on Drupal 11. Check each project page for its Drupal 12 status before you upgrade.
| Removed from core | What to do |
|---|---|
| Ban | Contributed project |
| Contact | Contributed project (when available) |
| Field Layout | Contributed project |
| History | Contributed project (when available) |
| Search | Contributed project |
| Settings Tray | Contributed project |
| Shortcut | Contributed project |
| Telephone | Contributed project |
| Toolbar | Contributed project |
| Text with Summary field | Contributed project |
| Claro and Olivero themes | Contributed projects |
| Migrate Drupal and Migrate Drupal UI | No replacement. Migrate Drupal 6 or 7 sites to Drupal 11 first |
Most of the work can happen on Drupal 11, before Drupal 12 is even released. That way the upgrade itself is small and low-risk.
Upgrade Status run across core, contributed and custom code, plus a check of your hosting's PHP and database versions. You get a written list of everything that has to change.
Core moved to the latest 11.x minor and contributed modules updated to their latest stable releases. That's what drupal.org recommends before the jump.
Removed modules and themes swapped for their contributed versions, or dropped where nothing uses them, while you're still on Drupal 11.
Custom modules and themes updated with Drupal Rector and static analysis, then tested. Most of this work is the same on 11 and 12.
PHP 8.5 and the required database versions set up on staging first, then on live. That might mean a host upgrade or a move.
Drupal 12 installed on staging, regression tested, then released with a backup and a rollback plan.
You can't. Drupal 12 only upgrades from Drupal 11.3.0 or later, so every Drupal 10 site has to go through Drupal 11. Drupal 12 is also scheduled for the same week Drupal 10 support ends, which leaves no room for delays. Move to Drupal 11 now. It's supported until at least 2028.
No. Drupal 11 stays supported at least until Drupal 13 is released, expected mid to late 2028. Stay on the latest Drupal 11 minor version, prepare as you go, and upgrade once the contributed modules you rely on support Drupal 12.
The site keeps working, but no more security fixes are released for it. New vulnerabilities in Drupal 10 won't be patched by the Drupal security team, and many security standards, contracts and insurers expect software to be supported. If you can't move in time, talk to me about a plan to keep the site protected in the meantime.
Yes, if you have to, but not without extended security support. HeroDevs and Tag1 both offer it and are certified by the Drupal Association. I can work with either one to apply the patches, look after your custom code and hosting, and plan the migration to Drupal 11.
They might. Drupal 12 missed its earlier June and August 2026 release windows, and the December release week is the scheduled one. The Drupal 10 end-of-life date of 9 December 2026 is fixed on the release schedule. I'll update this page when drupal.org changes its schedule.
It depends on how much custom code and how many contributed modules the site has, and on your hosting. The upgrade assessment answers that for your site, with a fixed price for the work.
Tell me which version you're on. I'll come back with what has to change, the route to a supported version and a fixed price. The first conversation is free and comes with no obligation.
All dates and requirements on this page were checked on drupal.org on 27 October 2026. Provider details were checked on each provider's website the same day.
This page is general information, not a guarantee of drupal.org's schedule. Always check the dates on drupal.org before you plan around them.