Services
All ServicesDrupal DevelopmentBusiness TransformationIndustries
Products
AI Smart Quality AssistantPMO AI PlatformAll Products
Portfolio Company
About UsCareersFAQ
Blog Schedule a Consultation
Drupal 12

Drupal 12 for Decision-Makers: Release Cycles, Support Windows and Upgrade Planning

Team planning a project around a table with laptops

If your organization runs on Drupal, major versions are a predictable part of the platform's life, not a surprise. Understanding the rhythm lets you budget calmly, avoid running unsupported software, and turn each upgrade into an opportunity rather than an emergency.

How Drupal's release cycle works

  • Minor releases (for example 11.1, 11.2) arrive roughly twice a year with new features and are backwards compatible.
  • Major releases (10, 11, 12) arrive roughly every two years and remove old, deprecated code.
  • Support windows: each major version receives security support for a defined period, which ends some time after the next major ships.

History shows the pattern: Drupal 9 reached end of life in November 2023, Drupal 7 in January 2025, and Drupal 10's security support is scheduled to end in late 2026. Always confirm current dates on drupal.org's release schedule page.

Why staying supported matters

Unsupported versions stop receiving security fixes. For public sector, healthcare and finance sites, that quickly becomes a compliance and reputational risk, not just a technical one.

What makes a Drupal 12 upgrade cheap or expensive

Lower costHigher cost
Already on the latest Drupal 11Still on Drupal 10 or older
Small, well-tested custom codeLarge custom modules without tests
Popular, maintained contrib modulesAbandoned or heavily patched modules
Modern hosting and PHP versionOutdated servers that need replacing too

The biggest lever is continuous maintenance. Teams that clean up deprecations every few months often upgrade in days rather than weeks.

A practical planning timeline

  1. Now: make sure you are on a supported version. If you are on Drupal 10, upgrade to Drupal 11 first.
  2. Before Drupal 12 is released: commission a readiness assessment covering code, contrib and hosting.
  3. After release: upgrade once the contrib modules you rely on support it, typically within a few months.
  4. Before Drupal 11 support ends: complete the move, with margin.

Budgeting

Treat upgrades as an operating cost, not a capital project. A useful model is a small, steady maintenance allocation (updates, security, deprecation cleanup) plus a modest upgrade budget each major cycle. That is far cheaper than a large emergency project when a version goes out of support.

Questions to ask your team or vendor

  • Which Drupal version are we on, and when does its security support end?
  • How many custom modules do we have, and do they have automated tests?
  • Which contributed modules are unmaintained or patched?
  • Is our hosting ready for the next PHP version?
  • Can we use this upgrade to retire features nobody uses?

Turn the upgrade into an opportunity

Each major version brings real improvements: better editorial tools, visual page building with Drupal Canvas, and an AI layer you can govern centrally. Plan the upgrade alongside one or two improvements users will notice, and it becomes an easy decision for leadership. Talk to us about a Drupal readiness assessment.

3P Technologies Engineering

Our team builds enterprise Drupal platforms, mobile apps and AI products from Amman, Jordan. About us

Keep reading

Related articles

All articles
Need an enterprise implementation?

Put our engineers on your project.

Our team specializes in Drupal 11/12 platforms, AI integration, performance engineering and multi-level data migrations.