Home/ Questions/Q 6954679
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T14:38:13+00:00

I was tasked to research migrating a 2007 MOSS to ShrePoint 2010. Got two

  • 0

I was tasked to research migrating a 2007 MOSS to ShrePoint 2010. Got two servers, one is runing a SQL 2008, and the other has SharePoint 2010 already installed. I need to migrate several publishing and team sites and their corresponding databases. I started reading this article on Upgrade and Migration for SharePoint Server 2010
, then another at Migrate an existing server farm to a 64-bit environment but have a little confusion about wheather I’m migrating, upgrading, or moving the system, as each article defines steps to do this.

Current 2007 MOSS and SQL 2005 are on Windows 2003 32-bit OSs. The new system which at this point in not part of the farm but is in the same domain, are a 64-bit blades running Win 2008 OS with SQL 2008 and SharePoint 2010 – all already instaled / Central Admin site already running. The whole farm consists of 2 severs I just described.

Thanks for reading my post and appreciate any pointers!

Risho.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I just went through this exact scenario. The documentation on the various methods can get confusing. Note, for simple farms (no BDC, etc.), all you really need is the content databases. Here’s a simple way to accomplish your goal:

    • On existing, 2007 farm, make sure it’s Service Pack 2
    • On existing 2007 farm, run stsadm -o preupgradecheck
    • Fix any errors identified by the upgrade checker
    • Backup the Content database(s) you want to migrate (old 2007 farm)
    • Restore Content database(s) to new SQL server
    • Create a new Web Application on the new 2010 farm. A new WebApp will need to create a Content DB, so name it something like WSS_Content_Temp. This will be the WebApp that you will restore your Content to, so name the WebApp appropriately. You’ll remove the content DB, so name it whatever you want.
    • From PowerShell, run: Test-SPContentDatabase -name <NameOfMovedContentDB> -webapplication http://yourNewWebApp
    • Fix any errors identified
    • From PowerShell, mount the newly restored/moved database. Run Mount-SPContentDatabases -name <NameOfRestoredContentDB> -webapplication http://yourNewWebApp. You should see a progress % number that is incrementing. Depending on how big your content databases are, this could take a while (30+ minutes)
    • From Central Admin -> Application Management, select/highlight your new Web Application.
    • The go back to Central Admin -> Manage Content Databases, and remove the original, temp Content DB (WSS_Content_Temp)

    At this point, if all went well, you should be able to browse to http://yourNewWebApp and see all your content.

    Rinse and repeat as needed.

    • 0