Drupal 12 Is Coming: What It Means for Associations

Drupal 12 is targeting an August 2026 release, with a fallback window of December 2026. For associations running Drupal, this release sits at the intersection of two pressures: the platform is making significant architectural changes that improve the long-term developer and editor experience, and Drupal 10 reaches end of life on December 9, 2026, which means organizations on older versions are running out of runway.

Whether your association is on Drupal 7 wondering what to do next, on Drupal 10 planning your upgrade to 11, or already on Drupal 11 and thinking ahead, here is what Drupal 12 brings to the table and what it means for your organization.

What Is Actually Changing in Drupal 12

Drupal 12 is not a ground-up rewrite. It follows the same continuous upgrade model that Drupal established starting with Drupal 9, where major versions are incremental steps rather than the painful rebuild-from-scratch migrations that plagued earlier Drupal generations. That said, Drupal 12 introduces meaningful changes under the hood and in the editorial experience.

Symfony 8 Foundation. Drupal 12 upgrades its underlying framework to Symfony 8. Symfony is the PHP framework that powers Drupal is core architecture, handling routing, dependency injection, event dispatching, and other foundational operations. Moving to Symfony 8 means modern PHP practices, better performance, and long-term support from the Symfony community. For site owners, this is invisible. For developers, it means cleaner code and better tooling.

New Admin Theme: Gin Replaces Claro. The admin interface is getting a visual overhaul. Gin, which has been one of the most popular contributed admin themes in the Drupal ecosystem, is being merged into core to replace the current Claro admin theme. Gin provides a more modern, polished editorial interface with better typography, improved form layouts, and a more intuitive navigation structure. For association content editors who spend hours in the Drupal admin, this is a meaningful quality-of-life improvement.

Navigation Module Replaces Toolbar. The legacy Toolbar module that has served as Drupal is primary admin navigation for over a decade is being replaced by the new Navigation module. The Navigation module provides a sidebar-based navigation experience that is more flexible, more customizable, and more consistent with modern web application interfaces. Content editors can pin frequently used items, collapse sections they rarely use, and navigate the admin more efficiently.

Experience Builder (Layout Builder Evolution). Layout Builder, Drupal is visual page building tool, is being rebranded and evolved as the "Experience Builder." This is more than a name change. The Experience Builder is intended to be a more intuitive, more capable visual editing tool that brings Drupal closer to the kind of drag-and-drop page building that association staff expect from modern CMS platforms. The goal is to let content editors create and modify page layouts without requiring a developer to configure layout templates.

Recipes and the Drupal CMS Initiative. Drupal 12 continues the work of the Drupal CMS initiative (formerly known as Starshot), which aims to make Drupal dramatically easier to set up and use out of the box. Central to this effort is the Recipes system, which allows pre-packaged configurations to be applied to a Drupal site. Instead of installing and configuring twenty modules to get a blog, event calendar, or member directory working, you install a Recipe that sets everything up in one step. For associations, this lowers the barrier to extending your site with new functionality.

Module Removals. Drupal 12 removes the Migrate Drupal and Migrate Drupal UI modules from core. These modules were specifically designed to migrate sites from Drupal 6 and Drupal 7 to modern Drupal. Their removal from core reflects the reality that Drupal 6 has been end-of-life since 2016 and Drupal 7 since January 2025. If your association is still on Drupal 7, this removal does not affect you directly since you would migrate to Drupal 11 (which still includes these modules) rather than jumping straight to 12. But it does underscore the urgency of getting off Drupal 7.

The Drupal 10 End-of-Life Deadline

This is the most immediately actionable piece of news for associations. Drupal 10 reaches end of life on December 9, 2026. After that date, the Drupal Security Team will no longer publish security advisories or patches for Drupal 10 core or contributed modules. Vulnerabilities discovered after that date will have no official fix.

For associations that handle member data, process payments, or store any personally identifiable information on their Drupal website, running an unsupported version is a serious risk. It is not just a technical concern. Organizations operating under audit requirements, compliance frameworks, or cyber insurance policies may find that running end-of-life software voids their coverage or triggers compliance violations.

The good news is that the upgrade path from Drupal 10 to Drupal 11 is one of the most manageable version upgrades in Drupal is history. Because Drupal 11 was built on the same architectural foundation as Drupal 10, it is an incremental upgrade rather than a full rebuild. Most sites can upgrade by updating their codebase, running database updates, and resolving any deprecated code in custom modules or themes. Tools like Upgrade Status and Drupal Rector automate much of the compatibility checking and code updating.

If your association is currently on Drupal 10, the window to upgrade to Drupal 11 is now through late 2026. Do not wait until December. Upgrades take time to plan, test, and deploy, and your developers will be competing with every other organization that waited until the deadline.

Where Does This Leave Drupal 7 Sites?

Drupal 7 reached its official community end of life in January 2025. Extended commercial support is available through third-party vendors, but the core project no longer maintains it.

If your association is still running Drupal 7, the path forward is a migration, not an upgrade. Drupal 7 to Drupal 11 (or eventually 12) is a rebuild. The content can be migrated using Drupal is migration framework (which is still in Drupal 11 core), but themes, custom modules, and site architecture need to be rebuilt from scratch. This is a significant project, typically comparable in scope and cost to a full website redesign.

Some associations in this position choose to evaluate whether Drupal is still the right platform. The migration from Drupal 7 is an equally heavy lift whether you are going to Drupal 11 or to WordPress, and the decision should be based on your organization is specific needs rather than platform loyalty. We covered this comparison in detail in our post on Drupal versus WordPress for associations.

Regardless of your target platform, if you are on Drupal 7, the time to act is now. Every month you wait increases the security risk and narrows the pool of developers available to help, since the Drupal community is increasingly focused on modern versions.

The Drupal 11 to 12 Upgrade Path

For associations already on Drupal 11 or planning to get there, the eventual upgrade to Drupal 12 should follow the same incremental model. Drupal is semantic versioning approach means that Drupal 12 will remove deprecated code from Drupal 11 but will not introduce breaking changes that were not previously announced through deprecation notices.

In practical terms: if your Drupal 11 site uses no deprecated APIs (which tools like Upgrade Status can verify), the upgrade to Drupal 12 should be relatively smooth. If your site has custom modules that use deprecated code, those modules will need to be updated before upgrading. This is standard maintenance work, not a rebuild.

The key variable is contributed module compatibility. Not every contributed module will have a Drupal 12 compatible release on day one. Before planning your upgrade, check the compatibility status of every module your site uses. The most popular modules typically release Drupal 12 compatible versions within the first month. Smaller or unmaintained modules may take longer or may never be updated, requiring you to find alternatives.

What the Drupal CMS Initiative Means for Associations

The Drupal CMS initiative, which will reach its full expression in the Drupal 12 era, represents a philosophical shift for the project. Historically, Drupal has been a developer-first platform. Setting up a Drupal site required significant technical knowledge: installing modules, configuring content types, building views, setting up permissions, and assembling an editorial workflow from dozens of individual components.

The Drupal CMS initiative aims to change this by providing an opinionated, ready-to-use Drupal installation that works out of the box for common use cases. The Recipes system is the engine behind this: pre-packaged configurations that set up entire features (blog, events, media gallery, contact forms) with a single installation step.

For associations, this could significantly reduce the cost and complexity of initial Drupal deployments. Instead of paying a developer to build an events system from scratch, you could install an Events Recipe that creates the content type, configures the calendar view, sets up the listing page, and wires the permissions. Your developer then customizes the output rather than building the foundation.

This does not eliminate the need for Drupal expertise. Custom integrations, complex permissions, AMS connectivity, and multi-site architectures will still require skilled developers. But it lowers the floor for common functionality, which means more of your budget can go toward the custom work that differentiates your site rather than rebuilding the same basic features every Drupal site needs.

Should You Wait for Drupal 12?

No. Here is why:

If you are on Drupal 10, upgrade to Drupal 11 now. Drupal 10 hits end of life in December 2026. Waiting for Drupal 12 means running unsupported software for months or longer. Get to Drupal 11 first, then upgrade to 12 when it stabilizes.

If you are on Drupal 7, start your migration project immediately. Whether your target is Drupal 11, Drupal 12, or a different platform entirely, you are already past the point where waiting makes sense. Every month on Drupal 7 is a month without security support.

If you are on Drupal 11, you are in the best position. Continue maintaining your site, keep your contributed modules up to date, and plan to evaluate Drupal 12 two to three months after its initial release. Let the early adopters shake out the bugs. Check your contributed module compatibility. Then plan a controlled upgrade.

If you are planning a brand-new Drupal site, build on Drupal 11 today. Starting on Drupal 11 gives you a stable, supported platform now and a clear upgrade path to 12 later. Waiting for 12 to launch delays your project by months with no guarantee that the first release will be ready for production use on complex association sites.

Drupal 12 and the Competitive Landscape

Drupal 12 arrives in a CMS market that has changed dramatically since Drupal is last major release. WordPress 7.0 shipped in May 2026 with native AI integration. Headless CMS platforms like Contentful and Sanity continue to gain market share in the enterprise segment. Website builders like Webflow and Squarespace are increasingly sophisticated.

Drupal is positioning itself at the intersection of enterprise capability and editorial usability. The Experience Builder, Recipes, and Gin admin theme are all aimed at closing the usability gap that has historically been Drupal is biggest weakness. The Symfony 8 foundation and the Abilities API equivalent ensure that Drupal remains a serious choice for complex, integration-heavy sites.

For associations, Drupal continues to make sense when your requirements include complex content modeling across multiple content types, sophisticated permission structures (chapter administrators, committee chairs, staff, public visitors), deep integration with enterprise AMS platforms, and multi-site or multi-language architectures. These are the scenarios where Drupal is flexibility outweighs its higher implementation cost.

If your association needs a marketing website with a blog, event listings, and a contact form, Drupal 12 is overkill. But if you are running a member portal with role-based access, managing a resource library with thousands of documents, integrating with Salesforce or iMIS, and serving content to multiple audiences across multiple sites, Drupal remains one of the strongest options available.

Preparing Your Organization

Regardless of your current Drupal version, here is what to do now:

• Audit your current version. Know exactly what version of Drupal you are running, what contributed modules you depend on, and whether any custom code uses deprecated APIs. The Upgrade Status module gives you a clear report.
• Plan your upgrade path. If you are on Drupal 10, schedule your Drupal 11 upgrade before the December 2026 EOL. If you are on Drupal 7, scope a migration project. If you are on Drupal 11, monitor Drupal 12 development and plan for a 2027 upgrade.
• Budget for ongoing maintenance. Drupal is continuous upgrade model means regular investment in keeping your site current. Budget annual maintenance hours for core and module updates, security patching, and version upgrades.
• Evaluate your hosting. Drupal 12 on Symfony 8 will require PHP 8.3 or higher. Confirm your hosting environment meets these requirements or plan to upgrade.
• Talk to your development partner. If you work with a Drupal agency or freelancer, have a conversation now about their Drupal 12 readiness, their experience with Drupal 11 upgrades, and their availability in the second half of 2026.

The Bottom Line

Drupal 12 is a meaningful release that brings a better editorial experience, modern architecture, and the beginnings of a more accessible Drupal for non-technical users. But it is an evolution, not a revolution. The continuous upgrade model means that organizations on Drupal 11 will have a clear, manageable path to 12.

The more urgent concern for most associations is not Drupal 12 features but Drupal 10 end of life. If your site is on Drupal 10, get to 11 before December. If your site is on Drupal 7, start your migration yesterday. Drupal 12 is the future of the platform, but the present demands attention first.