October 6, 2026 · By Drupal Company
Drupal 7 has reached end of life. That means the Drupal community no longer ships security fixes for core or for most contributed modules. A site that keeps running on it is accumulating risk, and it gets harder over time to find hosting that supports the PHP versions it needs.
There is no in-place upgrade
Drupal 7 to Drupal 10 or 11 is a migration to a new codebase. Content, users, files and configuration are moved across with the Migrate API, and custom modules and themes are rebuilt for current APIs.
Start with an inventory
Before choosing an approach, list:
- Content types, fields and how much content each holds
- Contributed modules and whether they have Drupal 10 or 11 versions
- Custom modules and themes and what they actually do
- Integrations: SSO, CRM, search, payment, feeds
- Editors, roles and workflows that must survive
Three realistic options
- Migrate to Drupal 10 or 11 with a modernised content model. Best when the site is still doing its job.
- Rebuild and migrate selectively. Best when the content model or design has aged badly and only part of the content is worth keeping.
- Consolidate or retire. Many organisations find that several small Drupal 7 sites can become one, or that parts are no longer needed.
Do not forget redirects
Map old URLs to new ones before launch and test the map. It protects search traffic and saves you from a pile of 404s.
If you want a second opinion on which path fits, we can run a short audit of the site and give you a scoped plan.
Drupal 7 Migration Security