RE: stsadm import top level site into site collection As part of a Proof of Concept we migrated an SPS 2003 top level site to a new MOSS web application site (on a different port.. not 80). The new site appears to have everything in working order. However, we actually need that site to fall under a site collection on the main site (port 80), but apparently there is no way to do that directly through stsadm addcontentdb. So we are attempting to import the site 2007 to 2007 from the top level web application to a new site collection. However, we encounter these problems. Some web parts don't come over stating they are not in the safe list. Sites under the top level site don't migrate.. keeping in mind these sites are under /sites directory so they would have to end up under /sites/NewSite/sites and perhaps that is the problem. I attempted to export/import these sites seperately and throw them in at the same level as the new site collection (not ideal but an experiment), but I get an error that template MPS#3 vs STS#0 are not consistent. Thanks for any help or information.

Have you tried the "backup" & "restore" options using stsadm?Generally when I have to move a complete site collection from one web app to another web app, this (backup & restore) seems to be the cleanest one... I dont believe this method will cure the webpart "safe list issue you are having - the web.config changes has to be made for the new web app.

Well I know you can't restore v2 into v3 for sure. Are you saying you've restored a top level site into a site collection? So you might have ended with directory paths like:./sites/Mysite/sites/MysubSite ?

JCNET, Are you trying to make the top level site a subsite of a site collection, or are you just trying to relocate it (as a new site collection)? If you are trying to "demote" the top level site, backup and restore aren't going to work and you are going to be forced to try and use export and import (which sucks and work spotty at best). However, if you are just trying to relocate it to a new site collection, while keeping it as that collection's root, the easiest way would be to migrate the database (to upgrade it), then just backup and restore the collection to the exact location you want it. As for the web part errors, have you checked the web part maintenance page for them? http://sitecollection/<pagewitherror>.aspx?contents=1

Hi, When you use STSADM export import the templates of source site and destination sites must be same. If you are importing it somewhere under a already created site collection then at the destination do not create any site while running the import command it will automatically create it. If you are going to do thsi at the top level then I would suggest you to create a site using STSADM createsite without any parameter for template. This will create a blank site and you can import in that without any issues. I hope this will help you out. Thanks, Rahul Rashu

Take a look at http://social.technet.microsoft.com/forums/en-us/sharepointgeneral/thread/EF5BE73B-306A-4E5C-9820-8A526929B237 Regards,