Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I have a site collection with a dozen or so document libraries in it (total size about 300GB's). The goal is to move each of these document libraries into it's own site collection (and content database).

I've seen posts like Exporting sites to a new content database (talks about moving whole sites) and Restructuring a Very Large Document Library (restructuring a large document library). I found an article online that specifically adresses this issue, http://pravahaminfo.blogspot.com/2011/05/how-to-move-document-library-from-one.html, but the method of exporting the list as a template with content and then importing it on the new site only works up to 10 MB's (500 Mb's max if you change it) and my smallest document library is about 5GB's.

Right now I am considering exporting the list as a template WITHOUT content, importing it, and then using code to move the files. I looked into using Explorer view to move the files but the document libraries I have with over 20,000 folders in the root won't open in Explorer view...

Suggestions on how I should move forward? I'm currently looking for a method that will work in 2007 BUT we are migrating to 2010 in the near future so if the time/headache savings are big enough I will wait.

share|improve this question
    
Any update on this? Is the best method to export somehow in v3 and import into v4, or is it better to upgrade the db to v4 and then use Export-SPWeb? I'm doing the same thing but ultimately going from v3 to v5, but I have a v4 environment at my disposal as well. Does that change the equation at all? –  thanby May 30 '13 at 2:43
add comment

1 Answer 1

I am going to provide an answer that will work in 2010. I will need to depend on others who are more versed in MOSS for that; however, I believe there is a similar stsadm command for the Powershell I will provide below.

The Export-SPWeb command is able to be defined for a site, list or library. I have used this extensively to move a troubling list from production to dev/test so that I may work on a specific criteria.

Here is the TechNet Article

An example:

Add-PSSnapin Microsoft.SharePoint.PowerShell
$URL = "http://iwanttotest.com/MyManagedPath/SiteName"
$DocLibrary = "http://iwanttotest.com/apps/site/DocLibraryName"
Export-SPWeb -Identity $URL -Path C:\SiteBackup.cmp -ItemURL $DocLibrary -IncludeUserSecurity -IncludeVersions

Please note this must be executed on a server within the SP Farm so you may add the Powershell snapin.

share|improve this answer
    
Exporting lists and libraries is was added in SP2010 and is not possible with the export stsadm operation in 2007. Upgrading first to 2010 and then exporting is a good solution provided Patricker can wait. SharePoint upgrades are also tricky in their own right. –  shufler Nov 14 '11 at 21:54
    
Thanks for the assist shufler. I found the upgrade to 2010 to be fairly good, but I scripted every piece with Powershell and ran the upgrade and revert likely 100 times before the live execution. –  websch01ar Nov 15 '11 at 12:10
    
I did some more research, what about using Microsoft.SharePoint.Deployment.SPExport / SPImport? This appears to be able handle SPList objects. –  Peter Nov 15 '11 at 15:25
    
My assumption is stsadm wraps SPExport. Obviously that doesn't mean SPExport can't handle SPLists, but I'm not seeing anything other than SPSites mentioned in the MSDN for either v3 or v4. –  shufler Nov 16 '11 at 0:11
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.