In some situations (very, very few - such as when moving content from a version 1.x or 2.x DotNetNuke site) , the only way to migrate content is to copy and paste content module by module from the old site to the new. Since a DotNetNuke site does not have actual pages (as a static, html site would have), it is not possible to copy and paste an entire "virtual" page at once. In addition to moving Html module contents (the easiest part), one would also have to re-upload image files and other file-based content. Then there is data such as user registration and profiles, forum posts, calendar events, etc. which cannot be migrated by copy and paste. In short, the copy and paste approach is a last resort.

Surely your current hosting provider must have some way of creating a backup of the site's database and providing it to you as a .bak or .zip file.

As for upgrading the DotNetNuke framework version of the old site first - I would not recommend doing so without being able to first make a backup of the filesystem and database - which you say is not possible.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

Richard, please be aware that a DoNetNuke site consists of all all files in file system and the database backup. Both connection strings in the web.config file provide the link to the database. For a move or clone of your site you need web site being setup with appropriate permissions for the ASP.Net account, all web site files be restored, the database being recreated from backup, dbowner permissions be granted and both connection strings modified accordingly. Your hosting expert should be able to setup the site accordingly, if he has some minimal experience with DNN and ASP.Net.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN