Monday, September 19, 2011

Migrate from MOSS 2007 to SharePoint 2010 - Step by Step

In this article, I'm walking through Migrating from MOSS 2007 to SharePoint 2010 using database attachment method. 

  1. Run Preupgradecheck in MOSS 2007 server.
    1.  Analyze & Fix the issues.
  2. Take the back up of content database from MOSS 2007.
  3. Restore the content databases backup to SQL Server of SharePoint 2010.
  4. Create web application in SharePoint 2010.
  5. Attach the MOSS 2007 content databases to SharePoint 2010.
  6. Post Migration fixes

1. Run preupgradecheck in MOSS 2007 Server

This will be our primary analysis and reporting tool providing us with invaluable information regarding your SharePoint 2007 farm and actions that may be required to be taken prior to upgrading to SharePoint 2010. It is better to have October CU: where the preupgradecheck is enhanced further. 

Run the preupgradecheck as below in command prompt:

stsadm.exe -o preupgradecheck

stsadm.exe -o preupgradecheck Report
Once you get "Operation completed successfully", it will launch the “SharePoint Products and Technologies Pre-Upgrade Check Report”.  It can also be located under the following location;
%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\Logs\

1(a).   Analyze the report and Fix the following settings:

2. Take the Content Database Backup from MOSS 2007

Set the database to read-only before taking backups.
Set the database as read only:
  1. On the MOSS 2007’s database server, click Start, point to All Programs, Microsoft SQL Server, and then click SQL Server Management Studio.Take the Content Database Backup from MOSS 2007

SQL Server 2005 Management Studio Splash Screen

  1. Traverse to Databases node by expanding the tree.
  2. Right-click the name of the database that you want to set to read-only, and then click Properties.
4.    In the Properties dialog box, click the Options tab.
      5.   Under State, select the Database Read-only to True, and then click OK
Set SharePoint Content Database to Read-Only

Backup the database:
Follow these steps to take back-up:
  1. Traverse to Databases node by expanding the tree.
  2. Right-click the database you want to back up, point to Tasks, and then click Backup DatabaseBackup SharePoint Content Database from SQL Server
 3. In the SQL Server Backup dialog box, specify a name for the backup, select Back-up type - Full, select a destination, and then Click OK to start the backup process.
Backup SharePoint Content Database from SQL Server

 4. Repeat these steps to back up the databases that are used by MOSS 2007 in the environment.

3. Restore the back up on SharePoint 2010’s SQL Server:

  1. Open the SQL Server Management studio, traverse to “Databases” node. Then right click the “Databases” node and choose “Restore Database…” from the context menu. Restore SharePoint 2007 Content Database to SharePoint 2010
  1. Specify the Database name, Restore Source, Destination, File names in the screens.
Restore MOSS 2007 Content Database to SharePoint 2010
3. Click “OK” to start the restore operation and Wait for the restore to complete! The time of restoring database depends upon the database size and server’s capacity.

4. Create web application in SharePoint 2010

  1. In the SharePoint Central Administration, click on “Application Management” and click on “Create or extend Web application” under “SharePoint Web Application Management”.
  2. Again click on “Create Web application”. Set the settings according to the needs say
  3. Don’t create any site collection.
  4. Install & Copy the solutions, file system changes (like images, themes) from MOSS 2007 to MOSS 2007 servers.

Remove content database of the newly created web application in SharePoint 2010

Now, we need to delete the content db of the newly created web application in order to avoid any URL conflicts. Run the below stsadm command:

stsadm -o deletecontentdb -url -databasename <MOSS2007_Migration_Content>

Remove SharePoint Content Database: stsadm -o deletecontentdb

5. Attach restored database with the newly created web application in SharePoint 2010

Test the content database
Before attaching the content databases to the Web applications, use the Test-SPContentDatabase PowerShell cmdlet to verify that all of the custom components that you need for that database. It checks for all artifacts such as feature, setup files, web parts,etc that are referred in the content database are installed in the farm and provide you with an report.

Test-SPContentDatabase -Name <DatabaseName> -WebApplication <URL>

Delete the corrupted objects

stsadm -o databaserepair -url  <URL of SharePoint site>  -databasename <name of database> -deletecorruption

Finally, we need to attach the restored MOSS 2007 database to MOSS 2007 by running the STSADM
  1. The Content DB containing the root site collection is always applied first.
  2. The other content DBs can be applied in any order.
Attach the Content DB of the Root Site collection First. And then Attach the Content DBs of other Site Collections.

stsadm.exe -o addcontentdb -url -databasename <MOSS2007_Portal_Content>

Attach Content Database to SharePoint

 Or you can use the PowerShell cmd-let: Mount-SPContentDatabase
Mount-SPContentDatabase -Name <DatabaseName> -DatabaseServer <ServerName> -WebApplication <URL> 

Post Migration fixes

Once the content database attachment process is over, we have to manually fix the below things:

Unit Test:

Browse the migrated sites in SharePoint 2010 and check their look& feel and functionality.
SharePoint 2010 look and feel
Before and After:
MOSS 2007 to SharePoint 2010 - Before and After Screen


You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.

Check out these SharePoint products:


  1. This is an excellant post

  2. Nice detailed article. Thanks for posting.

  3. its totally cool

  4. It's really good job!............

  5. very good article and help full!!!!!!!!!!!!!!!

  6. Really great job done.

  7. Very helpful post.. It saved lot of my time

  8. Thanks for posting... Excellent article

  9. I actually enjoyed reading through this posting.Many thanks...

    Email Database

  10. Really very very good article

  11. Great Article.

    But, I have follow all if the steps , but my site collection is not displaying the content from sharepoint 2007. The database upgraded successfully and I can the mysites collection. The visual upgrade button is also grayed out.
    What can I do to be able to see the data from the 2007 SP site?


    1. Hi Antonio,
      If Visual upgrade is grayed out, You can use PowerShell to upgrade your sites to SharePoint 2010 UI. Visual Upgrade All Sites in a web application Using PowerShell


  12. Excellent article..

    Why do we use tools to migrate instead of attaching and detach migration ? What is the difference can you explain please ?

    1. Avinash,

      I've conducted a research on SharePoint Migration products, Methods and compared their features. Refer this article to get your questions answered: SharePoint Migration Products Comparison

      Salaudeen Rajack

  13. Its great Post with Details

  14. Really good article, very nice presentation, got everything i was looking for, thanks millions :-)

  15. A good article and very good presentation with details, got everything I was looking for, thanks millions for posting this article :-)

  16. Worked like a charm ! Great post and keep posting nice articles.. :)

  17. Hi Salaudeen,

    Can i migrate just a single site from SP2007 to SP2010 without tools ? If yes, how to do it ?

    1. You can Move your existing site collection to New content database and Migrate that Content DB!

      Refer here for: Move SharePoint Site collections between Content Databases

  18. Very informative, thanks a lot for saving our time.

  19. Thanks buddy..really helpful article.

  20. Salaudeen great collection thanks

  21. Really excelent job done. Thanks a lot Salaudeen.

    I am looking for another article after this process; "Upgrading to 2013".
    As you know there isn't any direct path to upgrade from 2007 to 2013.

  22. Excellent Post.

    Did you ever get a chance to make a Good SharePoint DR Document? In same Premise or Remote Data Center?

  23. Can you please help me ..... How to Migrate a SharePoint Site from 2007 to 2010 Using Server side coding / Power shell script

  24. Excellent Articles......thank U

  25. Appreciate your efforts, you have put in to write this post. Really nice n useful.

  26. Only thing missing is Item #4 under Step 4 - Install & Copy the solutions.
    Some detail on that aspect is BADLY needed. We have some XSN files that go with InfoPath forms, and it is very unclear how to migrate those pieces. Thanks.

  27. Hi

    Recently I did migration from Moss 2007 to SharePoint 2010. Everything was done successfully, except one that is documents were not attaching to shared document but in 2007 it was working fine. 2) I added documents manually, when I was trying to open those documents I was getting error. that is...( Word Web App cannot open this document due to an unknown error. If the problem persists, try opening the file in Microsoft Word). Please guide me in a right way.


    1. If its happening ONLY with the particular document library/document, Chances could be: DB/Library got corrupted!

  28. Hello,

    Could you please let me know in which step we need to deploy custom solutions(WSP) which needs to be deployed against web application.

    Is it after attaching the content databases to sharepoint?
    Before deleting the content database of newly created web application?

    Thanks in Advance.

    1. Deploy All custom solutions, 3rd party components, web parts before attaching databases!

  29. If the WSP file is deployed on web application in 2007 then how we can deploy the same solution in 2010 without web application.

    Even if we are creating dummy web application(as per Step4) but we are going to delete content database associated with it. Please help me to understand.

    Thanks in Advance.

  30. Hi,

    On step #5 when you say deleted the corrupted objects --

    stsadm -o databaserepair -url -databasename -deletecorruption

    Do you mean the URL of new webapplication on sharePoint 2010 server or the old MOSS 2007 server.

  31. Hi, Very nice description about SharePoint Migration.
    I like your web blog.Because whenever i come into your web blog
    then i always get the new interesting and important information in your web blog.

    Thank You

    SharePoint Migration

  32. Hi, I cannot delete the content db by your stsadm command it shows following errors
    1.The farm is unavailable
    2.Object reference not set to an instance of the object


Please Login and comment to get your questions answered!

You might also like:

Related Posts Plugin for WordPress, Blogger...