Convert DNN Evoq to DNN Platform

Do you want to convert, downgrade or migrate your DNN Evoq version to the free Platform (formerly Community) edition? No problem! Follow these proven steps and you'll be on your way!

  • Posted on Nov 08, 2016

There have been many different flavors of the licensed DNN (DotNetNuke) CMS over the past few years including DNN Professional, DNN Enterprise, EVOQ Content, EVOQ Engage and EVOQ Social. While all of them have had great features, and solved challenges for many customers - sometimes the yearly licensing costs can outweigh the benefits for your organization.

The DNN Corp does not officially provide or support a migration path for existing customers to downgrade or migrate away from the EVOQ products to the free DNN Platform (formally DNN Community) version. However, I have successfully preformed the migration over a dozen times.

The following is as a high-level list of tasks that you must perform to remove the EVOQ Enterprise (or whatever flavor you are running) modules, providers, etc. Please note, I advise that you only complete this in a fully isolated non-production environment. As well, thorough testing of your site(s) should occur before migrating it back to production - all sites are different and yours may have unique characteristics that the below do not consider.

Steps to Migrate from DNN EVOQ to DNN Platform

  1. Convert System Extensions - To delete the EVOQ extensions from the Extensions page you must change them from System to Non-System packages. There is a IsSystemPackage in the Packages table. Most of the EVOQ extensions have Professional, Enterprise or EVOQ in the package name. You will want to create and validate a list of packages that are truly from the paid version before doing this.
  2. Fix Content Staging Manifest - The DNN manifest for the Enterprise Content Staging module may not uninstall gracefully if you've modified various sections of your web.config file. If you have, you will need to adjust the Manifest field for this package to consider the changes.
  3. Uninstall Modules - From the Extensions screen you can now uninstall each EVOQ module.
  4. Uninstall Providers - From the Extensions screen you can now uninstall the EVOQ providers.
  5. Uninstall Libraries - From the Extensions screen you can now uninstall the EVOQ libraries.
  6. Downgrade HTML Pro Module - The HTML Pro module is a modification to the HTML module.  You can reinstall the HTML module over top of the HTML Pro module and have it revert to the HTML module.  There are several differences that you must consider including additional files that you will need to manually remove and a few stored procedures that were missing or need to be modified.
  7. Remove Scheduled Tasks - Some of the EVOQ versions have specific scheduled tasks that are no longer relevant in the Platform version. Investigate your tasks and anything that is referencing the Professional, Enterprise, etc. version then you can remove it.
  8. Permissions - Some of the EVOQ versions have granular permissions that are not included within the Platform version. You may want to write a SQL script that can migrate the EVOQ permissions to the Platform permissions so that your users do not lose the ability to do specific tasks. Keep in mind, with the removal of granular permissions your users may now be able to more than they used to be able to.
  9. Admin and Host Pages - You will be left with some pages that previously had EVOQ extensions on them. You no longer need these and should go through the pages and remove anything that is orphaned.
  10. Analytics - If you were using the Google Analytics Pro module then you can now reinstall the Google Analytics module. To make it work you will also need to modify the SiteAnalytics file at the root of the application. The engine type will need to reference 'DotNetNuke.Services.Analytics.GoogleAnalyticsEngine, DotNetNuke' and the script template will need to be updated.
  11. Delete License Table - You can now drop the DNNProLicense table from your database
  12. Web.Config Cleanup - Ensure that there are no references left in the web.config to the EVOQ providers, etc. If there are then you can manually remove them.
  13. Test - Test, test and test some more!

That's it! Most the work is quite seamless but roadblocks will present themselves for extensions that may have bugs in there uninstall code or modifications that you've made to your site. In all instances, I was utilized the Log4Net logs and/or the Event Viewer to determine the extent of the error I was receiving and work through it.

If you need assistance planning or performing a DNN EVOQ to DNN Platform migration/downgrade, please feel free to reach out and we can discuss various consulting options.

Requirements & Disclaimer

The above steps are meant as a high-level guide to get you started and are not a complete step-by-step. Always perform the migration in a test environment and double check everything before proceeding.