How Bamboo Content Migration for SharePoint Works

Bamboo Content Migration for SharePoint is an application that allows users to move content between SharePoint environments. Use the application to migrate content from sites within the same SharePoint version. For example, you can migrate content from a SharePoint 2007 environment (WSS 3.0 and MOSS 2007) to another SharePoint 2007 environment (WSS 3.0 and MOSS 2007). Or, migrate content from a SharePoint 2010 environment (Server 2010 and Foundation 2010) to another SharePoint 2010 environment (Server 2010 and Foundation 2010). You can migrate content from full site collections, or you can migrate specific subsites within a site collection.

Note: You cannot migrate content from a higher SharePoint edition to a lower SharePoint edition. For example, you cannot migrate content from SharePoint Server 2010 to SharePoint Foundation 2010. You cannot migrate content from MOSS 2007 Enterprise to MOSS 2007 Standard. See this table to compare SharePoint editions.

Installing Bamboo Content Migration for SharePoint 

If you are installing Bamboo Content Migration for SharePoint on Windows Server 2008, disable Admin Approval Mode in the UAC policy or turn off UAC on any SharePoint server where the product will be installed. See this Microsoft TechNet article for more information.

1) Download the Bamboo Content Migration for SharePoint from Bamboo Labs and save it to a local folder on your SharePoint server.

2) Double-click the product EXE file. The contents of the EXE are extracted into the same folder where the product EXE resides. Double-click the Setup.bat file at the root of the extraction folder to run the Setup program. You can also use the .msi located in the msi folder to install the application.

3) From the Setup program, select the Bamboo Content Migration for SharePoint component and click Install.

• Click Next, then browse to the location where you want to install the application. Choose who can use the application. Then click Next.
• Click Next again. When the application has been installed, click Close.

 

Note: Navigate to Control Panel > Add or Remove Programs (or Control Panel > Programs and Features for Windows Server 2008) to view the application in the list of programs or to remove it.

Using Bamboo Content Migration for SharePoint

To export data:

1) Double-click the Bamboo Content Migration for SharePoint desktop icon to run the program. Click Next.

2) Select your Web application from the drop-down list, then choose the desired site collection that you want to export (or choose the site collection that contains the subsite that you want to export). Select the option to export data. Click Next

3) Select the source site and click Next.

4) Browse to the location where you want to save the export file (.cmp). Enter a name for the file, then click Next.

5) Confirm the export settings and click Export to begin the exporting process. Wait while the site collection or site is exported. This step could take a few hours if the content being migrated contains several sites and/or lists.

6) Click Finish to review the migration summary log. Click Close.

To import data:

1) In SharePoint, create the import/destination location where you want to import the content. Use the tables below to determine how to create the import/destination location and which site template to use:

SharePoint 2007
Scenario	Description	Requirement
1	Source Site: Team Site at the root web or site collection Export Site: Team Site Example: Source Site: TeamA Export Site Collection: /TeamA	Preparation: Create the import/destination location at the root web or site collection using only a blank* site template. Example: Destination Site: TeamB Destination Import Site Collection: /TeamB
2	Source Site: PM Central at the root web or site collection Export Site: PM Central Site Example: Source Site: PMC Export Site Collection: /PMC	Preparation: Create the import/destination location at the root web or site collection using only a blank* site template. Example: Destination Site: NewPMC Destination Import Site Collection Only: /NewPMC
3	Source Site: Team Site at the root web or site collection Export Site: Another Team Site, which is a subsite of the Team Site Example: Source Site: TeamA Export Subsite Only: /TeamA/TeamA1	Preparation: Create the import/destination location at the root web or site collection using a blank site template or a team site template. Example: Destination Site: TeamB Destination Import Subsite Only: /TeamB/TeamA1
4	Source Site: Team Site at the root web or site collection Export Site: PM Central Site, which is a subsite of the Team Site Example: Source Site: TeamA Export Subsite Only: /TeamA/PMC	Preparation: Create the import/destination location at the root web or site collection using a blank site template or a team site template. Example: Destination Site: TeamB Destination Import Subsite Only: /TeamB/PMC
5	Source Site: Team Site at the root web or site collection. This team site contains another team site as a subsite. Export Site: Team Site Example: Source Site: TeamA Export Site Collection: /TeamA/TeamA1	Preparation: Create the import/destination location at the root web or site collection using only a blank* site template. Example: Destination Site: TeamB Destination Import Site Collection: /TeamB/TeamA1
6	Source Site: Team Site at the root web or site collection. This team site contains a PM Central site as a subsite. Export Site: Team Site Example: Source Site: TeamA Export Site Collection: /TeamA/PMC	Preparation: Create the import/destination location at the root web or site collection using only a blank* site template. Example: Destination Site: TeamB Destination Import Site Collection: /TeamB/PMC

 

SharePoint 2010
Scenario	Description	Requirement
7	Source Site: Team Site at the root web or site collection Export Site: Team Site Example: Source Site: TeamA Export Site Collection: /TeamA	Preparation: Create the import/destination location at the root web or site collection only via command line** to avoid creating a blank site*. stsadm.exe -o createsite -url http://servername/sites/sitename -ownerlogin domainuser -owneremail email address Example: Destination Site: TeamB Destination Import Site Collection: /TeamB
8	Source Site: PM Central at the root web or site collection, i.e. users use a PM Central portfolio site template to create the site collection Export Site: PM Central Site Example: Source Site: PMC Export Site Collection: /PMC	Preparation: Create the import/destination location at the root web or site collection only via command line** to avoid creating a blank site*. stsadm.exe -o createsite -url http://servername/sites/sitename -ownerlogin domainuser -owneremail email address Example: Destination Site: NewPMC Destination Import Site Collection: /NewPMC
9	Source Site: Team Site at the root web or site collection Export Site: Another Team Site, which is a subsite of the Team Site Example: Source Site: TeamA Export Subsite Only: /TeamA/TeamA1	Preparation: Create the import/destination location at the root web or site collection using a blank site template or a team site template. Example: Destination Site: TeamB Destination Import Subsite Only: /TeamB/TeamA1
10	Source Site: Team Site at the root web or site collection Export Site: PM Central Site, which is a subsite of the Team Site Example: Source Site: TeamA Export Subsite Only: /TeamA/PMC	Preparation: Create the import/destination location at the root web or site collection using a blank site template or a team site template. Example: Destination Site: TeamB Destination Import Subsite Only: /TeamB/PMC
11	Source Site: Team Site at the root web or site collection. This team site contains another team site as a subsite. Export Site: Team Site Example: Source Site: TeamA Export Site: /TeamA/TeamA1	Preparation: Create the import/destination location at the root web or site collection only via command line** to avoid creating a blank site*. stsadm.exe -o createsite -url http://servername/sites/sitename -ownerlogin domainuser -owneremail email address Example: Destination Site: TeamB Destination Import Site Collection: /TeamB/TeamA1
12	Source Site: Team Site at the root web or site collection. This team site contains a PM Central site as a subsite. Export Site: Team Site Example: Source Site: TeamA Export Site: /TeamA/PMC	Preparation: Create the import/destination location at the root web or site collection only via command line** to avoid creating a blank site*. stsadm.exe -o createsite -url http://servername/sites/sitename -ownerlogin domainuser -owneremail email address Example: Destination Site: TeamB Destination Import Site Collection: /TeamB/PMC

* Users will see the below error if the specific template for the import/destination location is not created as specified in Scenarios 2, 7, 8, 11 and 12.

** For SharePoint 2010: When the source site collection or root web is created using a team site template or a PM Central portfolio site template, users should not create the import/destination location site using a blank site except in Scenarios 9 and 10. Use the command line to create the import/destination site to avoid creating a site using the blank site template.

2) From the Bamboo Content Migration for SharePoint screen, choose your Web application and the site collection where you want to import the data. Select Import data content to the selected site collection, then click Next.

3) Browse to the location of the .cmp file. Click Next.

4) Make sure that the import settings are correct, then click Import. Wait while the import is completed. This could take awhile, depending on how much content is being imported.

5) Once the import is complete, click Finish to review the migration summary log. Click Close.

6) Navigate to the site collection or subsite that contains the imported data. You can now begin using the site collection or site as desired.

Using Bamboo Content Migration for SharePoint With PM Central

In order to successfully migrate PM Central using Bamboo Content Migration for SharePoint, make sure that you deploy the same version of PM Central on each site collection or site. For example, if you export content from a site using PM Central R2.0, you cannot import that content to a site using PM Central R1.8; the site must be using PM Central R2.0. As noted above, you can only migrate PM Central on the same SharePoint edition (SharePoint 2007 to SharePoint 2007 or SharePoint 2010 to SharePoint 2010).

Use the tables above to create the import/destination location site for PM Central sites.

Create the PM Central portfolio site using the same top-level site template for each site that you want to export and import. For example, if you create a PM Central site using the top-level custom template and then export that content, you need to create a PM Central site using the same template (top-level custom template) in order to import that content into the new site.

You must manually configure the department site’s filter settings after the import is complete:

1. In PM Central, go to the department site and select Central Actions > Lists > Project Filter Configuration List. Delete the item in the list.
2. From the portfolio site, select Central Actions > Lists > Department Site List. Edit the list item and edit the department site’s URL.
3. Return to the department site and go to the Settings tab. Select the Configuration Filter Web Part. Under Top Site URL, choose the desired portfolio site. Then configure the department site filter settings as desired. Click OK.

Bamboo is committed to making quality products, and we are always open to customer feedback. Please visit the Bamboo Content Migration for SharePoint forum to submit questions or comments. To download Bamboo Content Migration for SharePoint for free, visit Bamboo Labs.

---