Regular readers might have spotted I’ve been slightly quieter than usual over the past few weeks – actually I’ve not been slacking, but working on a tool which you might find useful from time to time. As I’ve discussed in numerous posts, deployment of SharePoint artifacts is something that’s perhaps more complex than it should be, and the standard tools provided don’t always simplify this picture. Personally, over my past few MOSS projects, there have been several times when I’ve thought:
- I just need to move this document library from A to B
- I just need to move these selected files (e.g. master page, page layouts, CSS etc.) from A to B
- I just need to move this web from A to B
- I just need to move this site collection from A to B
- I just need to move these 20 list items from A to B
If only there was an easy way! CMS 2002 users may remember the SDO export mechanism which allowed you to use a treeview to select exactly which content you wished to move, but unfortunately there’s no similar tool for MOSS. Sure, we have Content Deployment and STSADM export etc., but the lowest level of granularity is a web, and if you don’t want to overwrite the whole thing neither option can be used. The only other option is to write code which uses the Content Migration API. This is fine for projects which have the appropriate development skills and time, but otherwise things can be tricky.
Enter the SharePoint Content Deployment Wizard.
The tool provides a wizard-like approach to deploying content between SharePoint sites. The selected content is exported using the Content Migration API (PRIME), giving a .cmp file (Content Migration Package) which can be copied to other servers.
Since pictures are often more useful than words, let’s look at using the tool. Click to enlarge any of the images below:
Welcome screen (click any image to enlarge):
Select action (import or export) and provide site URL:
For export, use the treeview to select which content you wish to deploy. On container objects such as webs, there are options about whether descendent objects should be included:
Browse to the .cmp file we exported in the previous steps, and select options around security, versions and, importantly for some scenarios, whether object IDs should be retained:
The details are shown back for confirmation, and when ‘Finish’ is clicked the import will begin:
And that’s the gist of it. This is the first beta of the tool and I’m sure there will be issues. Regardless, when using any tool which makes this kind of change to your data you should always take a backup before performing the import. Depending on what you’re doing, it could be difficult to revert back to the previous state otherwise.
Some other notes:
- the tool must be installed locally on the server which hosts the site
- not all features of the Content Migration API are supported by the tool
- the next beta (mid-December) will properly support large sites – currently the site bind operation can be slow for large sites since the treeview is built in one operation
- it must be run under an account which has the appropriate permissions to the SharePoint site – use the Windows ‘Run as..’ feature to do this if necessary (shown below in the image below- right-click on the .exe and select ‘Run as..’)