In this post
Many businesses still run websites built years ago on DNN or older .NET versions. They work, but they are slow to change, hard to keep secure and increasingly hard to find people for. Moving to something modern is often the right call. The main risk is not the new site — it is losing the search traffic the old one has earned.
1. Make a list of every address
Before anything is built, export every page address the old site has: from its sitemap, from Google Search Console and from your analytics. Note which pages bring visitors and enquiries. Those are the ones that must survive the move.
2. Decide where each old page goes
Every old address needs a home on the new site — the same page, or the closest one. Write it down as a simple two-column list: old address, new address. Nothing should be left pointing nowhere.
3. Set up permanent redirects
On launch day each old address should send visitors, and search engines, to its new home with a permanent (301) redirect. This tells Google the page has moved rather than disappeared, and carries most of its standing with it.
4. Keep what the old pages said
If a page ranks for a phrase, the new page should still answer the same question. A redesign is a good time to improve the words — just do not delete the topic that brought people in.
5. Watch the first weeks closely
After launch, check Search Console for pages Google cannot find, fix any missing redirects quickly and submit the new sitemap. A small dip that recovers within weeks is normal. A steep, lasting drop usually means redirects are missing.
What about the content and users inside DNN?
Pages, news, documents and user accounts can usually be moved across rather than typed in again. It is worth checking early what has to move and what can be left behind.
DNN and .NET are part of our everyday work. If you are planning a move, we are happy to look at your current site and tell you what is involved.
