When the upgrade became a rebuild

Drupal 7 powered an enormous number of websites for well over a decade. If yours is one of them, you are now on a platform that reached the end of its official life in January 2025. No more security updates. No more fixes. And the path forward is not the gentle upgrade the version number suggests — it is, in practice, a rebuild.

Understanding why is the difference between making a calm, planned decision and being forced into a rushed one after something breaks.

Why Drupal 7 to 8 was never a simple step

Drupal 8 was a major rewrite of the core platform and its programming interfaces, rebuilt on a modern foundation and a different approach to how the software is structured. That was the right long-term decision for the project, but it meant there was no easy upgrade path from 7. Unlike the later jumps — 8 to 9 to 10 — which are comparatively routine, moving off 7 means rebuilding the site on a current version and migrating the content across.

Your custom modules, your theme, and the integrations built for Drupal 7 do not carry over. They are rebuilt for the new architecture. The content can be migrated with tooling, but the site around it is, for practical purposes, a new build.

The scale of the stranding

This is not a niche problem. Drupal 7’s end of life was extended more than once, partly because so many sites were still running it — hundreds of thousands were still live well into the platform’s final years. The reason is exactly the one above: the upgrade was a rebuild, so organisations deferred it. Deferral is rational right up until the support runs out, at which point the deferred cost is joined by a security liability.

A Drupal 7 site today is functional and unsupported at the same time. It will keep serving pages. It will also keep accumulating unpatched vulnerabilities, on a platform whose underlying components are themselves out of support. For any site that handles personal data or sits at the centre of how an organisation operates, that is an exposure that grows quietly until it does not.

The decision this forces

Because moving off Drupal 7 is a rebuild, it forces a question worth answering properly rather than by reflex: is the right destination a current version of Drupal, or is this the moment to reconsider the platform altogether? For a large, content-heavy site with deep Drupal-specific functionality, rebuilding on current Drupal is often the sensible path. For a site that grew complex by accident, the forced rebuild is a chance to simplify, or to move to a platform that fits the organisation better today.

What you should not do is recreate the old site verbatim on a new version. The rebuild is the one moment you get to leave behind the modules nobody uses and the structure nobody understands. Spending the budget to faithfully reproduce a decade of accumulated decisions wastes the opportunity the deadline handed you.

What to do now

The first step is an assessment, not a build. What does the site actually do, which functionality is genuinely in use, what content needs to migrate, and where is the business going. That picture determines whether the answer is current Drupal or a different platform, and it sizes the work honestly before anyone commits a budget.

If you are still on Drupal 7, you are running an unsupported platform and the rebuild is no longer optional — only its timing and shape are. We will establish where you stand and the cleanest way forward.

Start a Conversation