SharePoint 2007 to SharePoint 2010 Farm Migration. Phase 1 – Configuration Analysis


In the current series I’d like to describe how to analyse the SharePoint Farm and prepare it for the SharePoint 2010 migration. We will review the following 3 sections:

  1. Farm Architecture and Configuration Analysis (current)
  2. User and Group Analysis
  3. Farm Migration

The first and the most important step in SharePoint 2007 –>SharePoint 2010 migration is the understanding of existing SharePoint environment to get enough information to design the new Farm. 

Let’s review in details the following template that I’m using to document the farm settings and tools that allow to gather all necessary information (we don”t describe search, excel and other services settings here)

  1. Farm Information
    1. Farm Servers and Services
    2. Web Applications
    3. Content Database and Site Collections
    4. Alternative Access Mapping
    5. Farm Solutions
    6. Enabled Farm Features
    7. Search Settings
  2. Site Information
    1. Web Parts
    2. Web.config changes
    3. Site Definitions
    4. Customized & Checked-out Items
  3. Sites Topology
    1. Sites
    2. Sites Structure Diagram
    3. Site Collections with Diagrams
  4. Issues

1. Farm Information

Content: This section enlists farm servers, components from the farm and general information about farm configuration (email settings)
Tools: STSADM –o “preupgradecheck” (Upgrade Planning Information section for servers and components) & Central Administration to get the mail settings

a,,) Farm Servers and Services

Content: table with the farm servers and assigned roles
Tool: Use the Central Administration & SharePoint Manager 2007 to get this information

b) Web Applications

Content: List of web applications and its URS
Tool: Central Administration

c) Content Database and Site Collections

Content: Table with the following info – content database name, number of sites, size, list of site collections
Tool: SharePoint Diagnostic tool for the Content DB size; Central Administration and SharePoint Administration Toolkit (Batch Site Manager Solution)

d) Alternative Access Mapping

Content: Table with AAM Internal/External URLs and Zones
Tool: “preupgradecheck” log & SharePoint Diagnostic

e) Farm Solutions

Content: Table with the installed solutions and sites where they are active
Tool: SharePoint Manager 2007 / Bamboo SharePoint Analyser

1.f) Enabled Farm Features

Content: List of enabled features on the farm level
Tool: Central Administration 

1.f) Search settings

Content: SSP settings (servers, databases name, crawling settings)
Tool: Central Administration & SharePoint Diagnostic

2. Site Information

a) Web Parts

Content: list of installed web parts
Tool: Bamboo SharePoint Analyzer

b) Web.config changes

Content: list what was changed in web.config for SharePoint sites
Tool: SharePoint Diagnostic shows web.config for each web application, but developer/admins own the knowledge about the changes

c) Customized & Checked-out Items

Content: list of customized & checked-out items
Tool: SharePoint Designer, choose Sites menu –> Reports –> Shared Content –> Customized Pages / Checked-out items

d) Used Site Templates across sites

Tool: “preupgradecheck” gives you a list where site templates are used

3. Sites Topology

a) Sites

Content: list of sites
Tool: Site Settings of the root site –> “Site hierarchy” item

a) Site Structure Diagram

Content: diagram of the root site
Tool: SWAT tool –> right mouse click on the site name and Show Site Diagram

4. Sites Topology

  • Use “preupgradecheck” log to document all found issues
  • use SharePoint Designer Diagnostic tab, to discover the potential issues



To get the necessary information I recommend to use the following tools:




  1. Alex Mondale Said,

    December 8, 2009@ 12:11 am      Reply

    What I am most frustrated about in trying to get sites from 2007 up and running in 2010 b2 is the fact that “stsadm -o import” doesn”t appear to be a workable approach: (Progress: Import did not complete|FatalError: The version of the package is different from the current v
    ersion this program supports,, and “stsadm -o restore” doesn”t work either (More cryptic failure: The site collection could not be restored. If this problem persists, please make sure the content databases are available and have sufficient free space.). Is MS really giving us zero tools for these upgrades, because if the pain involved in going from 2003 to 2007 is any indication, my company will likely not be willing to migrate to 2010 until 2020!

    Thanks for any clues you can provide! This is a great series of articles.

  2. laflour Said,

    December 8, 2009@ 7:16 am      Reply

    Why are you trying to import/export between versions?!
    Why not to make content DB upgrade instead to the test site and then move content within the SP2010 sites?!

    See there for more details

  3. harry Said,

    December 30, 2009@ 12:06 pm      Reply


    This artical is very useful for me. I am a Share Point developer and always looking to learn something new. I would like to introduce another good SharePoint blog, Have a look.

  4. Puja Said,

    March 5, 2010@ 12:17 am      Reply

    Hi Michael,

    I came across your article when searching for “migrating sharepoint 2007 list wsp to sharepoint 2010 list using Visual Studio 2010” . This is not as easy as migrating a workflow package was. DO you have any tips to share on it.

  5. laflour Said,

    March 5, 2010@ 12:28 am      Reply

    I struggling to find some time to write the final post on this topic 🙂 but my plan is to do a database attach migration via the PowerShell

    See this section of MSDN where they described the process

    The different migration tips (but for the old version are there)

  6. Puja Said,

    March 5, 2010@ 12:33 am      Reply

    Sorry for not being clear on my question. I do not want to migrate the list data, rather the LIST/Content Type itself. I have the definition of my List wrapped in a wsp package (built in VS 2008). I am looking to migrate the package to VS 2010 and then create a package (.wsp) and finally deploy it on sharepoint 2010.

    I have another qustion, if you can help. Is it possible to reverse engineer sharepoint 2010 list like it was possible in Sp 2007 using SPSource.

  7. laflour Said,

    March 5, 2010@ 4:06 am      Reply

    There is a converter for VS 2010 that can take your 2007 package and convert to 2010, but I forgot the name and url.

    Will send you link later today

  8. Dmitriy Chernyavsky Said,

    March 11, 2010@ 7:51 pm      Reply

    Well, I am in the process of migration from 2007 to 2010 beta. So I”m really interested in a link to the migration tool you”ve mentioned.

  9. laflour Said,

    March 12, 2010@ 1:30 am      Reply

    Google for “Visual Studio 2010 migration tool for VSeWSS SharePoint projects”

  10. rfarqleet Said,

    April 6, 2010@ 7:14 am      Reply

    Thanks for writing such an interesting article.
    Migrate data from your existing SharePoint 2007 to SharePoint 2010 with 0% content loss,

    Download here:

  11. Steve Said,

    September 9, 2010@ 11:51 pm      Reply

    If I migrate from Sharepont 2007 to 2010, what will be the impact on database sizings? Will I have SP2007 content etc migrated to different SP2010 databases and maintain the overall same volume ( MB ) in data, or will data grow or shrink in size?

    Also, if I create a new SP2010 farm and import data, will this change data volume ( MB )?

    We are having issues with trying to establish what will happen to our existing farm as this impacts cost of hardware.

    Any thoughts welcome



  12. Michael Said,

    September 9, 2010@ 11:59 pm      Reply

    Interesting question. Hard to say actually. The actual SharePoint content should stay the same, but the overall DB content of all SharePoint databases will grow, because SharePoint 2010 introduces new services and almost each service has its own database

  13. Steve Said,

    September 10, 2010@ 3:54 am      Reply

    Hi Michael,

    Well were in the process of creating a new SP2010 farm, but also importing content from existing SP2007 which we will shut down.

    We wanted to work out if the SP2007 content database, once it was imported into SP2010, whether it would go up or down in size compared to its original SP2007 size.

    As the new content comes into SP2010 from the SP2007 database, will it affect other databases for other SP2010 services etc and make these existing SP2010 farm SQL databases grow?

    If I do import a content database in SP2010, what else do I need to do? Does SP2010 automatically query the new database and create sites etc based on what sin the database, or do we have to do all that manually? Having to teach myself SP2010 and do a migration…..ouch

    My brain hurts…he he

  14. Michael Said,

    September 10, 2010@ 4:04 am      Reply

    There will be a slight change in the content, because the SharePoint 2010 has slightly different structure of Content Database. When you attach SP 2007 content DB to SharePoint 2010 it will be updated to the new format, but this change won”t increase your data in 2-3 times.

    To migrate SP2007 to SP2010 you might end up with Data Attach option, when you install SP2010 farm first and then detach content DB from 2007 and attach to 2010. The new SP2010 farm will require additional DBs. for example I made a full SP2010 install with all services from scratch, created a couple of sites, and I have about 50 databases with total size of 5GB. So yes, the entire content did grow.

  15. Raj Said,

    January 23, 2011@ 7:17 pm      Reply

    We are migrating 2007 to 2010, i would like to know what other (such as customized workflows, SP designer etc)will not migrate easily and what are ways. And the impact of this migration to any customized items.

RSS feed for comments on this post · TrackBack URI

Leave a Comment