← All Drupal end-of-life dates
Is staying on an end-of-life version actually risky?
Yes — staying on end-of-life versions is a real risk: security vulnerabilities, no patches, degraded performance, and an increasingly painful developer experience. That said, the actual exposure level varies a lot depending on how well the site was built.
We've seen legacy Drupal 7 sites that were clean, well-documented, and minimal on plugins — honestly lower risk than some "modern" sites drowning in third-party integrations and spaghetti code. So the honest answer is: it depends — but the direction of travel is clear. Unpatched software only gets riskier with time, and eventually the practical realities (old PHP, abandoned modules, compliance) catch up with even a well-built legacy site.
Drupal 7 → 11: what the upgrade really involves
There's no clean upgrade path from Drupal 7 to Drupal 11 — it's essentially a rebuild. Drupal changed architecture after version 7, so you're building a new site and migrating content, not running an in-place update. Realistic timelines:
Straightforward small site
A relatively simple site with standard content and few custom modules.
Complex site
A large university site with custom modules, integrations, and lots of content. Plan conservatively — discovery always surfaces more than expected.
Upgrade vs. redesign: worth pausing to ask
It's almost always worth pausing to ask this question. If a site is so far behind that it's still on Drupal 7, it's likely the UX, sitemap, and feature set are also dated. Starting fresh is often more efficient than a like-for-like migration — and it gives the organization a chance to rethink everything properly: information architecture, content strategy, accessibility, and the features people actually use today.
Will Drupal 11 actually be faster?
Generally, yes — Drupal 11 on modern hosting will usually be faster. But "Drupal upgrade = fast site" isn't a guarantee on its own. Hosting, caching, image handling, and theme quality matter just as much as the Drupal version. A clean upgrade paired with good infrastructure and a well-built theme is where the real performance gains come from.
And if the redesign question has you wondering whether to stay on Drupal at all, that's a fair thing to weigh — see reevaluating Drupal and considering WordPress.
Not sure whether to upgrade, rebuild, or redesign?
Tell us what you're running as well as any additional tech stack details. From there we can figure out together if an upgrade makes the most sense — or if there's another option best suited for you and your organization.
Tell us what you need
Share your site and any additional tech stack details. We'll detect your Drupal version, flag any end-of-life risk, and figure out together whether an upgrade makes the most sense — or if another option is better suited for you and your organization. No obligation.
We'll email you back and may follow up if we spot significant issues worth fixing. No spam.
Drupal 7 to 11: frequently asked questions
Is it risky to stay on an end-of-life version of Drupal?
Yes — unpatched security holes, no updates, degraded performance, and a harder dev experience. But exposure depends on how well the site was built; a clean, minimal Drupal 7 site can be lower risk than a messy modern one. The trend, though, is that risk only grows over time.
How long does a Drupal 7 to 11 upgrade take?
It's a rebuild, not an update. Roughly 3–4 months for a straightforward small site; 6–12 months conservatively for a complex university site with custom modules and lots of content.
Should I upgrade or redesign?
Usually worth asking. If you're that far behind, the UX and feature set are likely dated too — starting fresh is often more efficient and a chance to rethink things properly.
Will upgrading make my site faster?
Usually, on modern hosting — but it's not automatic. Hosting, caching, image handling, and theme quality matter just as much as the Drupal version.