Navigating Drupal upgrades with Helm

These upgrades matter because they determine whether your site continues to receive security coverage and community support.

At Helm, we’re committed to making sure our partners aren’t caught off guard when those milestones arrive. We’ve developed a clear approach to Drupal upgrades that balances cost, complexity, and predictability.

Two Paths: Rebuilds vs. Routine Upgrades

Not all Drupal upgrades are created equal. The path you’ll take depends on which version you’re currently running.

The Big Leap: Drupal 7 to 11

For sites still on Drupal 7, the journey to Drupal 11 is not really an “upgrade” in the traditional sense. It’s closer to a rebuild.

• Content models in Drupal 7 differ dramatically from modern versions.
• Custom modules often need to be rewritten.
• Themes and front-end code must be reimagined to take advantage of Drupal 11’s capabilities.

Because of this complexity, we treat Drupal 7 → 11 migrations as standalone projects. They require planning, scoping, and dedicated development time that goes beyond the scope of Helm’s monthly service.

In practice, this means we’ll work with you to define a project plan, schedule, and budget specifically for the rebuild. Once your new Drupal 11 site is launched, Helm steps back in as your day-to-day partner for ongoing support and future upgrades.

The Predictable Path: Drupal 9 or 10 to 11

For teams already on Drupal 9 or 10, the story is much simpler. The move to Drupal 11 is more of a routine upgrade than a rebuild. The underlying architecture is similar, and most of the heavy lifting has already been done by Drupal core maintainers and the module community.

That’s why we include Drupal 9 → 11 and 10 → 11 upgrades in your monthly Helm service fee. No separate project is needed.

But here’s an important detail:

• Your Helm subscription includes a set number of hours each month.
• An upgrade counts against that monthly allotment.
• If the upgrade requires more hours than are available in a given month, we may borrow from future months to complete the work.

This ensures there are no surprise invoices, but it does mean your team should plan ahead for the upgrade window.

Why This Matters

We structure upgrades this way for a few reasons:

• Clarity: You know exactly what’s covered in your monthly fee and what requires a separate project.
• Fairness: Small, routine upgrades don’t trigger unexpected costs, while large rebuilds get the dedicated planning they deserve.
• Continuity: Once your site is on a modern Drupal version, Helm keeps you current with the least disruption possible.

Our goal is always to simplify the process, keep your site secure, and help your team stay focused on mission-driven work instead of infrastructure.

Staying Ahead of the Curve

Drupal’s release cycle is designed to be predictable. Every two years, a new major version arrives. Old versions eventually reach end-of-life. The best time to think about your upgrade isn’t when a version is about to expire, but well before.

At Helm, we keep an eye on the roadmap for you. We’ll let you know when an upgrade is coming, what it will involve, and how it fits into your service plan. For Drupal 7, that means talking through a migration project. For Drupal 9 and 10, it means scheduling a smooth upgrade that fits within your monthly hours.

The takeaway is simple: you won’t be surprised.

Helm’s Promise

Whether you’re planning a Drupal 7 rebuild or preparing for the move from Drupal 9/10 to 11, Helm is your partner in keeping things predictable, manageable, and secure. We’ve been through these transitions before, and we know how to balance technical rigor with practical constraints like budgets and timelines.

Upgrades are just one part of the journey—but they’re a part that can make or break your long-term success. With Helm, you can count on a steady hand at the wheel.