SharePoint Content Deployment Wizard

Updated Wiki: Home

chrisobrien — Wed, 17 Apr 2013 14:34:12 GMT

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:

Import settings screen:

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

Updated Wiki: Home

chrisobrien — Wed, 17 Apr 2013 14:19:14 GMT

Project Description

NOTE: 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.

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

The SharePoint Content Deployment Wizard is a tool for *SharePoint 2007/2010* which provides the means to deploy the following content:

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

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:

Import settings screen:

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

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

Updated Wiki: Home

chrisobrien — Wed, 17 Apr 2013 14:18:40 GMT

Project Description

NOTE: 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.

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 (linked above). Also note that v2.8 (or later) provides the best install experience on 2010

The SharePoint Content Deployment Wizard is a tool for *SharePoint 2007/2010* which provides the means to deploy the following content:

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

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:

Import settings screen:

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

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

Updated Wiki: Home

chrisobrien — Wed, 17 Apr 2013 14:17:20 GMT

Project Description

NOTE: 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 at the same version.

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 (linked above). Also note that v2.8 (or later) provides the best install experience on 2010

The SharePoint Content Deployment Wizard is a tool for *SharePoint 2007/2010* which provides the means to deploy the following content:

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

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:

Import settings screen:

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

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

New Post: List View Forms Broken After Wizard Import

geborx — Tue, 16 Apr 2013 08:49:53 GMT

Hi Ben,

sorry to disturb you.
I have the same error and I would like to know if you fixed the problem and how you did.
In my case, I have created a custom List and I have created my ListView to Edit the List Items. I have exported the list from SP2010 and I have imported it in SP2013: when I try to open the view,, to edit an Iem, I have the error.
Please, can you help me?

Thank you.

Created Issue: schema change from 2007 to 2010 [12884]

kknab — Mon, 15 Apr 2013 20:55:47 GMT

I'm getting an error on the import step with this tool (screenshot attached).

I exported from 2007, with no extra configurations of the tool. it all worked fine and produced 77 .cmp files in our directory, with zero errors/warnings in the log file.

I accessed those .cmp files from my 2010 machine and began the import process into my 2010 environment. I did remember to edit the config file, to uncomment the binding redirect node.

Is there some other step to ensuring that the schema is updated so that a 2007 export can be imported into a 2010 environment?

Thanks

Reviewed: 2.8 beta - installs on SP2010 (Apr 09, 2013)

gefane — Tue, 09 Apr 2013 18:38:29 GMT

Rated 5 Stars (out of 5) - Brilliant great work mate

New Post: SP2007 to SP2010 .... Error on Versioning

hmendezm — Mon, 18 Mar 2013 12:33:52 GMT

Hi guys!!

Do you have the solution for this problem??

Thx

New Post: Versioning Problems.

hmendezm — Mon, 18 Mar 2013 12:32:04 GMT

I am trying to export from SP 2007 to SP 2010 and I got the versioning error msg. Do you have solution for this?

Thanks for any help you can give me!!

New Post: Import complains of null Guid

janustoth — Mon, 18 Mar 2013 08:28:25 GMT

It appears that all user fields (multi and single) create this problem if they were created without the List="UserInfo" property. The import/export API probably treats them like normal lookup fields.

So if you have already created some fields without the property the solutions is:

Add the property to your caml for the field.
Push updates to that field down using the UI or code.

Commented Issue: An unexpected network error occurred. [12828]

kdmrramu — Fri, 08 Mar 2013 12:28:54 GMT

I am getting below error message while importing document library from one site collection to another site collection within same web application. please some one help me out!

[2/21/2013 8:07:51 AM] [ListItem] [xyz bnq V31.pdf] Error: An unexpected network error occurred.

[2/21/2013 8:07:51 AM] [ListItem] [xyz bnq V31.pdf] Debug: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
at Microsoft.SharePoint.CoordinatedStreamBuffer.SPCoordinatedFileStream.Write(Byte[] array, Int32 offset, Int32 count)
at Microsoft.SharePoint.SPFileStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at Microsoft.SharePoint.SPFile.CloneStreamToSPFileStream(SPWeb web, Stream stream, Int64 bytesToCopy)
at Microsoft.SharePoint.Deployment.FileSerializer.UploadFileData(Object fileOrListItem, SPLoggerObject loggerObject, SPWeb web, Guid fileId, String fileUrl, FileInfo fileInfo, SPUser author, SPUser editor, String checkinComment, DateTime timeCreated, DateTime timeLastModified, MetaInfoHandler metaInfo, Int32 iVersion, Boolean isFirstVersion, Int32 listItemId, String listInternalName, ImportObjectManager objectManager)
at Microsoft.SharePoint.Deployment.FileSerializer.UploadFileData(Object fileOrListItem, SPLoggerObject loggerObject, SPWeb web, Guid id, String fileUrl, Boolean fileExistsInDb, SerializationInfoHelper infoHelper, SerializationInfoHelper infoHelperListitem, MetaInfoHandler metaInfo, StreamingContext context)
at Microsoft.SharePoint.Deployment.FileSerializer.CreateOrUpdateFile(Object fileOrListItem, SPLoggerObject loggerObject, SPWeb web, Guid id, String& fileUrl, Boolean fileExistsInDb, Boolean isFirstVersion, Boolean hasWebParts, SerializationInfoHelper infoHelper, SerializationInfoHelper infoHelperListitem, StreamingContext context)
at Microsoft.SharePoint.Deployment.FileSerializer.CreateOrUpdateFileAndAssocData(Object fileOrListItem, SPLoggerObject loggerObject, SPWeb web, Guid id, String& fileUrl, Boolean fileExistsInDb, SerializationInfoHelper infoHelper, SerializationInfoHelper infoHelperListitem, StreamingContext context, ISurrogateSelector selector)
at Microsoft.SharePoint.Deployment.ListItemSerializer.AddOrUpdateDoclibItem(SerializationInfoHelper infoHelper, SPListItem& listItem, SPLoggerObject loggerObject, SPWeb web, Guid newId, String& listItemServerRelativeUrl, Boolean bIsPublish, Boolean exists, StreamingContext context, ISurrogateSelector selector)
at Microsoft.SharePoint.Deployment.ListItemSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)

How can i fix this issue.
Comments: ** Comment from web user: kdmrramu **

Hi ,

Any one have solution for this!!! , Please share with me if you have any solution for this.

Commented Issue: An unexpected network error occurred. [12828]

kdmrramu — Fri, 22 Feb 2013 06:16:55 GMT

Hi,
I hope you’re doing well, Thanks for your comments

My current environment details are as below:
SharePoint 2010 SP1
June 2012 CU updated
1 SharePoint server and 1-database server
Export file location is on same sharepoint server on D drive.

We have one web application (http://xyz.tech.com) with 2 site collections, under one site collection (http://xyz.tech.com/ss/default.aspx) we have a sub site (http://xyz.tech.com/ss/department) which is size of 64 GB. When I exported sub site using PowerShell successfully but when I am trying to import this sub site to another site collection (http://xyz.tech.com/sites/process) receiving the above error.
We can only able to import 38 GB out of 64 GB.

Thanks in advance for your help.

Commented Issue: error importing from 2007 to 2010 [12489]

PerrySharePoint — Thu, 21 Feb 2013 21:42:19 GMT

Comments: ** Comment from web user: PerrySharePoint **

A good bug report should probably start with basic info about your environment (e.g, what version of SharePoint), and should always say what version of the software you're using.

Commented Issue: xsl stylesheet is not exported [12816]

PerrySharePoint — Thu, 21 Feb 2013 21:41:12 GMT

Comments: ** Comment from web user: PerrySharePoint **

A good bug report should probably start with basic info about your environment (e.g, what version of SharePoint), and should always say what version of the software you're using.

Commented Issue: An unexpected network error occurred. [12828]

PerrySharePoint — Thu, 21 Feb 2013 21:40:32 GMT

Comments: ** Comment from web user: PerrySharePoint **

A good bug report should probably start with basic info about your environment (e.g, what version of SharePoint), and should always say what version of the software you're using.

Created Issue: An unexpected network error occurred. [12828]

kdmrramu — Thu, 21 Feb 2013 13:23:28 GMT

Created Issue: xsl stylesheet is not exported [12816]

AGuyCalledGerald — Tue, 12 Feb 2013 17:34:55 GMT

I have built an external list in Sharepoint Designer. I formatted some fields using formula. This creates an xsl stylesheet in the page code. But the stylesheet is not exported with the wizard.

Created Issue: Custom form of list not found [12815]

AGuyCalledGerald — Tue, 12 Feb 2013 10:34:41 GMT

I have built an external list with sharepoint designer and added a second, custom Display Form for formatting reasons. This works fine in the original list. However, after the export/import with the wizard, I get an error when I try to start the custom form: "File not found". The first, original form which is automatically added to the list still works well.

New Post: SP2007 to SP2010 .... Error on Versioning

roastchicken — Mon, 11 Feb 2013 11:30:20 GMT

Hi

I'm also having the same problem. Did you manages to find a solution?

Thanks

Reviewed: 2.8 beta - installs on SP2010 (Jan 30, 2013)

jsnl85 — Wed, 30 Jan 2013 15:45:16 GMT

Rated 5 Stars (out of 5) - One of the best OpenSource Tools out there! Congrats for this! It's extremely useful