Drupal Upgrades, Without the Drama

Drupal versions reach end of life, and when they do, security updates stop. Running an end-of-life CMS means every newly discovered vulnerability stays open on your site. For businesses that take payments, hold customer data, or care about their reputation, that's not a tenable long-term position.

What an upgrade actually involves

A modern Drupal upgrade is closer to a migration than a button press. The work typically includes:

• Auditing modules and themes for compatibility
• Migrating content and configuration to the new version
• Rebuilding or replacing custom code that no longer fits
• Refreshing the theme — often a good moment for a design update
• Testing, launch planning, and redirect preservation for SEO

If you would rather have us plan and carry out the upgrade, see our Drupal upgrade and migration service.

Why waiting gets more expensive

Each skipped version widens the gap between where you are and where you need to land, which increases migration effort. Meanwhile, developers familiar with very old versions become scarcer and pricier. The cheapest upgrade is almost always the one planned early.

The good news: an upgrade can be phased and scheduled around your business calendar, and the old site stays live until the new one is proven.

Where each Drupal version stands

Source checked October 18, 2026: Drupal 7 support ended January 5, 2025; Drupal 9 reached end of life November 1, 2023. See the official Drupal core release schedule.

Source checked October 18, 2026: The published end-of-life date for Drupal 10 is December 9, 2026; the schedule specifies no new Drupal 10 releases after that date. Drupal 10.6 is its final minor release. The same schedule lists the end of security support for 10.6.x and 11.3.x in the week of December 7, 2026, alongside the 11.5 release window recorded in that dated schedule. Support depends on the minor branch, not just the major version number.

Upgrade, migrate or move to another platform: how to decide

A Drupal 7 move requires migrating content and configuration to a new site; it is not an update applied to the existing installation. Themes need rebuilding, and contributed modules may need custom migration work. See Drupal’s migration overview.

For Drupal 8 and later, start with the supported major-version upgrade path and check module, theme and hosting compatibility. That is a different starting point from a Drupal 7 migration; see the major-version upgrade guide.

The platform decision starts with the work your site needs to do. Compare editorial workflow, required integrations, custom functionality and the budget for maintaining them. Keep Drupal when those needs fit; consider a different platform when a simpler arrangement meets them better. A version deadline alone does not decide the platform.

What to gather before you ask for quotes

• Your current Drupal version, module list and custom-code inventory
• Content types, approximate content volume and any multilingual requirements
• Integrations, scheduled tasks and business-critical journeys
• Hosting details, backups and deployment arrangements
• Who edits content and which parts of that workflow need to improve

If you would rather have us plan and carry out the upgrade, see our Drupal upgrade and migration service.