DotNetNuke runs on legacy ASP.NET Web Forms, requires Windows Server hosting that costs 2-5x more than Linux alternatives, and has a module ecosystem that has been contracting for years. Here is why organizations are leaving, and what a proper migration to WordPress involves.
The .NET Stack Problem
DotNetNuke is built on ASP.NET Web Forms, a framework Microsoft introduced in 2002 and has since superseded with ASP.NET MVC, ASP.NET Core, and now .NET 8 and 9. Web Forms carries architectural legacy: ViewState bloat, page life-cycle complexity, and a rendering model that was designed for desktop-style applications, not the lightweight, stateless HTTP requests that modern web performance requires. According to a technical analysis published by Symphonize (March 2026), DNN‘s core architecture has not kept pace with modern development paradigms, carrying Web Forms baggage that makes unit testing difficult and performance optimization unpredictable.
The .NET stack dependency has a second consequence that is purely financial. Running a DNN site requires Windows Server and IIS. Linux hosting, which powers the overwhelming majority of the web including every standard WordPress installation, is not an option. Windows Server licences add cost that Linux-based hosting does not carry. According to hosting comparison data, DNN hosting typically costs two to five times more than equivalent Linux/WordPress hosting for the same storage and traffic capacity. Over a multi-year period, that gap compounds significantly.
A Declining Community and Thinning Module Ecosystem
DNN powers around 600,000 to 750,000 websites worldwide. WordPress powers over 800 million. That is not a gap that closes. And unlike platforms with a smaller but deeply committed ecosystem (like certain enterprise Java CMSs), DNN‘s module marketplace has not maintained the community investment that kept it vibrant in the 2008-2014 era.
A decline in the DNN community has led to fewer developers working on functionality and providing patches and updates for the platform. This poses several risks for those who use the CMS as lengthy periods between receiving these often critical fixes may result in security vulnerability or even affect website performance.
WordHerd Migration, DotNetNuke to WordPress Migration Services, 2023
An interesting project but not much up to date. Has been around for years but we moved on to a different platform.
Verified reviewer, Gartner Peer Insights, 2024
Evoq has been becoming slightly more bloated over the years and uses a lot of system resources on the server side even when idle. DNN management of a web farm of IIS servers is, to put it simply, a bit buggy.
G2 user review, Evoq Content
The practical consequence is that modules that were actively maintained three or four years ago are now stale. New modules are not being built by developers who can earn more working on WordPress, where the user base is thousands of times larger. When a DNN module fails or becomes incompatible with a newer DNN version, the options are: find one of the dwindling pool of DNN specialists to fix it, pay to have it rebuilt, or abandon the functionality entirely.
DNN Modules and Their WordPress Equivalents
Every piece of functionality that DNN provides through its module system has a well-supported WordPress equivalent. The table below maps the most common DNN modules to their counterparts, including the one many organizations care about most: moving from the DNN forum module to wpForo 360° AI, which brings full AI-powered community features that the DNN forum system cannot match.
| DNN Module | What It Does | WordPress Equivalent | Cost |
|---|---|---|---|
| HTML Module (core) | Freeform HTML/text content blocks on any page | Gutenberg Block Editor (built in) | Built in |
| Announcements Module (core) | Simple dated content listings | WordPress Posts / custom CPT (built in) | Built in |
| Ventrian News Articles / EasyDNNnews | Structured article publishing with categories | WordPress Posts + ACF Pro content fields | Free + Pro |
| Active Forums / DNN Forum | Community discussion boards and Q&A | wpForo 360° AI (full forum with AI features) | Free + Pro |
| Forms & Lists (core) | Basic form building and data collection | Gravity Forms / WPForms / Fluent Forms | Free tiers |
| Catalook Store | E-commerce: products, cart, checkout | WooCommerce (8M+ active installs) | Free core |
| EasyDNNevents / Events Module | Event calendars and registration | The Events Calendar (700k+ installs) | Free core |
| DNN Blog Module | Multi-author blog with comments | WordPress native blogging (built in) | Built in |
| Photo Gallery Module | Image gallery management and display | NextGEN Gallery / WP native galleries + ACF | Free tiers |
| Documents Module | File library management and downloads | WordPress Media Library + WP File Manager | Free tiers |
| DNN Skin (theme system) | Template files controlling page layout and design | Custom WordPress theme (PHP/HTML) | Custom dev |
| Role / Permission Manager | Granular page and module access control | WP User Roles + MemberPress / Ultimate Member | Free core |
| Google Analytics Module | Site analytics integration | Site Kit by Google / native GA4 integration | Free |
A note on the forum migration. Many DNN sites run Active Forums or the built-in DNN Forum module with years of discussion threads, registered community members, and accumulated knowledge. gConverter migrates DNN forum content directly into wpForo 360° AI, mapping forum categories to wpForo categories, topics to wpForo threads, replies with author and timestamp data preserved, and member accounts to wpForo user profiles. The result is a fully populated community platform with complete history intact and AI moderation and search features the DNN forum module never had.
What a Proper DotNetNuke Migration Involves
A DNN site is structured around portals, pages, and modules. Each page is a container for one or more module instances, each of which holds content independently. The content model is fundamentally different from WordPress‘s post and page hierarchy. A proper migration cannot be done by exporting XML and importing it. It requires reading from the DNN SQL Server database directly and mapping each content type to its WordPress equivalent. Here is how each layer is handled.
Pages to posts and pages
DNN pages (tabs) become WordPress pages or posts depending on their content type and purpose. Static content pages (About, Services, Contact) become WordPress pages. News, article, and blog pages become WordPress posts or custom post type archives. Portal tab hierarchies are replicated in WordPress‘s native page hierarchy so that the navigation tree is preserved exactly.
HTML Module content
The HTML Module is the most common way DNN sites store textual content. Each instance is stored in the HtmlText table in the SQL Server database. Every HTML Module instance is migrated to the corresponding WordPress page or post body as a Gutenberg HTML block, preserving all formatting, inline images, and hyperlinks.
Ventrian News Articles and EasyDNNnews
These modules store structured article content in their own database tables with custom field values per article. A proper migration reads these tables directly, creating WordPress posts with ACF Pro field groups that match the original article structure. Category structures, author attributions, publication dates, and custom field values are all preserved.
Forum content to wpForo
DNN forum data (from Active Forums or the core Forum module) is stored in module-specific SQL Server tables. Forum categories become wpForo 360° AI categories. Forum boards become wpForo 360° AI sub-forums. Topics are migrated with their original author attribution, view counts, and publication timestamps. All replies are nested correctly under their parent topics. Member data is cross-referenced with the DNN user system to correctly attribute authorship throughout.
User accounts and roles
DNN maintains its own user system in the Users, UserRoles, and ProfilePropertyDefinition tables. All registered users are migrated to WordPress with role mapping. DNN Administrators map to WordPress Administrators. Custom roles are created in WordPress using a matching structure. User profile field data (custom properties defined in the DNN Profile system) is imported as WordPress user meta. Passwords use different hashing algorithms between the two systems, so users are prompted to reset passwords on first login via a secure email link.
Skin to theme
DNN skins define the layout and visual design of the site in ASCX container files. They cannot be ported directly to WordPress. A proper migration delivers a custom WordPress theme that replicates the visual output of the original DNN skin exactly: same header, footer, navigation structure, sidebar layout, typography, and colour scheme. The result is visually identical to the original site but built on native WordPress PHP templates with no dependency on the DNN skin architecture.
URLs, SEO, and redirects
DNN generates page URLs from the tab path (e.g., /Home/About-Us). Where these paths can be replicated in WordPress permalink settings, they are. Where the structure changes, 301 redirects are created for every affected URL using the Redirection plugin. SEO metadata (titles, descriptions, keywords) stored in the DNN PageHead settings or third-party SEO modules is imported to Yoast SEO. No page goes live without its SEO data intact.
What Bad DNN Migrations Look Like
- HTML Module content flattened or lost. Generic migration tools do not know how to read the
HtmlTextSQL Server table. Content from HTML Module instances is either skipped entirely or imported as a single undifferentiated text blob with no page association. - Module-specific content silently abandoned. Ventrian News Articles, EasyDNNnews, and custom module data all live in separate SQL tables. Tools that do not specifically map these tables leave all structured article and news content behind.
- Forum threads dropped. Active Forums content is stored in module-specific tables that generic tools do not handle. Years of community discussion history are simply not imported, and no error is raised.
- Skin not converted. Some providers copy the HTML and CSS from the existing DNN skin into a basic WordPress template and call it done. The result is a brittle, unmaintainable theme that breaks when WordPress is updated and does not follow WordPress template hierarchy conventions.
- User accounts missing profile data. DNN Profile property values stored in
UserProfileandProfilePropertyValuestables are rarely handled by generic tools. User accounts arrive in WordPress with names and email addresses but no other profile information. - No URL redirects. The DNN tab URL structure is replaced by default WordPress slugs with no redirects in place. All existing inbound links and search engine rankings for specific pages break immediately.
GDPR and Your Data
A DNN SQL Server database contains every piece of personal data your site has ever collected: registered user accounts with email addresses, hashed passwords, and profile data; contact form submissions from the Forms module; forum member data including post history linked to user identities; and e-commerce customer records if you use Catalook. Moving this database to WordPress is a personal data transfer under GDPR. Before any migration provider accesses your data, you need a signed Data Processing Agreement, clarity on where the data will be processed, how it will be encrypted, and when it will be deleted.
gConverter is US-registered with full EU GDPR compliance. We sign a DPA before any access is granted. All credentials are stored in AES-256 encrypted vaults, transmitted over TLS 1.3, and deleted within 24 hours of job completion. All customer data is permanently deleted within 30 days. Read the full GDPR documentation →
What Clients Say
Went FAR above and beyond to help us work through this project. We are thrilled with the final result and they were professional, great to work with, and responsive every step of the way. Would highly recommend.
Anna P., Wilmington NC – Customer Lobby, January 2026
There were very few conversion issues on the first pass, and they cleaned it right. Very impressive.
Stacy C., Katy TX – Customer Lobby, November 2025
The Bottom Line
DotNetNuke earned its reputation during the ASP.NET era. But that era has passed. The Web Forms architecture is a Microsoft legacy path. The hosting costs are structurally higher. The module ecosystem has thinned. The developer community has contracted. And the skills required to build and maintain a DNN site are expensive because the platform serves a small and shrinking audience.
WordPress runs on Linux, costs a fraction to host, has a developer community orders of magnitude larger, and has a plugin ecosystem covering every use case. Every page, every article, every forum thread, every user account, and every carefully optimized URL on your DNN site can be migrated cleanly. And when your community forum moves, it moves into wpForo 360° AI, not into a stripped-down replacement.