WSS 3.0 Migrate root site to subsite in different web application
- For WSS 3.0, I need to migrate a root site with all sub sites from one web app at https://site.example.com to another web application on the same server as a sub site located at https://site2.example.com/site. The second site has other sub sites already up and running on it
I was planning on doing an export and then an import but wasn't sure if there were any gotchas that anyone might know of. I haven't found any similar situations that have been listed anywhere. Any insight would help.
Thanks,
Dana
Answers
- Dana,
A few things to think about are, just from my experience... Are the security and versions switches that can be added to import and export, so you move the user and rights associated with the site and versions of content in the site... IF you want those, check this link out.
http://technet.microsoft.com/en-us/library/cc262759.aspx
Kris Wagner, MCITP, MCTS Twitter @sharepointkris Blog: http://sharepointkris.com- Marked As Answer byLambert QinMSFT, ModeratorFriday, November 13, 2009 5:30 AM
Hi,
There is a few things that you should know before doing export/import :- "Stsadm -o export" exports the data using the object model;
- "stsadm -o import" imports the data using the object model and generates a new GUID for every objects such as sites, sub sites, lists and items;
- It does not copy any information related to workflows, task lists and recycle-bin;
- Do not forget to use includeusersecurity parameter in both export and import if you wish to preserve information relative to permissions and other properties such as documents authors;
Hope that help,
Mario
My blog (en français) : http://spcontext.wordpress.com/- Marked As Answer byLambert QinMSFT, ModeratorFriday, November 13, 2009 5:30 AM
as was mentioned you can use STSADM export/import but move workflows and update navigation links manually.
The biggest challenge is if you have Publishing site and want to move subsite on the root. Publishing site doesn't support it natevely, so you need to use GL extentions for this
http://stsadm.blogspot.com/2007/08/fix-publishing-pages-page-layout-url.html
SharePoint Tips & Tricks Portal | Microsoft MVP | My Blog | My twitter- Marked As Answer byLambert QinMSFT, ModeratorFriday, November 13, 2009 5:30 AM
All Replies
- Dana,
A few things to think about are, just from my experience... Are the security and versions switches that can be added to import and export, so you move the user and rights associated with the site and versions of content in the site... IF you want those, check this link out.
http://technet.microsoft.com/en-us/library/cc262759.aspx
Kris Wagner, MCITP, MCTS Twitter @sharepointkris Blog: http://sharepointkris.com- Marked As Answer byLambert QinMSFT, ModeratorFriday, November 13, 2009 5:30 AM
Hi,
There is a few things that you should know before doing export/import :- "Stsadm -o export" exports the data using the object model;
- "stsadm -o import" imports the data using the object model and generates a new GUID for every objects such as sites, sub sites, lists and items;
- It does not copy any information related to workflows, task lists and recycle-bin;
- Do not forget to use includeusersecurity parameter in both export and import if you wish to preserve information relative to permissions and other properties such as documents authors;
Hope that help,
Mario
My blog (en français) : http://spcontext.wordpress.com/- Marked As Answer byLambert QinMSFT, ModeratorFriday, November 13, 2009 5:30 AM
as was mentioned you can use STSADM export/import but move workflows and update navigation links manually.
The biggest challenge is if you have Publishing site and want to move subsite on the root. Publishing site doesn't support it natevely, so you need to use GL extentions for this
http://stsadm.blogspot.com/2007/08/fix-publishing-pages-page-layout-url.html
SharePoint Tips & Tricks Portal | Microsoft MVP | My Blog | My twitter- Marked As Answer byLambert QinMSFT, ModeratorFriday, November 13, 2009 5:30 AM
Thanks for the help, I ran into an issue when I migrated the web site. One of the security groups appears to only have included the first 100 users in the group when there should be 200 users. Does anyone know how to add them without manually going through and adding them?


