Project Description

This tool is for moving content in *SharePoint 2007/2010/2013* - within an environment (or across similar envs). NOT an *upgrade* tool (e.g. 2010 to 2013).

The SharePoint Content Deployment Wizard provides the means to deploy the following content:

- site collections
- webs
- lists
- folders
- list items (including files/documents)

Content is exported using the Content Migration API as a .cmp file

The two screenshots which probably illustrate the concept of the tool best are:

Export selection screen:

CDW_ExportSelect.jpg

Import settings screen:

CDW_ImportSettings.jpg

N.B. The import operation overwrites your site data, always take a backup before importing.

As discussed above, this tool is NOT an upgrade tool. It can only be used to move/copy content within a SharePoint environment, or across multiple SharePoint environments which are at the same version. It cannot be used to move content from SP2007 to SP2010, or SP2010 to SP2013 etc

All versions of this tool work with SharePoint 2010 (and probably SP2013, but not tested) though you must edit a file (one time) to do this - see notes on version 2.8 page. Also note that v2.8 (or later) provides the best install experience on 2010

More details (taken from readme)

Usage notes
  • The tool must be installed locally on the server which hosts the site
  • Site URL - enter using format http://source.test.dev
  • Import web URL - enter using format http://target.com/targetweb
  • See 'permissions' note lower down

Import/Export characteristics

Since the Content Migration API is used, imports/exports have the following characteristics:
  • dependencies of selected content (e.g. referenced CSS files, master pages) are automatically included in the export - check 'Exclude dependencies of selected objects' to disable this
  • all required content types, columns etc. are automatically included in the export
  • in contrast to STSADM export, it is possible to retain GUIDs during deployment (where objects are not being reparented) - check 'Retain object IDs and locations' to enable this
  • no filesystem files (assemblies, SharePoint Solutions/Features etc.) are deployed - these must already be present on the target for the import to succeed)
  • the following content does not get captured by the Content Migration API - alerts, audit trail, change log history, recycle-bin items, workflow tasks/state

Reparenting

Reparenting of objects such as webs and lists is possible with the following usage on the import:

- enter the URL for the target web in the 'Import web URL' textbox
- ensure 'Retain object IDs and locations' is not checked

Permissions

The Content Migration API (PRIME) is used to package the content as a .cmp file, which can be copied to another
server for import. The application MUST be run from the SharePoint server(s), and MUST be run under the context
of an account which has appropriate SharePoint permissions - currently the way to specify an alternative user
to the currently-logged on user is by using the 'Run as..' feature in Windows 2003 (right-click on the .exe and
select 'Run as..').

See my blog post 'Introducing the SharePoint Content Deployment Wizard' for more screenshots and information - http://www.sharepointnutsandbolts.com/2007/12/introducing-sharepoint-content.html

Chris O'Brien
http://feeds.feedburner.com/ChrisObrien

Last edited Apr 17, 2013 at 3:34 PM by chrisobrien, version 28