One of the biggest advantages of DNN is what comes out of the box, of course. The time it takes for a team to assimilate DNN will obviously vary, so it's hard to say how long anything will take. I can say, however, that taking a phased approach to implementing DNN is probably one of the more popular approaches that I've seen. You can keep your existing site as-is (or at least with very few modifications) and use the IFrame module to link to the pages within the legacy app. From there, you can identify what can be replaced with core modules. This should be your initial release (or second release, if you want to simply release DNN as a wrapper first). At this point, you've most likely gotten rid of all your legacy semi-static content and have the "real" work ahead of you. Prioritize legacy features and look at existing modules to see if you can they can be used to modernize legacy code. You may have to modify core modules, but sometimes that can prove best, if your team feels comfortable with that. All you really have to do now is attack modernizing modules one at a time. Sometimes, if you keep your modules abstract enough, you can cover multiple modules at once.

Not sure what else to tell you. It's really pretty simple to get your modernization started. The biggest thing I can really suggest is to review the module dev doc to make sure you have a good idea of what it takes to develop modules.

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com