Here is the scenario. You create a sub-site and start building all of your lists, libraries, and other content, only to find that this site should be a top-level or at some other location other than where it’s currently at.

Using SharePoint Powershell and the ‘stsadm’ command to perform an Export and Import this can easily be accomplished. Below are the steps I used to successfully move a sub-site from one level to another.

To Export a Site, at the PowerShell prompt type:

stsadm -o export -url http://sharepointsite/sub_site_01/sub_site_12 -filename c:\backup\sharepointsite.bak -includeusersecurity -versions 4 –nofilecompression

To Import a Site, at the PowerShell prompt type:

stsadm –o import –url http://sharepointsite/sub_site_12/ -filename c:\backup\sharepointsite.bak –includeusersecurity

Here is some additional information regarding the various options for the Import and Export commands.

stsadm.exe -o export
    -url <URL to be exported>
    -filename <export file name>
         [-overwrite]
    [-includeusersecurity]
    [-haltonwarning]
    [-haltonfatalerror]
    [-nologfile]
    [-versions <1-4>
        1 - Last major version for files and list items (default)
        2 - The current version, either the last major or the last minor
        3 - Last major and last minor version for files and list items
        4 - All versions for files and list items]
    [-cabsize <integer from 1-1024 megabytes>]
    [-quiet]

stsadm.exe -o import
    -url <URL to import to>
    -filename <import file name>
    [-includeusersecurity]
    [-haltonwarning]
    [-haltonfatalerror]
    [-nologfile]
    [-updateversions <1-4>
        1 - Add new versions to the current file (default)
        2 - Overwrite the file and all its versions (delete then insert)
        3 - Ignore the file
        4 - Terminate with conflicts]
    [-quiet]

When trying to accomplish particular tasks within SharePoint, there is a common sense way, and then there is the SharePoint way.

Say for instance you would like to have items within your list archived or retained when a certain date has been reached or an item has been marked as completed by a check box. To accomplish this by using the way SharePoint has laid out (http://technet.microsoft.com/en-us/library/cc262490.aspx), you’ll need to setup retention policies for either a content type or list/folder. Some of this setup has to be accomplished at the Site Collection level and/or at the List level. Long and be hold you then discover you do not have the appropriate permissions, or have to go through other individuals to get this setup. It becomes too much frustration for the task you’re trying to complete. I can understand the purpose behind the design, but sometimes you need something simple and straight forward.

Yes, you could setup a List View to hide the old or completed items, but they begin to take up space in your list and eventually impact it’s performance.

Lets Keep it Simple

I’m going to outline a simple way to archive using a designer workflow. Continue reading →