sharepoint migration using metalogix

Sriram Bala

SHarepoint practice

Table of Contents

1. MOSS 2007/SP 2010 POC Activity................................................................21.1 Planned POC Migration Activities................................................................................2

1.2 Actual POC Migration Activities....................................................................................2

1.2.1 Metalogix Content Matrix Installation..........................................................................2

1.2.2 Configuring Content Matrix – Jobs for Migration.........................................................8

1.2.3 Establishing Connections............................................................................................9

1.2.4 Observations while using Metalogix..........................................................................26

1.2.5 SP 2010 to SP 2013 Migration using Metalogix – Content Matrix (Trial)...................26

1.2.5.1 Few Observations during SP 2010 migration.........................................................30

1.2.6 MOSS 2007 to SP 2013 Migration using Metalogix – Content Matrix (Trial).............30

1.2.6.1 Few Observations during MOSS Migration............................................................35

1.2.7 Analysis on the above Observations (Using Metalogix)............................................36

1. MOSS 2007/SP 2010 POC Activity

1.1 Planned POC Migration ActivitiesFor both MOSS 2007/SP 2010 migration to SP 2013

1. Using Migration Tool - Metalogix Content Matrix – SharePoint Edition2. Database Backup - Restore

Below are mandatory for carrying out the POC

Access to the POC Servers where SP 2013 is installed Access to the POC Servers where Metalogix Content Matrix 6.1 – SharePoint Edition is installed Access to the Legacy Systems (MOSS 2007, SP 2010 Environments) MOSS 2007/SP 2010 SQL Database Backup (.bak) is initially required as we cannot directly access

the production Server with SharePoint 2010 installation is required for restoring the MOSS 2007 SQL Database

Backup (.bak)

1.2 Actual POC Migration Activities

Actual POC Migration involved only the first approach, migration using Migration Tool - Metalogix Content Matrix – SharePoint Edition.

1.2.1 Metalogix Content Matrix Installation

Below are the steps for installing Metalogix Content Matrix 6.1

Click on the Metalogix Content Matrix Setup file from the respective file location

Click on the Next button to proceed with the Metalogix Content Matrix Installation.

Accept the License Agreement terms and click next.

Select the Setup Type Complete or Custom. Installation starts if Complete is selected

Check the required features for the custom setup and click Install

Installation starts and can be interrupted any-time by clicking cancel

Click Finish once the Installation Wizards completes successfully

1.2.2 Configuring Content Matrix – Jobs for Migration

Once Metalogix is installed, we need to open the respective Content Matrix Console from the Start Menu, in our case it will be Content Matrix Console – SharePoint Edition

Content Matrix Console – SharePoint Edition – 6.1.2.1 Window opens

The first step once we open the console will be to establish the connection to the Source and the Target applications. This connection can be established in 3 ways:

1. Connect to SharePoint Database2. Connect to SharePoint3. Connect to SharePoint - Read Only

1.2.3 Establishing Connections

Connect to SharePoint DatabaseUsing this option we can establish the connection to the SharePoint Database and migrate the database from the source (MOSS2007, SP 2010) to the target (SP 2010, SP 2013) provided the user has the admin privilege to that particular Database. Source Database can be either from local machine or network.

Connect to SharePoint Using this option we can establish the connection to the SharePoint Site/WebApp/Farm and migrate the content from the source (MOSS2007, SP 2010) to the target (SP 2010, SP 2013) provided the user has the respective privilege to that particular Application.

Provide the SharePoint root site link and choose the Target Type as site

Choose Auto Detect in Connection Type dropdown

Choose Auto Detect in Authentication Type dropdown

Enable Proxy if required [In our case not required]

Add Installed certificate if required [In our case not required]

Once the connections to the source and the target are established, expand the source application in the left pane and the Target Application in the right Pane

Sites or Sub Sites can be copied from the source and pasted to the target application

Once we select the Paste Site option the Configure dialog opens

If the user does not have the proper privilege to the source then the UNAUTHORISED error occurs

In such case the user can create the sites using the tool and migrate the associated lists provided the user is granted with at least Contribute Permission

Create a new site based on a template

Right click on the List from the source site and select Copy List.

Select the target site and Paste List as shown below.

Configure various copying options based on our requirement as shown below and save the configuration which inturn creates a job for migration

On Saving the configuration the Migration Job is created and is listed in the Jobs list.

Select the migration job that we created and click on Run Job.

Click Yes to confirm the job to be done in the confirm box.

In case of trial version it displays the information that only 50% of the content will be migrated

Once the migration is complete job reports will be shown as shown in the below screen. This will also indicate the errors if anything occurred.

The Site Structure in the Migration Tool - Metalogix Content Matrix – SharePoint Edition post migration

Below are the comparison of the content in the SharePoint sites before and after migration

1.2.4 Observations while using Metalogix

Metalogix Content Matrix needs to be installed on top of .NET Framework 4.0, so as to establish the connection to any version of the SharePoint URL in any server. If not connection to SP 2013 fails.

1.2.5 SP 2010 to SP 2013 Migration using Metalogix – Content Matrix (Trial)

Created several Jobs in Metalogix Content Matrix Console - SharePoint Edition - 6.1.2.1 and tried to migrate the Sites, Lists, Libraries, Folders, Metadata, and Permissions etc., from SP 2010 Site Collection to SP 2013 Site Collection

Source SP 2010 Site Collection: https://sharepoint/

Target SP 2013 Site Collection: http://alphclspapp01:53160/

Source SP 2010 and Target SP 2013 Content Structure – Metalogix Content Matrix

Source Content - SP 2010 (Shared Documents)

Target Content – SP 2013 (Shared Documents)

Source Content - SP 2010 (Site Contents)

Target Content – SP 2013 (Site Contents)

1.2.5.1 Few Observations during SP 2010 migration

Moved 50% of data from source to target.

Able to run the created job to migrate the list, libraries, pages with items, permissions and other metadata. Based on trial version limitation 50% content moved from source to target server.

Faced issue when pasting the sites to target server.[UNAUTHORISED] Folders within list/library were not migrated User Permissions and Groups were not migrated completely

1.2.6 MOSS 2007 to SP 2013 Migration using Metalogix – Content Matrix (Trial)

Created several Jobs in Metalogix Content Matrix Console - SharePoint Edition - 6.1.2.1 and tried to migrate the Sites, Lists, Libraries, Folders, Metadata, and Permissions etc., from MOSS 2007 Site to SP 2013 Site Collection.

Source MOSS 2007 Site: https://aibmoss/mossgov/

Target SP 2013 Site Collection: http://alphclspapp01:53160/

Source MOSS 2007 and Target SP 2013 Content Structure – Metalogix Content Matrix

Source Content – MOSS 2007 (Governance Policies)

Target Content - SP 2013 (Governance Policies)

Source Content – MOSS 2007 (Site Contents)

Target Content – SP 2013 (Site Contents)

1.2.6.1 Few Observations during MOSS Migration

Moved 50% of data from source to target.

Unable to connect to MOSS 2007 Site when granted Read-Only access – [UNAUTHORISED] Able to connect to the server and migrate contents only when granted Contribute access Able to run the created job to migrate the list, libraries, pages with items, permissions and other

metadata. Based on trial version limitation 50% content moved from source to target server. Faced issue when pasting the sites to the target server.[UNAUTHORISED]

Folders within list/library were not migrated User Permissions/Groups were missing after migration

1.2.7 Analysis on the above Observations (Using Metalogix)

Users need to be migrated first before we proceed with the content migration, so that the user permissions with groups are migrated

Read-only access is not sufficient enough for migrating the content completely; admin access is required for complete migration.

Sites/sub sites and folders are getting migrated to SP 2013 when granted with Full Control access for MOSS 2007 web application