Migration strategies and Step by Step – Migrating from MOSS 2007 to SharePoint 2010

I was reading a post from Apoorv Durga, about migration strategies on software development. It is a fantastic post. It is really true that many of the migration falls due to poor planning or sometime negligence towards the basic. SharePoint 2010 lunched yesterday and a very interesting product from Microsoft. Many organisations already considering migrate from the existing version of MOSS 2007 to SP 2010.

Organisations need to be very careful as most organizations do not undertake a migration effort with the rigor and discipline that they normally would for a software project. The result is often a failed migration. The following table maps the activities that you carry out in a software development phase with the activities that should be carried out for a migration project.

Activities in Software Development Activities in Migration
Requirement Analysis

Functional Specifications

  • Conduct Site/Content Inventory
    • Identify content types
    • Identify content that will not be migrated
    • Identify content parameters like type, owner, size, last modified, name, location, audience, importance and so forth
  • Analysis of the above
    • Frequency and complexity
    • Relationships
    • “Common-ness” between different content items
    • Taxonomy and Metadata assessment
Architecture Design

High Level Design

Low Level Design

  • Map content from source to destination
  • Map metadata from source to destination
  • Map users and roles
  • Identify gaps and strategies for them
  • Decide how much of manual and how much of automated migration can be done
  • Decide big bang Vs Incremental migration
  • Prototype or Proof-of-Concept
  • Design of import and export scripts
  • Test and QA plans


Unit Testing

  • Development of migration scripts and utilities
  • Unit Testing of these scripts and utilities
  • The actual migration (both automated and manual)
  • Post extraction refinement
System Testing

Integration Testing

Regression Testing

User Acceptance Testing

  • Test and QA different migration scenarios:
    • default values getting populated properly
    • data type mapping between source and destination
    • user and roles mapping
  • Performance testing of scripts
  • User Acceptance Testing
    • Content Quality
  • System roll over
  • System roll out
  • Post migration refinements

Depending on whether you use Waterfall, Iterative, RUP, Agile or some other methodology, there will be variations in the way you carry out some of the migration activities. However, the point is that you should treat content migration just like you would treat any other project and give it the respect it deserves.

Migrate MOSS 2007 to SharePoint Server 2010 (Taken from


Microsoft recently released SharePoint Server 2010. Microsoft claims that migrating from SharePoint 2007 to 2010 is easy and straightforward, however, migrating from SharePoint 2003 to 2007 the process was painful and difficult and there were several incompatible elements that had to be dealt with.

The sample intranet site presented in this article is hosted on Windows Server 2008 R2 64-bit (which is required for SharePoint 2010) with SQL 2008 Express 64-bit.

First, let’s look at the SharePoint 2007 site we migrate. For this demonstration I created a simple MOSS 2007 Enterprise environment based on the Collaboration template, which contains some generic web parts we’ll test on SharePoint 2010, Document Center and Search Center. I setup and double checked the search, because I wonder if the migrated SharePoint would be able to use the search database crawled in the previous, 2007 version of SharePoint. Search is an important issue for migrating SharePoint installations with large amount of data where a full crawl of the content may take weeks.

My Intranet Site in MOSS 2007

Now, install SharePoint Server 2010 right on the existing installation. In the Setup window, we can view the server requirements, installation guide etc. We will skip this part and proceed straight to the Installation.

SharePoint Server 2010 installation screen

First we need to install software prerequisites. We may already have all required components since we are already running MOSS 2007, but to be sure, we’ll go select this option.

The preparation tool window that launches checks our server for the required components, and installs them if needed. The components that will be updated are:

  • Application Server Role and IIS Role
  • SQL Server 2008 Native Client
  • Microsoft “Geneva” Framework Runtime
  • Microsoft Sync Framework Runtime v1.0
  • Microsoft Chart Controls for Microsoft .NET Framework 3.5
  • Microsoft Filter Pack 2.0
  • Microsoft SQL Server 2008 Analysis Services ADOMD.NET

Let’s open the preparation tool. After reading the short tool description and accepting the terms, the preparation tool will start updating the server immediately.

SharePoint Server 2010 Preparation Tool

After successful configuration, the summary screen will be displayed and the tool will likely request a reboot of the system.

Preparation Tool Summary Screen

When Finish button is clicked the system will reboot automatically. After the reboot, the Preparation Tool launches again and finishes the rest of the steps. Now our system is ready to install SharePoint Server 2010, so select that option from the setup pane.

We will be prompted to enter the license key

Product Key window in SharePoint Server 2010 Setup

After the key we have to read and accept licence terms. Next screen advise that MOSS 2007 was detected.

SharePoint Server 2010 Setup Screen – Upgrade Window

As advised in the above screen we need to run the stsadm command now to ensure our intranet can be successfully migrated. Open cmd.exe console in administrator mode.

Start – Cmd.exe in Administrator mode.

Navigate to the MOSS 2007 Bin Directory, which is located by default at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin directory.

Cmd Window in the MOSS 2007 bin folder.

Enter stsadm -o preupgradecheck. This command does not perform any repairs, but \only checks for and reports issues with possible solutions to apply before the migration. As the command executes we will see the output continuously displayed on the screen with different status notifications. In this check, some notifications were “Aborted due to internal error”. We will ignore this for now as the overall check was successful.

stsadm preupgradecheck output.

The browser will then open to display the html document with the summary of the output and details of every issue. As all components passed the test we are ready for the migration.

Go back to our SharePoint Server 2010 Setup window and click the Install Now button.

After the installation, we’ll see the final screen where we are informed that we must launch the SharePoint configuration wizard in order to update our content to latest SharePoint version.

SharePoint Server 2010 Installation Summary screen

Click Close to run SharePoint Configuration wizard. If you were expecting a wizard similar to the SharePoint 2007 wizard, you will be disappointed. We have now entirely new environment for SharePoint 2010 version and hence a new Configuration Wizard.

SharePoint 2010 Configuration Wizard

Click Next, and the below warning will be shown:

Warning Window in SharePoint 2010 Configuration Wizard

Click Yes and we will see a new feature of SharePoint 2010  –  Farm Passphrase.

Farm Security Settings Window

The Farm Passphrase will prevent server administrators from changing any data in our SharePoint 2010 installation when no password is provided. Administrations won’t be able to use content or configuration databases even if full database backups are obtained. Enter a password and continue with the configuration.

The next step is the Visual Upgrade.

Visual Upgrade Window

Here we decide the look and feel of the SharePoint site. You can upgrade all your farm to the SharePoint 2010 design right now. However we will not do this in this demonstration in order to be sure that everything will run fine in 2010 before modifying the design. SharePoint Server 2010 allow me to preview the look and feel of sites before switching to the new SharePoint design, so  select “Preserve the look and feel of existing SharePoint sites” option, which will maintain the original SharePoint Server 2007 design.

Next we’ll be presented with a summary screen where we can review our settings and then click Next to start the farm configuration.

SharePoint 2010 Configuration Wizard Summary Window

If everything went fine and without any errors, we’ll see the final screen.

Configuration Wizard Setup Finished Screen

Click finish and review the migrated site:

Our Intranet site on SharePoint 2010

Since we elected to preserve the original SharePoint 2007  design the site looks identical to the site prior to migration (except for the large Give Feedback button)..

We can now preview the new layout. From the Site Actions Menu, select Visual Upgrade.

Site Actions Menu

The configuration window will open, where we can select generic options about the site, such as the title, description, logo and the template.

Site Settings Window

Under the Visual Upgrade option, select “Preview the new SharePoint user interface” which will allow us to view the site in new 2010 design but we still have the ability to revert to the SharePoint 2007 layout if any errors are encountered. Click OK and view the results.

Site Preview of the SharePoint 2010 Design

We can view the new layout and it seems to work as expected. So go back to Visual Upgrade option and finish the migration completely.

Site settings screen – we’ve selected Use the New SharePoint User Interface option.

We are done! As you’ve seen, it is quite simple to migrate a SharePoint 2007 environment to SharePoint 2010.

Happy and successful migrations!

I was reading a post from Apoorv Durga, about migration strategies on software development. It is a fantastic post. It is really true that many of the migration falls due to poor planning or sometime negligence towards the basic. SharePoint 2010 lunched yesterday and a very interesting product from Microsoft. Many organisations already considering migrate from the existing version of MOSS 2007 to SP 2010
This entry was posted in SharePoint 2007, SharePoint 2010 and tagged , , , , . Bookmark the permalink.

1 Response to Migration strategies and Step by Step – Migrating from MOSS 2007 to SharePoint 2010

  1. Pingback: Migration strategies and Step by Step – Migrating from MOSS 2007 to SharePoint 2010 (via Mrin’s Blog) « Sharepoint Infoblog

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s