Skip to content
← Back to Blog

Your Drupal Site Now Needs Two Upgrades a Year. Budget for Them Like a Subscription, Not a Project.

The once-a-year upgrade habit no longer works. How associations and nonprofits without a Drupal developer should budget and schedule the new rhythm.

Most associations and nonprofits on Drupal budget for the website the same way: a redesign every several years, a maintenance line in between, and an upgrade project when someone says the version is about to go out of support. That last part used to come up about once a year.

Starting in 2027, it comes up twice. Drupal has cut security support for each minor version from twelve months to eight. A site now has to move to the next minor version within about two months of its release, every June and every December.

Where this comes from. The Drupal Security Team's announcement of November 2, 2026, PSA-2026-11-02, and Drupal's core release schedule, read directly. Our first post on the change has the full list of dates.

Why the Old Budget Habit Breaks

Under the twelve-month window, an organization could skip every other release and do one upgrade a year, usually when the budget allowed. Under the eight-month window, there is no skipping. Each release has to be applied within roughly two months of the next one shipping.

That timing does not care about your fiscal year. A December release lands in the middle of year-end giving. A June release lands in conference season for many associations. "We will do it next budget cycle" now means running an unsupported site for part of the year.

The Organizations This Hits Hardest

In our experience, the associations and nonprofits most exposed are the ones without a Drupal developer on staff. The site was built by an agency, someone on the communications team edits it, and upgrades happen when a vendor is called in. That model worked when upgrades were rare. It does not hold up at twice a year, plus weekly module advisories.

The other exposed group is anyone still on Drupal 10. Drupal 10 reaches end of life on December 9, 2026. After that, there are no security fixes for it at all.

Budget It Like a Subscription

The work is now predictable: two minor upgrades a year, module updates most weeks, and a major version upgrade every couple of years. In our experience, predictable work costs less to buy as a monthly service than as a series of emergency projects, because nobody has to scope, approve and schedule each one from scratch.

  • One line, every month. A monthly amount that covers security updates and both minor upgrades, not a project line that only appears when something is about to expire.
  • Two dates on the calendar. Name the June and December windows in your annual calendar, alongside the conference and the year-end appeal, so staff can plan content freezes around them.
  • Majors are separate. A major version upgrade, such as Drupal 11 to Drupal 12, is larger work. Drupal 11 is supported until December 2028, so plan it for a year when you are not also redesigning.

What 2027 Looks Like

  • Before the week of December 7, 2026. If you are still on Drupal 10, this is not optional. Move to a supported version before December 9.
  • By April 21, 2027. Sites on Drupal 11.4 move to 11.5 or 12.0, both released in December 2026.
  • June to August 2027. Drupal 11.6 and 12.1 are scheduled for June. The December versions stay covered until August.
  • December 2027 to February 2028. The next releases arrive in December, and the June versions stay covered until February 2028.
  • Every week. Module security advisories usually publish on Wednesdays. Someone reads them and applies the ones that affect your site.

What to Tell Your Board

The site still runs on the same software. Drupal still supports each major version for at least four years. What changed is the maintenance rhythm, and the reason is outside anyone's control: AI tools are producing more security reports than the Drupal Security Team can process at the old pace. Keeping the site covered now takes steady attention instead of an occasional project.

Keep Your Drupal Site on a Supported Version

Our partnership plans give you a team that tracks Drupal core and module security releases, applies the updates, and schedules the two minor upgrades a year so your site does not run on an unsupported version. Every plan is a set number of hours each month, so security updates, upgrades and improvements come out of the same predictable budget.

See our partnership plans →

Ask about your Drupal site →

83 Creative

We're a web development studio that works exclusively with trade associations, professional societies, and membership organizations.

← Previous Article Redesign, Rebuild, or Replatform? What Each Word Actually Means on Your Invoice