Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...Import non-DNN pages into new DNN installationImport non-DNN pages into new DNN installation
Previous
 
Next
New Post
1/20/2016 2:50 PM
 
Hi. I am trying to figure out the best way to migrate data from my custom built system. Any help is very much appreciated. I am a new DNN (Evoq) customer. I have an existing website with a custom built CMS behind it. I need to migrate some legacy data from my custom built site over to my new DNN (Evoq) installation. Specifically, I have approx. 10,000 pages which exist in custom non-DNN Sql Server data schema. We think of these items as "documents". I know this won't be the case in the DNN schema. Our documents have various relationships with other items such as tags and categories.  Can anyone suggest a way to go about migrating this custom data into DNN?  Thank you.
 
New Post
1/20/2016 7:50 PM
 

Unfortunately there isn't a really good, easy to use solution for this that I know of. 

Depending on the Content itself, it might be imported into DNN as Pages with Modules on them to fill in the content (content actually imported into the modules themselves, but the title and URL being defined by the page itself). It could also be imported into XML templates that DNN can "import" to create pages in an Instance of DNN. 

Neither of those two approaches are easy to do without a thorough understanding of DNN and lots of testing.

You might take a different approach, and import all the Content into a single module, which will provide those "documents" and a way to navigate through the documents. Something like the 2sxc Content module, in which you items become different "cotennttypes".

Is most of the content simply text/html, or are there images and PDF/DOCX files and such that need to be accounted for?


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...Import non-DNN pages into new DNN installationImport non-DNN pages into new DNN installation


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out