Moving a website is like moving house. It always costs more and takes longer than the brochure suggests, and half of what is in the attic turns out to matter. Keene Systems migrates sites to, from and between editions of DNN, and we will tell you first whether the move is worth making.
Most companies that ask about leaving DNN have one of two problems: the site is badly out of date, or the developer who looked after it has gone. Neither is a reason to rebuild. Both are cheaper and quicker to fix where you are.
| Your situation | What usually makes sense |
|---|---|
| The site is several versions behind | Upgrade it |
| Your DNN developer left | Put a team behind it |
| You pay for Evoq and use little of what it adds | Move to the open-source DNN Platform |
| The custom modules have become the whole system | Rebuild as a custom web application |
| The site is only pages and articles, with no logins or custom modules | WordPress is a reasonable move |
| Your current site cannot handle logins, permissions or business data | Move it onto DNN |

Evoq is the commercial edition of DNN, sold on an annual license. It adds a small number of features to the free, open-source DNN Platform, and the best known is content approval workflow. We build on the open-source platform. In our experience the differences are few, and when a client needs one of them it is better value to add that one feature than to license a whole edition for it.
A recent example: Trailmark Bank wanted content approval, so that a change to a page is reviewed by a second person before the public sees it. It was the one Evoq feature they needed. We wrote it as a custom DNN module instead. They got an approval process built around how their own staff work, and they are not paying for an annual license to have it.
If you are on Evoq today and use little of what it adds, the site can be moved to the open-source platform. The work is in the differences:
Some DNN sites stop being websites. Over the years the custom modules grow until they run orders, scheduling or customer accounts, and the content management system around them is along for the ride. At that point DNN can be in the way: every platform upgrade risks the modules, and the modules cannot use what modern ASP.NET offers.
When that is the case, we rebuild the system as a custom ASP.NET Core web application. This is our core business, and a DNN site is a better starting point than most:
We begin these projects with our no-risk business analysis. A senior business analyst documents what the system does and what it should do, and you have a written requirements document before you commit to anything. See legacy application modernization.
Pages, articles, images and documents move to WordPress without much trouble. Custom modules, user logins, permissions and business data do not move. They have to be rebuilt, and that rebuilding is where the time goes.
So the question is what your site does. If it is a brochure and a blog, WordPress is a sensible home and plenty of people can run it. If customers or staff log in to do something, think hard before you go. We build on both platforms and will give you a straight answer. The full comparison is in DotNetNuke vs. WordPress.
Migration runs the other way too. A hand-coded website that needs a programmer for every change, or a site that has outgrown a simpler tool, can be moved onto DNN so staff manage the content themselves. We converted the website of Southwestern Vermont Health Care, a hospital with eight facilities, to DotNetNuke and added custom modules to manage and display its doctors by specialty.
Sometimes the platform is fine and the server is the problem. We can move a DNN site to a new host or onto Microsoft Azure, including the database, the files and the settings that never make it into anyone’s notes.
We have built custom business software since 1987, worked in ASP.NET since 2002 and in DNN since 2004. That covers both ends of any move involving DNN. Our 50+ professionals include the developers, database architects, designers and business analysts a migration needs. See our DotNetNuke development services.
Not sure which way to go? Book a 20-minute call and we will tell you what we would do in your position.
Usually not. If the trouble is an old version or a departed developer, an upgrade and a support team fix it for far less than a rebuild. Migration makes sense when the site has outgrown a CMS or never needed one.
Yes, once the Evoq-only features it uses have been identified and replaced or retired. Often one small custom module covers the feature that mattered.
Yes. Content moves across. Custom modules, logins and business data have to be rebuilt, so we look at what the site does before recommending it.
For a content site, WordPress. For a business system, a custom ASP.NET Core web application. Which one fits depends on whether your site is mainly content or mainly function.
Not if it is done properly. We redirect every old address to its new one and check the results after the switch.
Keene Systems has built custom business software since 1987. We are veteran-owned, and our 50+ professionals have delivered systems for companies including Hormel, McCormick, IBM and Dartmouth-Hitchcock. See our client list.
Talk to a DNN developer