Steps for Converting Evoq to DNN Community
- Review your current site(s) to determine which modules and extensions from Evoq are in use. You will not be able to use these modules on DNN.
- Develop a plan for switching these modules to a new open-source version.
- If your using workflows, develop a new system to replace workflow approvals.
- Create a new back-up of the Evoq site's file system and database.
- Create a duplicate local development site.
- Install any needed DNN modules and convert the content from the Evoq module ot the new DNN module.
- Convert the entire site so that no content is in Evoq modules.
- QA (review) the website for any issues.
- Fix any issues, document the fix and retest.
- Upon a clear QA, the live site should go under a content freeze.
- Create a fresh back-up again, restore to the test site and repeat the steps.
- All teams perform a QA -- IT, marketing, leadership, etc.
- Fix any issues.
- Upon a clear QA, push/deploy the test sites to the production servers effectively overlaying the old Evoq site.
- Again, all teams should do a QA to ensure a successful deployment.
- Fix any remaining issues if any.
As DNN experts, Engage has performed this conversion for many clients and we can do the same for you. Pricing will vary depending on the simplicity and/or complexity of your site configuartion and module deployment. Please use the form below to contact us for a FREE evaluation.
The most important piece to keep in mind is that DNN requires the Evoq license renewal to be in place 60 days before your license actually expires. Therefore, diligent planning is needed to ensure a successful transition before the expiration. It is recommendated that you allow yourself at least 120 days to begin implementing your migration.