Drupal migration and upgrades
Upgrade, or move off Drupal. Whichever fits, we've done both.
We've built on Drupal since 2009. That means we can tell you honestly whether your site needs an upgrade, a rebuild on a current version, or a different platform entirely, and then deliver whichever it is.
Which situation are you in?
Still on Drupal 7
Community support ended in January 2025. Security fixes now depend on paid extended support, and contributed modules are going unmaintained. This is a migration rather than an upgrade: the content model and custom code have to be rebuilt.
On Drupal 10
Support ends in December 2026. Moving to Drupal 11 is an upgrade rather than a rebuild, provided the custom code and contributed modules have been kept current. We audit the codebase and tell you which you have.
Moving off Drupal
Sometimes Drupal isn't the right fit any more. We move sites to enterprise WordPress or a headless CMS when the evidence supports it, and we say so when it doesn't.
The risks we manage
A migration rarely fails on the new build. It fails on the things that were never written down: a field nobody mapped, a URL nobody redirected, an integration nobody knew about until the morning after cutover.
Data mapping
Every content type, field and taxonomy mapped from old to new and signed off by its owner before build starts.
URLs and SEO
Each old URL redirected to its nearest new page, tested before launch and monitored in Search Console after.
Content freeze
Repeated test migrations of real data, so the final run is a rehearsal and the freeze stays short.
Integrations
Every connection inventoried in discovery and decided on: keep, rebuild or retire. Nothing found on launch day.
Accessibility
Rebuilt to WCAG 2.2 AA, including the content that migrates across, not only the new templates.
Support after launch
Parallel running, a rollback plan, then ongoing care through WebsiteSupport.io if you want it.
How a Drupal migration runs
Typically six to nine monthsWorkshops, codebase audit, module inventory, decision log.
Content model, field mapping, redirect plan, integrations.
Staged releases and repeated test migrations of real data.
Freeze, final migration, redirects, parallel running, rollback.
Training, documentation, support through WebsiteSupport.io.
Drupal migrations we've run
All case studies →
Chevening
Replaced a scholarship application system handling thousands of applications a year, with design partner Webb & Webb.
University of London Housing
Replaced the accommodation service's platform so students and landlords could find each other, and the team could run it themselves.
Questions we get asked
If yours isn't here, it's usually quicker to ask on the phone.
It depends on your content model, your integrations and who will run the site. Discovery answers it with evidence: we audit what you have and recommend the platform that fits, including staying on Drupal.
Not if the redirects are planned. Every old URL is mapped to its new page during architecture, tested before cutover and monitored in Search Console afterwards.
Usually days rather than weeks. We run repeated test migrations of your real data, so the final run is rehearsed and the freeze only covers that run and its checks.
Most can. We inventory every connection during discovery and agree which to keep, rebuild or retire before any build work starts.
Most of our migrations run six to nine months including discovery. Smaller, simpler sites are quicker, and we will tell you which yours is on the first call.
WebsiteSupport.io, our support company, if you want it. Or your own team, with the documentation and training we hand over.
Book a migration readiness review
A free 30-minute call with a technical lead, then a short written summary: upgrade, rebuild or move, roughly what it involves, and what to do first.
020 3608 2525