Drupal 12 Is Coming: What Business Leaders Should Know Before December 2026

Modern Drupal has a predictable release cycle. Major versions are planned every two years, minor versions arrive every six months, and security and bug fix releases follow a regular pattern. That predictability is useful for business planning. It means budgets, internal resourcing, testing windows, hosting checks and agency support can be organised ahead of time.

However, a new major version becoming available does not automatically mean every organisation should upgrade immediately. This is especially true for larger, more complex Drupal 11 sites.

Drupal websites usually rely on a mix of Drupal core, contributed modules, custom code, integrations, hosting configuration and editorial workflows. Drupal core may be ready on release day, but every contributed module your site depends on may not be fully production ready for Drupal 12 at the same time. Some modules may be ready quickly. Others may take weeks or months. For complex sites, it is possible that the sensible upgrade window could be many months after Drupal 12 is officially released, and in some cases close to a year.

That is not a failure of Drupal. It is a normal reality of responsible open source platform management.

A good Drupal 12 strategy should therefore start with an audit, not an upgrade button. Suitably skilled Drupal developers can review your Drupal 11 site and identify which modules, themes, integrations and custom code are important to your business. They can then assess whether those medium and high importance components are ready for Drupal 12, whether patches are available, whether replacements are needed, and whether any custom code uses older APIs that need attention.

This gives business leaders a much clearer decision. Instead of asking “Can we upgrade today?”, the better question is “Are the parts of our site that matter ready for Drupal 12 in production?”

For small brochure sites, the answer may become yes quite quickly. For larger sites with ecommerce, membership, CRM, marketing automation, complex content workflows, search, multilingual content or custom integrations, the answer may take longer. In those cases, waiting can be the lower risk business decision.

That does not mean doing nothing. The best preparation for Drupal 12 is a well maintained Drupal 11 site. Keep Drupal core current. Keep contributed modules updated. Remove unused modules. Review custom code. Check hosting requirements. Confirm that your development, staging and production processes are reliable. The cleaner your Drupal 11 site is, the easier your Drupal 12 upgrade is likely to be.

This is also the time to review technical debt. Major version planning often reveals old assumptions: modules that are no longer needed, integrations that no one owns, content types that have drifted from their original purpose, and custom code that was written years ago for business requirements that may no longer exist. Drupal 12 planning can become a useful governance exercise, not just a software upgrade.

There is another important deadline in the background. Drupal.org currently lists Drupal 10 end of life as 9 December 2026. Organisations still on Drupal 10 should treat that as a business risk date. Once a Drupal version reaches end of life, it no longer receives normal project support. That can create security, compliance and operational concerns. For those organisations, the priority should usually be getting safely to Drupal 11 first, then planning Drupal 12 from a stronger position.

The AI question is also becoming harder to ignore. WordPress 7.0 was released in May 2026, with official WordPress material highlighting AI infrastructure such as the WP AI Client and Connectors API. It is reasonable for business leaders to ask whether Drupal is also preparing for a more AI-assisted future.

The official answer is yes, although the details should be described carefully. Drupal.org has announced a formal Drupal AI Initiative, describing it as a coordinated effort to support responsible AI innovation across the Drupal ecosystem. Drupal.org also states that there are already hundreds of AI-related Drupal modules and integrations with major AI providers. Drupal CMS documentation includes AI tools, and the Drupal AI ecosystem includes work on AI agents that can help with tasks such as site building, content modelling and configuration.

What we should not say yet is that Drupal 12 will definitely include a particular AI feature in core, unless Drupal.org confirms it in official Drupal 12 release documentation. The safer and more accurate message is that Drupal 12 is expected to arrive in a Drupal ecosystem that is already investing heavily in AI readiness, AI-assisted site building and agent-style tools.

For business owners, that means Drupal 12 planning should include AI governance. Who is allowed to use AI tools? Can AI-generated content be published directly, or must it be reviewed? Where are API keys stored? Which providers are approved? What data can be sent to external AI services? These are management questions as much as technical ones.