Quick answer: Drupal 10 reaches end of life on 9 December. After that date, the Drupal Security Team stops releasing security fixes for it. If your site runs Drupal 10, the right move is to upgrade to Drupal 11, not wait for Drupal 12. The Drupal 10 to 11 jump is one of the smaller major upgrades in Drupal’s history, but it still needs planning, testing and a team that knows your modules. Most businesses should start an audit now.
If your organisation relies on a Drupal website, this deadline matters. After 9 December, any new vulnerability in Drupal 10 stays unpatched, which puts your data, your users and your reputation at risk. This guide explains what end of life means, what to do about it and how a Drupal development company can help you finish in time.
What “End of Life” Actually Means
End of life doesn’t mean your site stops working on 9 December. It means the community stops supporting that version:
- No more security advisories or patches for Drupal 10 core
- No new core releases
- Contributed modules gradually drop Drupal 10 support as maintainers move on
- Hosting and platform providers may stop guaranteeing compatibility
An unsupported CMS is a common target for attackers, because known vulnerabilities stay open. It can also be hard to justify under security frameworks such as the Essential Eight, which expects applications to be patched.
Which Sites Are Affected?
| Your version | Status |
|---|---|
|
Drupal 7, 8 or 9 |
Already unsupported. You should upgrade as soon as possible |
|
Drupal 10 |
Support ends on 9 December |
|
Drupal 11 |
Currently supported, and the recommended target |
If you’re on an older version, you can’t jump straight to the newest one. Drupal upgrades move through each major version in order, or use a migration approach that rebuilds the site on Drupal 11. Your Drupal development company can advise which fits your site. See our guide to Drupal migration and upgrades for more detail.
Why Upgrade to Drupal 11, Not Drupal 12?
Drupal 12 is expected around the same time Drupal 10 reaches end of life, which leads many people to ask whether they should wait. In most cases, you shouldn’t.
- You can’t skip a major version. Drupal’s upgrade policy requires moving through each major release, so Drupal 10 goes to 11 first.
- Drupal 11 has been stable for a while. It’s mature, widely supported and the practical destination for most sites.
- The 10 to 11 jump is small. Many of the more disruptive changes were deferred, so code-level changes are limited for most sites.
- Moving to 12 later gets easier. Once you’re on Drupal 11, the step to Drupal 12 looks much more like a routine update than a migration.
Waiting for Drupal 12 usually just leaves you unsupported for longer.
How the Drupal 10 to 11 Upgrade Works
A well-run upgrade follows a clear process:
1. Audit your site
Review your Drupal core version, contributed modules, custom modules, custom themes and integrations. Tools like the Upgrade Status module help identify what’s compatible with Drupal 11.
2. Check your hosting and platform
Drupal 11 requires newer versions of PHP and other server software. Confirm your hosting meets the requirements on drupal.org, and plan any hosting changes.
3. Update modules and themes
Update contributed modules to Drupal 11-compatible versions. Replace any that are abandoned or no longer maintained.
4. Fix custom code
Deprecated code in custom modules and themes needs updating. This is often where most of the development effort sits.
5. Test on a staging copy
Run the upgrade on a copy of your site first. Test content, forms, search, user roles, integrations, performance and accessibility.
6. Go live and monitor
Schedule the cutover for a quiet period, keep a rollback plan and monitor the site closely after launch.
Common Blockers That Delay Upgrades
Three problems cause most delays:
- Modules that aren’t Drupal 11 ready: the module may need a replacement or a custom patch.
- Heavy custom code: older custom modules and themes often use deprecated APIs.
- Hosting requirements: an old server environment may need upgrading before Drupal 11 can run.
Finding these early is the main reason to start with an audit.
How Much Does a Drupal 10 to 11 Upgrade Cost?
Cost depends on your site’s size and how much custom work it contains. As a general guide:
| Site type | Typical cost (AUD) | Typical timeline |
|---|---|---|
|
Small site, mostly standard modules |
$3,000 – $15,000 |
2 – 6 weeks |
|
Mid-size site with custom modules or integrations |
$15,000 – $50,000 |
1 – 3 months |
|
Large or complex site |
$50,000+ |
3+ months |
|
Upgrade audit and assessment |
$1,500 – $5,000 |
1 – 2 weeks |
Sites on Drupal 7, 8 or 9 usually cost more, because they need a larger migration rather than a straightforward update. For general pricing across Drupal projects, see our guide to Drupal development in Australia.
DIY vs Hiring a Drupal Development Company
You may be able to handle a simple upgrade in-house if:
- your site uses mostly standard, well-maintained modules
- you have little or no custom code
- someone on your team is comfortable with Composer and Drupal updates
You should consider a Drupal development company if:
- you have custom modules, a custom theme or complex integrations
- you rely on modules that haven’t been updated
- you’re on Drupal 7, 8 or 9
- the site is business-critical, handles personal data or serves a large audience
you’re short of time before the deadline
What to Ask a Drupal Development Company Before You Hire
- Have you completed Drupal 10 to 11 upgrades? Can I see examples?
- How will you audit my site, and will I get a written report?
- How do you handle modules that aren’t Drupal 11 ready?
- Will you test on a staging copy before touching the live site?
- What does the quote include, and what’s excluded?
- How long will it take, and can you finish before 9 December?
- What support do you provide after launch?
- Who owns the code, and do I keep full access to my site and hosting?
For a fuller checklist, read our guide to choosing the right Drupal development partner.
What If You Can’t Finish Before the Deadline?
If you can’t complete the upgrade in time, you still have options:
- Start the audit now. Knowing the scope lets you plan realistically.
- Add protective measures. A web application firewall, tight access controls and active monitoring can reduce risk in the short term. These aren’t a substitute for upgrading.
- Prioritise. Upgrade your highest-risk or most visible sites first.
- Consider extended support options. Some vendors offer paid support for end-of-life versions. Ask your hosting provider or Drupal development company what’s available, and treat it as a temporary bridge, not a permanent plan.
Don’t leave it until the last week. Developers get busy as the deadline approaches, and testing takes time.
Planning Beyond the Upgrade
An upgrade is a good time to look at what else your site needs. Drupal 11 and the newer Drupal CMS releases bring a modernised editing experience and built-in AI features. Our article on Drupal CMS 2.0, Canvas and built-in AI explains what that means for Australian businesses. Ongoing Drupal maintenance and support also helps you avoid being caught by the next deadline.
Frequently Asked Questions
When does Drupal 10 reach end of life?
On 9 December. After that date, Drupal 10 no longer receives security updates from the Drupal Security Team.
Will my Drupal 10 site stop working after end of life?
No. It will keep running, but it won’t receive security fixes, which makes it increasingly risky.
Should I upgrade to Drupal 11 or wait for Drupal 12?
Upgrade to Drupal 11. You can’t skip a major version, and moving from 11 to 12 later is much easier.
How long does a Drupal 10 to 11 upgrade take?
A simple site can take a few weeks. Sites with custom code or integrations may take a few months. An audit gives the most accurate estimate.
How much does it cost to upgrade from Drupal 10 to 11?
Small sites may start from a few thousand dollars, while complex sites cost much more. Custom code and module compatibility are the biggest factors.
I’m still on Drupal 7, 8 or 9. What should I do?
Those versions are already unsupported. You should plan an upgrade or migration to Drupal 11 soon, and a Drupal development company can advise which approach fits your site.
Can I do the upgrade myself?
Possibly, if your site is simple and uses standard modules. Business-critical sites and those with custom code are usually safer in the hands of an experienced team.
What happens to my modules?
Each contributed module needs a Drupal 11-compatible version. If one isn’t available, it may need replacing, patching or rebuilding.
Talk to a Drupal Development Company About Your Upgrade
Drupal Professionals is a Drupal development company helping Australian organisations upgrade, migrate, secure and maintain their Drupal sites. We can audit your site, give you a clear scope and cost, and manage the upgrade from start to finish.
Call: 1300 72 50 90
Email: info@drupalprofessionals.com.au
Not sure where your site stands? Request a free Drupal upgrade assessment and we’ll tell you what’s involved before the deadline.