Why (and how) government agencies should migrate from DNN to Drupal

Government websites carry a heavier load than most. They publish public health alerts, permit forms, meeting minutes, and emergency updates. Every page has to be accessible, secure, and accurate on the day it goes live.

Many agencies built those sites on DNN, formerly DotNetNuke, more than a decade ago. It was a sensible choice for teams already invested in Microsoft infrastructure. This article looks at what has changed since, how compliance and governance factor in, why are government agencies considering to move to Drupal now, and what a migration to Drupal involves.

Key Takeaways

• DNN (DotNetNuke) still runs on ASP.NET Web Forms, which leaves government sites on aging technology with a shrinking community.
• Drupal gives agencies built-in accessibility, a dedicated security team, and granular roles that support WCAG 2.1 AA, Section 508, and ADA Title II obligations.
• State and local governments serving 50,000+ people must meet WCAG 2.1 AA by April 26, 2027, under the DOJ's extended Title II timeline.
• A DNN-to-Drupal migration runs in four stages: audit, build, content migration, and testing.
• The move is a chance to set up web governance (workflows, permissions, audit trails) that DNN made hard to enforce.

Why are government agencies moving off DNN?

DNN launched in late 2002 as an open-source CMS written in C# on ASP.NET Web Forms. Microsoft has since moved to a unified .NET stack, and Web Forms did not make the trip. DNN still depends on it.

A series of acquisitions and a shrinking contributor base have slowed the platform's momentum, as we covered in our guide on why and how to migrate a DNN site to Drupal. Fewer contributors means fewer modules, slower fixes, and a smaller hiring pool.

Customizing editorial workflows on DNN often takes extensive coding. So when a new accessibility rule or a records policy lands, the change request goes to a developer instead of the content team.

One of our clients (not a government agency) ran three DNN-based magazine sites that had picked up malware and needed major rework. We rebuilt them on a single Drupal distribution, which let the team launch new sites about 10x faster.

How does Drupal help government websites stay compliant?

Compliance deadlines are now specific and close. In 2024, the U.S. Department of Justice finalized a rule requiring state and local government web content and mobile apps to meet WCAG 2.1 Level AA under ADA Title II. An April 2026 interim final rule pushed the dates back by a year:

The standard itself did not change. Federal agencies follow Section 508, whose revised standards incorporate WCAG 2.0 AA. Either way, the CMS has to make accessible content the default.

Drupal does a lot of that work in core, which is a big part of why Drupal for government projects start from a strong accessibility baseline. It ships semantic markup, keyboard navigation, screen-reader support, and required alt text fields. The Claro admin theme and Olivero front-end theme were both built with accessibility as a requirement. Contributed modules such as Editoria11y flag issues while editors write, before a page is published.

What about security and data privacy?

Security is part of compliance for any agency handling resident data. A permit application or a records request carries names, addresses, and sometimes more. That puts the CMS squarely inside the agency's risk surface.

Drupal handles this through process as much as code. The Drupal Security Team works privately with maintainers until a fix exists, then publishes a coordinated advisory with a risk score. Contributed modules marked with a security shield fall under the same advisory policy, so agencies can check coverage before installing anything.

For the most serious issues, the team warns site owners ahead of time. In May 2026, it announced a highly critical core release two days in advance, so IT teams could book maintenance windows before any details went public.

Access control is the second layer. Drupal's role-based permissions limit who can see or change sensitive content, and contributed modules add two-factor authentication and password policies for staff accounts.

Hosting completes the picture. Acquia, which runs a dedicated government cloud offering, achieved FedRAMP Authorized status for Acquia Cloud Next in 2024. For a migration, the practical lesson is to plan patching, roles, and hosting together, well before launch day.

What does web governance look like on Drupal?

Web governance is the set of rules for who publishes what, when, and with whose approval. On a government site, it is also how you prove a page met policy on the day it went live.

Drupal turns those rules into configuration. The Content Moderation and Workflows modules in core let you define states such as Draft, Legal Review, and Published. Each role gets only the transitions it needs. A department editor can draft, but only a web manager can publish.

Revisions log every change with an author and timestamp. That audit trail helps with records requests and accessibility complaints. Scheduled publishing handles board agendas and public notices that must go live at a set time.

A shared Drupal design system keeps every office on the same accessible components, while each team manages its own section. Specbee's web governance services add automated accessibility scanning, PDF remediation, and consent management on top.

What are the benefits of migrating from DNN to Drupal?

Beyond compliance, agency teams notice the day-to-day gains first.

Lower costs on a modern stack

Drupal is open source, so there are no license fees and procurement stays simpler. Drupal 11 runs on Symfony 7 and Twig 3, with predictable major releases and clear upgrade paths.

More independence for content teams

Drupal CMS 2.0 adds Recipes, Project Browser, Automatic Updates, and Experience Builder, so content teams build pages without filing tickets. Core translation support helps agencies serving residents in more than one language.

Capacity for traffic spikes and long-term support

Advanced caching handles traffic surges during elections, storms, and public health events. Drupal powers sites in more than 150 countries, so skilled support is easier to find than for a shrinking platform.

Proven results at government scale

When Specbee migrated the New York State Department of Health's Wadsworth Center site, multiple pages moved with zero downtime. Organic traffic grew 38% after launch.

How does a DNN to Drupal migration work?

A government migration follows the same four stages as any DNN move. Our Drupal migration services include compliance checks built into each stage.

Step 1: Audit the DNN site

Inventory DNN modules, content types, URLs, metadata, and media. Run an accessibility baseline, so you know which issues to fix during the move instead of carrying them over.

Step 2: Build the Drupal foundation

Rebuild the content model and theme in Drupal. Set up roles, moderation workflows, and accessible components before any content arrives.

Step 3: Migrate the content

Export DNN data as CSV, XML, or JSON, then map it to Drupal content types and fields with Drupal's Migrate API. Validate every batch for accuracy and completeness.

Step 4: Test and launch

Check data integrity, run load and security tests, and complete an accessibility review against WCAG 2.1 AA. Map old URLs to new ones with redirects so residents and search engines land in the right place.

Sign off each step with your web, legal, and accessibility owners before moving on.

When is the right time to start a DNN to Drupal migration?

The right time is before a deadline sets the schedule for you. Drupal 10 reaches end of life on December 9, 2026, and Drupal 12 arrives the same week. A DNN migration that starts now lands directly on Drupal 11, and the later move to Drupal 12 is a routine upgrade.

The second date is April 26, 2027, when larger state and local governments must meet WCAG 2.1 AA. Starting now leaves room to finish, test, and fix issues before then.

Specbee is a Drupal Certified Partner with Acquia Certified Developers and hands-on government migration experience. Our initial migration audit is free. Talk to our Drupal team about your timeline and compliance goals.

Frequently Asked Questions

How long does a DNN to Drupal migration take for a government agency?

Most DNN to Drupal migrations take a few weeks to a few months. The timeline depends on content volume, custom DNN modules, and integrations such as payment or permit systems. Building accessibility and governance checks into each stage adds little time and avoids rework later.

Is Drupal compliant with Section 508 and WCAG 2.1 AA?

Drupal core is built to support WCAG 2.1 AA and Section 508. No CMS makes a site compliant on its own, though. Compliance also depends on your theme, your content, and your publishing workflow, so an accessibility review belongs in every migration.

When do state and local governments need to meet ADA Title II web rules?

Entities serving 50,000 or more people must meet WCAG 2.1 AA by April 26, 2027. Smaller entities and special districts have until April 26, 2028. The DOJ extended both dates by one year in April 2026.

Will our URLs and search rankings carry over from DNN?

Yes, content, media, metadata, and URL structures can all carry over. A redirect map sends old DNN URLs to their new Drupal pages, so residents' bookmarks keep working and search engines keep their signals.

Can we keep our current hosting after migrating?

Drupal runs on standard PHP hosting, including government-focused clouds such as Acquia. Agencies moving off Windows servers can consolidate hosting during the move.