Hi, I have created 2 child portals from my 2 DNN (5.1 & 4.9.3) sites running as 2 sub-domains for our demo; and now I need to move/copy these temporary sites into two new hosting web folders and working in 2 individual parent portals as new installations (production sites) for two new domain names.

I am wondering that is it possible could be done, just like the same procedure that I have done before on moving the entire DNN installation in the web folder at one hosting provider to another location of the new provider? And if that so, then how should I backup / restore the SQL db for these 2 particular child portals.

I know I did not do it right in the beginning, but is there any way to avoid redo it from scratch. Thank you for help.

This may be a little late for you, but when I work on a development site, I export it to the production site using "portal templates".  You simply go to Host->Portals and choose "export portal template".  You'll go to a new page where you give the template a name, description, and you should check the box for "export content".  Checking that box for "export content" will take not just the modules but their content ie text as well.  The only thing I've had problems with are occasionally images that are in html/text modules don't get their new portal number assigned properly when adding a new portal using the exported template.  Also, blogs are not included in the portal export.  But, the portal templates sure make things a lot easier by getting all the text and the pages and the structure and menu heirarchy, skin and container choices, etc all right there and duplicated from the production site.  The portal templates get stored in different areas from dnn4 to dnn5.1.  They used to go into the /portals/_default/ directory up through dnn 5.0.1.  With 5.1.1 I found they now go into the /install/ directory in the respective portal template directory.  Anyway, try this method if you weren't able to just do a database backup and file backup to move the installation.  If you are changing the portal from child to parent and moving to it's own dnn installation (not the same portal structure as your development server), then the portal template export is probably the only way to go.

JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

Hello:

I have successfully used this method as well, i.e. exporting then importing to a new site, or more recently, to the DotNetNuke 5 upgrade in which I performed a fresh install rather than upgrading.

Also, if you have user accounts for your portal and wish to keep them, you may want to take a look at BulkReg Import/Export at Snowcovered.

Good luck!

John