Replacing Drupal 7 for Utilities: What the Migration Actually Involves

Drupal 7 support ended in January 2025. If your site connects to a CIS, OMS, or billing portal, a rebuild alone won't cut it. Your ratepayers use that site to pay bills, report outages, and check service status. Each integration needs a plan before you start.

We've built and maintained Drupal sites for utilities for over a decade. Delaware Electric Cooperative has been with us that whole time. We've worked through four website evolutions, the Beat the Peak mobile app, and ongoing integration support with their outage management system. That history matters when you scope a Drupal 7 replacement. The integrations that made the original site complex are still there. They need to be rebuilt, tested with real data, and handed off to a communications team that's usually small.

Replacing Drupal 7 for a utility is a platform migration. It touches authenticated ratepayer portals, third-party data feeds, accessibility, and sometimes regulatory reporting. To keep the scope honest, start with a technical audit.

Why utilities face a harder migration than most organizations

Most organizations leaving Drupal 7 move content, a theme, and a few contributed modules. Utilities have all that plus live data integrations your ratepayers depend on 24/7. When the outage map goes down at 11 PM during a storm, your team hears about it right away. That reality shapes how you scope and sequence the migration.

Utility sites mix public content with authenticated features. A member might read a news release, check the outage map, log in to pay a bill, and submit a service request in one visit. Each of those runs on different infrastructure. Migrations fail when they move the content layer but overlook the portal or the OMS feed.

Staffing matters too. Investor-owned utilities usually have IT departments. Electric cooperatives, municipal utilities, and water utilities often don't. The people who inherit the new site handle member communications, social media, and board reporting. If the editing experience is unmanageable, the platform hasn't solved the problem.

The integrations that drive scope: CIS, OMS, and billing

Integrations set the real scope. Three systems drive most of the complexity.

Customer information systems hold account data, billing history, and service records. The authenticated portal pulls from the CIS so ratepayers can view bills, make payments, and update account details. If your new Drupal site doesn't have a clear plan to authenticate and communicate with the CIS, the portal breaks at launch. That's a hard problem to recover from.

Outage management systems feed the live maps your ratepayers expect. The integration usually means real-time data exchange through a vendor API, sometimes with custom middleware built for your utility. That middleware doesn't carry over on its own. It needs to be documented, tested in the new environment, and validated against the OMS vendor's current API specs, which may have changed since the original integration.

Billing portals add a third layer. Some utilities use their CIS vendor's portal. Others build custom billing workflows in Drupal. If you have a custom billing integration on Drupal 7, you'll need to rebuild it for the new version. This isn't a find-and-replace job. Significant changes to modules, APIs, and data structures across major versions make migration more complex and time-sensitive. Running an unpatched, end-of-life CMS against live account data is a growing security risk. It is a reason to scope the work accurately from the start.

Build on Drupal 11

Build on Drupal 11. Drupal 10 reaches end of life on December 9, 2026. Migrating to Drupal 10 puts you close to unsupported from day one. Going straight from Drupal 7 to Drupal 11 avoids a second migration right after launch.

Accessibility and security requirements

The Department of Justice's ADA Title II rule, finalized in 2024, sets WCAG 2.1 AA as the standard for state and local government websites and mobile apps. In April 2026, DOJ extended the compliance dates by a year. Government entities serving 50,000 or more people now have until April 26, 2027. Smaller entities and special district governments have until April 26, 2028. The requirements themselves didn't change.

Title II covers state and local government entities, including municipal utilities and special districts. If that's you, the migration is your best chance to reach full compliance, but only if accessibility is built in from the start. Interactive outage maps, authenticated portals, and payment forms all have specific accessibility requirements that are slow and expensive to fix after launch.

Security needs the same early attention. Your new Drupal site should include role-based access controls, secure authentication, and a defined update schedule. That's an ongoing commitment, and it belongs in your maintenance agreement.

What drives the cost of a utility migration

We don't publish price ranges because your integrations set the number. If your site is mostly static content, a vendor-hosted outage map, and no custom portal, that's a different project than one with a custom CIS integration, middleware for a dynamic outage map, and a billing workflow built in Drupal. The complexity of those integrations and the quality of your CIS vendor's API documentation move the estimate more than anything else. If an agency quotes a flat number before auditing your environment, they're guessing.

Ongoing maintenance counts too. Drupal 11 needs security updates, module updates, and regular compatibility testing. If your communications team doesn't have engineering resources, a managed maintenance agreement with the agency that built your site keeps it secure.

Training is a real line item. If your team can't publish news releases, update outage information, and manage digital forms without filing tickets, the migration hasn't delivered value.

How Inclind structures utility migrations

We start every utility migration with a technical audit before any design or development work. The audit documents every integration, custom module, data dependency, and piece of functionality your ratepayers use. The resulting scope reflects your real environment.

From there, we sequence the work to protect continuity. The outage map and authenticated portal carry the most risk, so we test them first. We test integrations in staging against live data from your CIS or OMS. Mock data hides the edge cases that show up in production.

Our long partnership with Delaware Electric Cooperative shows us what utilities need to run day-to-day. We apply that standard to every utility project.

We build for the team that inherits the site. We set up content editing workflows, media management, form builders, and alert systems for people who aren't developers. That's a design decision we make early.

Water utilities face the same structure. A CIS sits behind the portal, service alerts must stay current, and a small team runs it all. We bring the same audit-first approach to those projects.

Start with a technical audit.

If your Drupal 7 site is still running, every month without security patches adds risk to live ratepayer data and critical infrastructure communications. That risk grows the longer you wait.

A proposal based on what an agency thinks your site involves is the wrong starting point. The right one is a technical audit of what your site actually does, documented in enough detail to produce a scope you can trust and a budget that won't surprise you six months in.

We've done this work for utilities for over a decade. We know where the complexity sits, how to sequence a migration that protects operational continuity, and how to build a Drupal 11 platform your communications team can run day to day.

Contact us to schedule a technical audit of your Drupal 7 environment. We'll show you exactly what the migration involves before you commit to anything.

Contact us to schedule a technical audit of your Drupal 7 environment. We'll tell you what the migration involves before you commit to anything.