Drupal 7 End of Life: Your Migration Options in 2025

Updated (first posted )

Drupal 7 officially reached end of life on 5 January 2025, yet hundreds of thousands of websites are still running on the platform. If yours is one of them, you're now operating without security updates from the Drupal community. Here's what that means and what your realistic options are in 2025.

What Drupal 7 End of Life Actually Means

End of life means the Drupal Security Team no longer provides security advisories or patches for Drupal 7. This doesn't mean your site will immediately stop working. It means:

  • No security patches. New vulnerabilities won't be fixed by the community. Your site becomes increasingly exposed over time.
  • No module updates. Contributed modules (Views, Webform, Commerce, etc.) are no longer maintained for D7.
  • Hosting pressure. Many managed hosting providers are phasing out Drupal 7 support or adding surcharges.
  • Compliance risk. For sites handling personal data, running unsupported software may put you offside with GDPR, PCI-DSS, or industry-specific regulations.

Three Realistic Options in 2025

The right path depends on your organisation's technical resources, budget, and long-term platform needs. However, all three options require action. Staying put is not a strategy.

Option 1: Extended Support (Short-Term Fix)

Several vendors offer paid extended support for Drupal 7, providing security patches beyond the official EOL date. This buys you time but doesn't solve the underlying problem.

Extended support makes sense if you need 6-12 months to plan a proper migration, your site is low-risk (no e-commerce, no sensitive data), and budget constraints prevent moving immediately. It doesn't make sense if you're running Drupal Commerce (increasingly fragile on D7), handling sensitive user data, or you've already been on extended support for a year and the window is closing.

Option 2: Upgrade to Drupal 10/11

Drupal 10 and 11 are the current supported versions. However, upgrading from Drupal 7 is not a simple version bump. It's effectively a complete rebuild. Drupal 7 and Drupal 10 have fundamentally different architectures, templating systems, and content management approaches. This is a critical point that catches many organisations off guard.

The work involved is substantial: a complete theme rebuild (PHPTemplate to Twig), module replacements (many D7 modules have no D10 equivalent), content migration using Drupal's Migrate API, and a custom code rewrite for any bespoke functionality.

When this makes sense:

  • Your team has strong Drupal expertise and wants to stay on the platform
  • You have Drupal-specific functionality that's hard to replicate elsewhere
  • Your organisation has invested heavily in Drupal training and workflows

Option 3: Migrate to WordPress

For many organisations, Drupal 7's end of life is the catalyst to move to WordPress. This is where the "it's a rebuild either way" reality becomes an opportunity. Since a D7-to-D10 upgrade requires complete theme reconstruction, module replacement, and content migration (the same work involved in moving to WordPress), it's worth evaluating whether a different platform better fits your needs going forward.

WordPress powers approximately 43% of all websites globally. That scale translates into practical advantages:

Why organisations choose WordPress:

  • Lower ongoing costs. Industry comparisons consistently show WordPress annual maintenance costs running lower than equivalent Drupal setups, primarily due to a larger developer talent pool and more affordable hosting options.
  • Easier content management. WordPress's block editor is more intuitive for non-technical content teams. Your marketing people can publish without developer involvement.
  • E-commerce ready. WooCommerce is mature and well-supported, with a vast plugin ecosystem.
  • Faster time to market. WordPress development is typically faster than equivalent Drupal work.

That said, WordPress isn't a drop-in replacement. Several areas need careful handling:

What you need to consider:

  • Custom content types. Drupal's content type system is more flexible out of the box. WordPress handles this through plugins (ACF, Pods) or custom post types, but it requires planning.
  • Complex permissions. If your site uses Drupal's granular permission system extensively, this needs careful mapping to WordPress roles and capabilities.
  • E-commerce data. Migrating from Drupal Commerce to WooCommerce requires specialist handling to preserve products, orders, customer accounts, and reviews.
  • SEO preservation. URL structures differ between platforms. Proper 301 redirect mapping is essential to protect your search rankings.

What a Professional Migration Looks Like

Regardless of which platform you move to, a complex migration follows a predictable process. For most projects, this typically involves six stages:

  1. Content audit: inventory every content type, field, taxonomy, and relationship
  2. Architecture mapping: design the equivalent structure on the new platform
  3. Custom scripting: write migration scripts tailored to your content structure
  4. Iterative testing: run 5-20 test migrations to catch edge cases
  5. SEO mapping: map old URLs to new, set up 301 redirects
  6. Zero-downtime launch: staged migration with DNS cutover for business-critical sites

This process typically takes 4-12 weeks depending on complexity. Automated migration tools can handle basic content, but the specifics of a real Drupal 7 site (custom content types, complex field relationships, bespoke functionality) all require custom scripting.

The Cost of Waiting

Every month on unsupported Drupal 7 increases your risk. New vulnerabilities won't be patched, and as browsers, PHP versions, and third-party services evolve, compatibility issues will compound.

I've worked on D7 sites where a single contributed module stored data across 15 custom database tables, structures that no automated tool even recognises. The longer those sites run without maintenance, the harder they are to unpick. Meanwhile, managed hosting providers are phasing out Drupal 7 support or adding surcharges for legacy environments.

The migration itself doesn't get cheaper by waiting either. Developer availability tightens as the remaining Drupal 7 talent pool moves on, and the growing technical debt (outdated modules, unpatched core, ageing server dependencies) makes the eventual migration more complex and more expensive.

If you're still on Drupal 7 in 2025, the time to act is now. Whether you choose Drupal 10 or WordPress, a well-planned migration protects your content, your SEO rankings, and your business.

Related reading:

Need Help With Your Drupal 7 Migration?

I specialise in complex Drupal to WordPress migrations, including e-commerce, custom content types, and business-critical sites that need zero-downtime launches. Get a free, no-obligation consultation to discuss your options.

Get a Free Quote