Drupal 7 End of Life: Your Upgrade Options in 2026

If you're still running Drupal 7, you're now 15 months past its official end of life date (January 5, 2025).

This isn't a future problem anymore. It's a current problem.

Your site is running software that no longer receives security updates. Every day you wait increases your risk of compromise, compliance violations, or your hosting provider forcing your hand.

Let me lay out your realistic options, what they cost, and how to decide what makes sense.

Why This Is Urgent

Drupal 7 served well for over a decade. It was released in 2011, and countless websites still run on it. But software doesn't stay secure forever.

After end of life, when security vulnerabilities are discovered - and they will be - there are no official patches. Your site becomes an increasingly attractive target for automated attacks.

The risks:

• Security breaches and data theft
• Defacement or malware injection
• Compliance violations (GDPR, accessibility requirements, industry regulations)
• Hosting providers refusing to host unsupported software
• Insurance implications if you're breached while running unsupported systems

You might think "my site isn't important enough to target," but most attacks are automated. They scan for known vulnerabilities and exploit them automatically. Your site doesn't need to be important - it just needs to be vulnerable.

Your Three Real Options

Option 1: Upgrade to Drupal 10 or 11

This means rebuilding your site on a modern Drupal platform. It's not a simple update—Drupal 7 and Drupal 10/11 are fundamentally different systems.

What's involved:

• Recreating your content types and structure in Drupal 10/11
• Migrating all your content (articles, pages, users, files)
• Rebuilding your theme for modern Drupal
• Rewriting or replacing custom modules
• Updating or replacing contributed modules
• Testing everything thoroughly

Realistic cost: £15,000 - £75,000 depending on site complexity

Realistic timeline: 3-6 months

This makes sense if:

• You want to stay with Drupal long-term
• Your site has complex content relationships or workflows
• You're happy with Drupal's approach to content management
• You have budget for a proper migration

This doesn't make sense if:

• Your site is simple and Drupal's complexity isn't necessary
• You're frustrated with Drupal and want something different
• You need a solution in the next few weeks, not months

Option 2: Migrate to a Different Platform

Maybe Drupal isn't the right fit anymore. Maybe your needs have changed, or you want something simpler.

Options include:

• WordPress - Simpler, larger ecosystem, easier to find developers. Good for content publishing without complex structure.
• A static site generator (Gatsby, Next.js, Hugo) - If your site is mostly static content, this can be faster and more secure.
• A hosted CMS (Contentful, Sanity, Webflow) - Less to manage, monthly fees instead of big upfront costs.

Realistic cost: £10,000 - £50,000 depending on platform and complexity

Realistic timeline: 2-4 months

This makes sense if:

• Your content needs are straightforward
• You're tired of Drupal's complexity
• You want lower ongoing maintenance costs
• You're redesigning anyway

This doesn't make sense if:

• You rely heavily on Drupal-specific functionality
• Your team knows Drupal well and doesn't want to learn something new
• You have complex editorial workflows that simpler systems can't handle

Option 3: Extended Support

Several vendors offer paid extended support for Drupal 7, providing security patches after official end of life.

The main providers are:

• Drupal 7 Extended Security Support from various providers
• Patches for critical security issues only

Realistic cost: £2,000 - £10,000 per year depending on site complexity and provider

This makes sense if:

• You need more time to plan a proper upgrade
• Your budget this year can't accommodate a full migration
• You're planning to replace the site entirely within 1-2 years

This doesn't make sense if:

• You're trying to avoid dealing with the problem indefinitely (extended support is temporary, not a long-term solution)
• Your site needs new features or improvements (extended support maintains, it doesn't enhance)

What Most People Should Do

For most organizations still on Drupal 7, here's my honest recommendation:

If you're still committed to Drupal and your site is genuinely complex, upgrade to Drupal 11. Yes, it's expensive. Yes, it takes time. But it's the right long-term solution, and you're already late.

If you're not sure Drupal still fits your needs, this is the perfect time to reconsider. Don't spend £40,000 upgrading to a platform you don't actually want to use.

If you need time to budget or plan, get on extended support immediately. It buys you time, but use that time actively planning your next move. Don't just stay on extended support forever.

What Each Option Actually Costs

Let me be specific about what drives costs in each scenario:

Drupal 7 to 11 Upgrade

Small site (basic content, minimal customization): £15,000 - £25,000

• Content migration
• Basic theme rebuild
• Testing and deployment

Medium site (custom modules, complex views, custom theme): £25,000 - £50,000

• Content migration with complex relationships
• Custom module rewriting
• Custom theme rebuild
• Integration updates
• Thorough testing

Large site (extensive customization, integrations, multiple content types): £50,000 - £100,000+

• Everything above, multiplied
• Multiple integrations with external systems
• Complex user roles and permissions
• Multi-site setup
• Extensive testing and training

Migration to WordPress

Generally 20-40% less than upgrading to Drupal 10/11 for sites of similar complexity, because WordPress is simpler and requires less custom development.

But remember: you're moving to a fundamentally different system. Make sure it actually fits your needs.

Extended Support

£2,000 - £10,000 per year, but this is annual cost, not a one-time fix. After 3-4 years, you've spent as much as an upgrade would have cost, and you still need to upgrade.

Timeline Reality Check

If you're starting now (April 2026):

• Extended support: Can be active within 1-2 weeks
• Simple site migration: 2-3 months
• Medium complexity upgrade: 3-4 months
• Complex site upgrade: 4-6 months

Add time for procurement, quotes, and planning. A project starting today might not launch until Q4 2026 or Q1 2027.

What Happens If You Do Nothing

Some organizations are tempted to just... not deal with it. Keep running Drupal 7 and hope for the best.

Here's what actually happens:

Short term (3-12 months):

• Probably nothing visible
• Increasing anxiety about security
• Possible warnings from hosting providers

Medium term (1-2 years):

• Security scans flag your site as vulnerable
• Compliance audits fail
• Hosting providers may refuse to continue hosting unsupported software
• If breached, much harder to recover

Long term (2+ years):

• PHP versions your site runs on become unsupported
• Hosting providers won't offer compatible environments
• You're forced into an emergency migration with no time to plan
• Emergency migrations cost 50-100% more and result in worse outcomes

Doing nothing is making a choice—just the worst possible one.

How to Decide

Ask yourself these questions:

1. Do we still need this website? 
   If the answer is no, decommission it properly. If yes, keep reading.
2. Does Drupal still fit our needs? 
   If you're happy with Drupal and it does what you need, upgrade to Drupal 11. If you're frustrated with it, this is your chance to switch.
3. What's our realistic budget this year? 
   If you can afford a proper upgrade, do it. If not, get on extended support while you budget for next year.
4. How complex is our site really? 
   Be honest. Many "complex" Drupal 7 sites are actually fairly simple. Get a proper assessment before assuming you need a £50,000 upgrade.
5. What happens if we're breached? 
   If the answer is "bad but not catastrophic," you have more flexibility. If it's "we go out of business," you need to treat this urgently.

Getting Started

Here's what to do this week:

1. Get an assessment 
   Find someone who knows Drupal 7 and modern Drupal. Have them review your site and give you realistic options.
2. Get quotes 
   From at least 2-3 providers. The quotes should include discovery work, not just guesses.
3. If you can't move forward immediately, get extended support 
   Don't run unsupported software while you plan. It's cheap insurance while you organize a proper solution.
4. Make a decision 
   Upgrade, migrate, or decommission. But decide actively, don't just drift.

A Final Word

I know this is frustrating. Your Drupal 7 site probably works fine. It seems unfair that you need to spend tens of thousands of pounds on something that already works.

But software has a lifecycle. Drupal 7 had an extraordinary run—13 years of active support. That's ancient in web terms.

The good news is that whether you upgrade to Drupal 11, migrate to WordPress, or choose another platform, you're not just maintaining the status quo—you're getting a faster, more secure, more capable website.

The investment isn't just about staying secure. It's about having a platform that will serve you for the next 5-10 years.

Just don't wait any longer. Every month you delay is a month of unnecessary risk.