Build With KawalSenior Drupal developer
All posts

Drupal 7 is past end of life. What that actually means for your site

By Kawal Kohli · · 5 min read

I get some version of this question a lot: "Our Drupal 7 site still works fine. Do we really have to do anything?" It's a fair question. Nothing broke on the day support ended. The site loaded the next morning like it always did. So let's talk about what actually changed.

What "end of life" means here

Drupal 7 reached end of life on January 5, 2025. From that date, the Drupal security team stopped reviewing and fixing security issues in Drupal 7 core. Contributed modules for Drupal 7 lost that coverage too. If someone finds a hole in Drupal 7 today, there's no official fix coming.

That's the whole thing, really. Your site doesn't switch off. It just stops getting patched. And the code doesn't get any less interesting to the people who scan the web looking for old, known weaknesses.

The problems that show up over time

Security is the big one, but in my experience it isn't the first thing that bites. These usually come first:

  • Your host wants to move you to a newer PHP version, and old modules start throwing errors.
  • A module you rely on gets abandoned, and nobody is around to fix the bug you just found.
  • Your insurer, your IT team, or a client's security review asks what CMS version you're on.
  • Hiring gets harder. Fewer developers want to work on Drupal 7, and the ones who do know it's a short-term job.

None of these are emergencies on their own. But they stack up, and they tend to arrive at the worst time, like the week before a launch or right after a security scare.

Why you can't just "update" to Drupal 10 or 11

This is the part that surprises people. Going from Drupal 7 to Drupal 10 or 11 isn't an update like going from 10.2 to 10.3. Drupal 8 was a rebuild of the platform. It moved to Symfony, swapped the old theme layer for Twig, and changed how configuration is stored. Everything since then builds on that.

So a Drupal 7 site moves to a new build. Your content, users, files, and URLs get migrated across with Drupal's migration tools. Your theme gets rebuilt. Custom modules get rewritten or replaced. It's real work, and anyone who tells you it's a quick button press hasn't done one.

Your actual options

  1. Upgrade to Drupal 10 or 11. You keep your content and your URLs, and you're back on a supported platform for years.
  2. Pay for extended Drupal 7 support. Some companies sell this. It buys time, but you're still on old code, and you're paying every year to stand still.
  3. Move to a different CMS. Sometimes this is the right call, especially if the site has shrunk to a few pages. I'll tell you if I think that's your situation.
  4. Do nothing. It's an option. It's just the one where the risk and the eventual bill both keep growing.

What I'd do first

Before anyone quotes you a price, get a clear picture of what you have. How many custom modules? Which contributed modules, and do they have Drupal 10 or 11 versions? How much content, and how messy is it? That's what decides how big the job is.

If you want a second pair of eyes on it, book a call. Send me the URL and I can usually tell you what you're dealing with pretty quickly.

Want to know what your upgrade looks like? 30 minutes, and you'll know.

Book a discovery call