Skip to main content

Keene Systems, Inc.

DNN Upgrade Services

Most DNN sites that are years out of date got that way for a sensible reason: somebody tried the upgrade, something broke, and they put it back. Keene Systems upgrades DotNetNuke sites in stages, on a copy, with every module tested along the way, so the live site only changes once we know it will work.

Why old DNN sites stay old

Upgrading DNN itself is the easy part. The hard part is everything attached to it. A typical site has a dozen or more third-party modules, a few custom ones and a theme, each written for the version that was current at the time. Move DNN forward and any of them can stop working. With no developer on hand to fix what breaks, staying put looks like the safe choice.

IT professional working at a computer in a server room

What staying on an old version costs you

  • Security. Each release fixes known holes. Older releases also shipped with third-party components that have since been found vulnerable. An unpatched site is the kind attackers look for.
  • Compatibility. Servers, browsers and the .NET Framework move on. Eventually a routine server update takes the site down.
  • Modules. Vendors stop supporting old versions, so you cannot buy fixes or new features.
  • A harder upgrade later. Every version you skip is another step to climb when you finally do it.

How we upgrade a DNN site

  1. Inventory. We record the DNN version, every module and its version, the theme, the database and the server it all runs on.
  2. Plan the path. An old site cannot jump straight to the current release. It has to pass through specific intermediate versions in order, and the server may need a newer .NET Framework and SQL Server on the way. We map each step before we start.
  3. Check every module. For each one we find out whether a compatible version exists, whether it needs replacing, or whether it is custom and needs our developers to update it.
  4. Upgrade a copy. We take a full copy of the site and run the whole path on it, fixing what breaks at each step.
  5. You test. Your staff use the upgraded copy and tell us what looks wrong. We fix it.
  6. Go live. We repeat the proven steps on the live site at a quiet time, with a backup we have already tested restoring.
  7. Follow up. We stay close afterwards for anything that only shows up in daily use.

What usually breaks, and what we do about it

  • Custom modules written against parts of DNN that have since changed. We update the code. If the source is missing, see custom DNN module development.
  • Abandoned third-party modules. We replace them with a supported equivalent and move the content across.
  • Old themes that were never built for phones. An upgrade is a good moment to move to a modern responsive theme.
  • Editor and admin changes. The administration screens in current DNN look different. We train your staff and record the session.

A good time to clean house

An upgrade is also the best chance you will get to remove what the site no longer needs: unused modules, forgotten pages, old user accounts and workarounds for features DNN now has built in. A smaller site is faster, safer and cheaper to look after.

Not sure what state your site is in? Start with a review on our DNN support and site takeover page. For everything else we do on the platform, see DotNetNuke development services.

Schedule a DNN upgrade exploration call or use the form on this page.

DNN upgrade questions

Can you upgrade a very old DotNetNuke site?

Yes. Older sites go through more intermediate versions, so there are more steps, and the method is the same: on a copy first, tested at each stage.

Will we lose content in an upgrade?

No. Pages, users and files carry forward. Where a module has to be replaced, moving its content across is part of the work.

Will the site be down during the upgrade?

Only for the final switch, which we schedule for a quiet time. All the trial and error happens on the copy.

Should we upgrade or rebuild?

Upgrade, in most cases. If the review shows the site has outgrown DNN, we will say so and explain the options.

Talk to a DNN developer

Why Keene Systems

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.

Schedule a project exploration call.

Schedule a Project Exploration Call

This free session is your fastest path to improved business productivity.