Skip to content
Call 03333 20 97 97
bristol.digital: empowering ideas
Legacy PHP rescue and modernisation
On this page

Drupal 7 end of life

Drupal 7 has been unsupported since January 2025. Here's what to do about it.

Drupal 7 reached end of life on 5 January 2025. There are no more security fixes from the Drupal community. If your site still runs on it, you're relying on luck, a paid extended-support arrangement, or both.

This isn't a one-click upgrade, but it's a well-trodden path. I'll help you work out the right route, and carry it out without losing the content and functionality your site depends on.

Book a free conversationLegacy System Assessment, from £2,500


Where things stand

Checked October 2026. Confirm at drupal.org.

Drupal version Status
7 End of life since 5 January 2025
8 End of life since November 2021
9 End of life since November 2023
10 Reaches end of life in December 2026
11 Current, and the version to move to

The key point: don't migrate from Drupal 7 to Drupal 10 and consider yourself finished. Drupal 10 itself ends in December 2026, so a new migration should normally target Drupal 11, unless a module you depend on isn't ready for it yet. Updates between recent Drupal versions are much easier than the jump from Drupal 7.


Why Drupal 7 is a bigger job than a normal upgrade

There's no in-place upgrade from Drupal 7 to a modern version. Modern Drupal is a different system. A Drupal 7 move is a migration:

  • Content (pages, articles, taxonomy, users, files and media) is moved across using migration tools
  • Modules are replaced with their modern equivalents, or rebuilt, because many Drupal 7 modules no longer exist
  • Custom modules are rewritten for the modern Drupal architecture
  • The theme is rebuilt, because the theme system changed completely
  • Configuration, views, permissions and workflows are recreated

Done properly, it's also a chance to tidy years of accumulated content and clutter before moving it.


Your options

Option What it involves Best when Watch out for
Migrate to Drupal 11 Build a new Drupal site and migrate content and functionality The site is valuable and you want to stay on Drupal A real project, but a supported destination
Paid extended support for Drupal 7 Certified vendors continue to provide security fixes for a fee You need time, and the site has a clear end date Costs money every month. It's a bridge, not a fix. Check what exactly is covered
Move to another platform Migrate content to a different CMS or framework The site no longer needs Drupal-level flexibility Re-platforming still costs. Content and URLs must be carried over carefully
Simplify or retire Archive content, or reduce to a simple site Much of the old content is no longer used Plan redirects, so you don't lose search rankings
Do nothing Stay on Drupal 7 Never recommended for a site holding personal data or taking payments Known vulnerabilities, hosting problems and failed audits

Which is right depends on what the site does and what it needs next. Rewrite vs refactor vs upgrade


How I approach it

1. Assess

I inventory the content, content types, modules (contributed and custom), theme, users, integrations and server. I find out which modules have modern replacements and which functionality has to be rebuilt. AI-assisted analysis makes this far faster, and I check it against the running site. How I use AI

2. Decide the shape of the new site

What to keep, what to drop, and what to rebuild. Cleaning up before migrating is cheaper than migrating clutter.

3. Build and migrate

A new, supported Drupal site is built alongside the old one. Content is migrated in repeatable runs, so it can be re-checked and re-run.

4. Test, and protect your search position

You check the result on a copy. URLs, redirects and key pages are mapped so you don't lose rankings or break links.

5. Switch over, with a way back

A planned cutover and a rollback ready, then monitoring. Hosting migration

6. Keep it current

Modern Drupal is built for regular updates. A small routine of updates is far cheaper than another catch-up. Ongoing care


The risk of staying on Drupal 7


What it costs

Fixed price, after assessment. A Drupal 7 migration varies enormously with the size and complexity of the site, so I won't quote without looking.

  1. Free conversation
  2. Legacy System Assessment, from £2,500, with the options costed
  3. Fixed-price quote for the route you choose

What affects cost: amount and quality of content, number of content types, custom and unreplaceable modules, theme complexity, integrations and number of users. Direct day rate is £950; urgent work from £1,300 per day. Pricing


For agencies

A client still on Drupal 7 and a team that's moved on? I can take it white-label, or direct with you as referrer. Agency terms


Frequently asked questions

When did Drupal 7 reach end of life?

5 January 2025.

Can I upgrade Drupal 7 to Drupal 10 or 11 directly?

Not in place. It's a migration to a new site, with content moved across and functionality rebuilt.

Should I go to Drupal 10 or 11?

Usually 11. Drupal 10 reaches end of life in December 2026. If a module you rely on isn't ready for 11 yet, we can discuss a staged route.

Is extended support worth it?

As a short bridge, sometimes. It costs money every month and doesn't fix the underlying problem. Ask exactly what's covered and for how long.

Will we lose our content and search rankings?

Not if it's planned. Content is migrated, and URLs are mapped and redirected. I check this before the switch.

Do you only work with Drupal?

No. I work with custom PHP and other frameworks. PHP upgrades


Tell me what you've inherited.

Tell me what your Drupal 7 site does, how big it is, and any deadline. I'll tell you honestly what the options are.

Book a free conversationLegacy System Assessment, from £2,500

Call Book a free conversation