Drupal 7 to 11 migration
Drupal 7 to Drupal 11, for one fixed price
Drupal 7 reached end of life in January 2025. No more security fixes, no more patches — every vulnerability found from now on stays open on your site.
If you're reading this in 2026 you've been running unsupported software for a while. You already know this, probably. The reason you haven't moved yet is the same reason most organisations haven't: Drupal 7 to Drupal 11 isn't an upgrade, it's a migration.
The architecture changed completely at Drupal 8, so there's no button to press — the site has to be rebuilt on the new platform and the content moved across. Agencies quote big numbers for it, and it's hard to know what you'd actually get.
What a migration includes
Everything moves.
Content, users, files, taxonomies — migrated into Drupal 11 and checked against the original
Your URLs survive.
Every address that worked before works after, so you don't lose your Google rankings or break a decade of inbound links.
The theme is rebuilt properly.
Drupal 11 uses Twig templating; your design is recreated on it (or refreshed, if you'd rather — the effort is similar).
Modules are mapped, not guessed.
Every Drupal 7 module on your site gets an answer: replaced by core, replaced by a maintained module, rebuilt as custom code, or genuinely no longer needed. You see the list before we start.
One price, agreed up front.
From £3,500 for a typical small-organisation site. If it turns out to be harder than scoped, that's my problem, not your invoice.
An unsupported CMS isn't a theoretical risk
Drupal 7's remaining vulnerabilities are public knowledge, automated scanners look for D7 sites specifically, and if you hold supporter, parent or member data, an unpatched CMS is an awkward conversation waiting to happen — with your insurers, your trustees, or the ICO. The migration doesn't get cheaper by waiting, either. It gets more expensive every year as the gap widens.
Where to start
Run the free scan. It'll tell you exactly what version you're on and how exposed you are, in about ten seconds. If you want the detail, request the written report — it's free, it's specific to your site, and it comes with a fixed-price estimate so you know what you're dealing with.
Quick answers
Most small-organisation sites take 2 -3 weeks from kickoff. You get a fixed timeline with the fixed price.
No. The new site is built alongside the old one and switched over when everything checks out. The old site keeps running until the moment it's replaced.
It's the most common situation we see. As long as the site is running, everything needed for the migration can be recovered from it.
Yes — that's exactly what the exposure check is for. Custom code gets reviewed as part of scoping, and the quote reflects it. No surprises after signing.
Find out what your migration involves
Drupal 7 to 11 is a bigger move than a version bump — but the first step is small. Run the free scan and you'll see in about ten seconds what you're on, what it exposes you to, and what a move to Drupal 11 would put right. No signup, no obligation.