This documentation is archived and is not being maintained.

Working with a Content Migration Package

Windows SharePoint Services 3

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

The content migration package consists of a set of data files that contain all of the content included in an export operation plus a manifest file that describes the structure of the data.

Following is a brief description of the files that are included in a content migration package.

The ExportSettings.xml file is used to verify the logic of the export and ensure that what is expected in the export is included in the package.

<ExportSettings xmlns:xsi="" 
   xmlns:xsd="" SiteUrl="http://server1/" 
   FileLocation="c:\" BaseFileName="cmfile.cmp" IncludeSecurity="None" 
   IncludeVersions="LastMajor" ExportMethod="ExportAll" 
   <ExportObjects />

The Requirements.xml file contains information that is used as a preliminary check before any import takes place. This XML file verifies information such as the following:

  • The language is installed at the destination location (in this case, English). If the language is not installed at the destination, the import will fail.

  • Templates are installed at the destination location (in this case, the English version of the template with the ID of "STS#1"). If the templates are not installed at the destination, the import will fail.

  • Feature definitions are installed at the destination location. If the feature definitions are not installed at the destination, the import will fail.


    After an import is complete, all features are activated.

  • Web Parts are in the Safe Controls list at the destination location. If this is the case, the import continues. If the Web Parts are not in the Safe Controls list, a warning is issued and the import continues (unless HaltOnWarning is set to true).


    The object model does not verify that the Web Part DLLs are installed at the destination location. This is the responsibility of the administrator.

<Requirements xmlns="urn:deployment-requirements-schema">
   <Requirement Type="Language" Id="1033" Name="English" /> 
   <Requirement Type="WebTemplate" Id="STS#1" Name="1033" Data="English" /> 
   <Requirement Type="WebPart" 
      Id="Microsoft.SharePoint.dll v2.0.50727" 
      Name="2242cce6-491a-657a-c8ee-b10a2a993eda" /> 
   <Requirement Type="FeatureDefinition" 
      Name="ctypes" />

The RootObjectMap.xml file defines the top-level object to import, that is, the object with no parent.

In the following example there is only a single, top-level object. However, because all dependencies are included in an export, and dependencies can be outside of the Web site that is being exported, there can be more than one top-level object.

<RootObjects xmlns="urn:deployment-rootobjectmap-schema">
   <RootObject Id="d78135df-74f0-44ff-86d9-44cb5583f3a1" 
   Type="Web" ParentId="00000000-0000-0000-0000-000000000000" 
   WebUrl="/" Url="/" IsDependency="false" /> 

The SystemData.xml file contains all the default objects that are installed on a server that is extended with Windows SharePoint Services. This information is used primarily when the export/import operation is retaining GUIDs between the source and destination locations.

This file contains the schema version. If this does not match the version at the destination, the import fails.

<SystemData xmlns="urn:deployment-systemdata-schema">
<SchemaVersion Version="12.0.x.0" Build="12.0.0.xxxx" DatabaseVersion="xxxx" SiteVersion="0" /> 
<ManifestFile Name="Manifest.xml" /> 
<SystemObject Id="d78135df-74f0-44ff-86d9-44cb5583f3a1" Type="Web" Url="/" /> 
<SystemObject Id="6b4bd918-76a0-4b7e-8e09-4a0356543e42" Type="Folder" Url="/" />

The UserGroup.xml file contains all the user and group information from the source Web site. The following example does not include user and group information. To include user and group information, see the IncludeSecurity property.

<UserGroupMap xmlns="urn:deployment-usergroupmap-schema">
<User Id="1" Name="Terry Adams" Login="DOMAIN\username" Email="" IsDomainGroup="False" IsSiteAdmin="True" SystemId="ABCDEFGHIJKLMNOPoQRWfnhXm1/yzIdwDMoDAD==" IsDeleted="false" /> 
<Groups /> 

The Manifest.xml file is the primary file used by content migration. This file contains a collection of SPObject elements, which represent all of the exported content serialized into XML. Each SPObject element has an ObjectType attribute that indicates whether it is an SPWeb, SPFolder, SPFile, and so on.


You can have multiple Manifest.xml files, and can break them into any number of smaller files.

The Manifest.xml file is based on a linear relationship of the objects—all objects are at the same level and there is no containership reflected in the file. The file requires that an parent of an object precedes the object in the Manifest.xml file. For example, the entry for the SPFile seen below must be preceded in the Manifest.xml file by its parent SPFolder.

Each SPFileobject has a FileValue attribute, which refers to the DAT file containing the file contents. For example, in the following section of the Manifest.xml file you see an SPFileobject with a FileValue="00000001.dat", indicating the location of this data associated with this file.

<SPObject Id="a9a407c3-b155-41cc-9ca1-483525072f70" 
 ObjectType="SPFile" ParentId="bb480411-a95c-49cc-857e-a229194b99d6" 
 ParentWebId="d78135df-74f0-44ff-86d9-44cb5583f3a1" ParentWebUrl="/" 
  <File Url="_catalogs/lt/Forms/DispForm.aspx" 
   ParentWebId="d78135df-74f0-44ff-86d9-44cb5583f3a1" ParentWebUrl="/" 
   DirName="_catalogs/lt/Forms" Name="DispForm.aspx" 
   TimeCreated="2006-03-13T22:58:21" TimeLastModified="2006-03-13T22:58:21" 
   Version="1.0" IsGhosted="true" SetupPath="pages\form.aspx" 
   SetupPathVersion="3" SetupPathUser="1" FileValue="00000001.dat" />