SharePoint 2010 support two methods for migrating and upgrading a SharePoint 2007 install
[EDIT: Upgrading to SharePoint 2013? Check out our post at http://blog.armgasys.com/?p=275]
Method#1
In place upgrade.
This is very simple and straightforward. You insert the SharePoint 2010 DVD, run the “is everything ready for an upgrade” wizard, and then perform the upgrade. You just have to remember all things SharePoint 2010 are now 64bit.
Method#2
Migrate and upgrade individual web applications and content database.
This is known as the Database Attach Method of upgrading and is (based on my experience) the most common upgrade SharePoint users will encounter.
In this post, we will be reviewing the steps for performing method #2 upgrades.
Step#0 – Backup everything related to the content database you are migrating
Nuf’ said!
Step#1 – Attach the SharePoint 2007 content database to the new database server
This step only applies if you are also migrating to a new database server during the SharePoint 2010 upgrade process. If you are not changing database servers, skip to step#2
For SQL Server 2005 users, see the following MSDN article
http://msdn.microsoft.com/en-us/library/ms190209(SQL.90).aspx
For SQL Server 2008 users, see the following MSDN article
http://technet.microsoft.com/en-us/library/ms190209.aspx
Step#2 – Create a new web application in SharePoint 2010
To upgrade a content database, you must first have a SharePoint web application created which will connect to and consume the soon to be upgraded content database.
- Launch the SharePoint 2010 Central Administration web site
- Select Manage Web Applications under Application Management
- Click “New” on the ribbon
- Configure the new web application to fit your needs
NOTE: Take the defaults for Database Name. See Step#3 for more details.
Step#3 – Delete the content database which was just created in Step#2
Yes, you read correctly, delete the content database.
- Launch the SharePoint 2010 Central Administration web site
- Select Manage Content Databases under Application Management
- Select the web application created in step#2 from the web application drop down loaded in the upper right of the screen
- Click on the Database Name which was created in step#2
It will be named something like WSS_Content 1234ab-cfe1234-443abc-1234ab - Scroll to the bottom of the database information page displayed and check the Remove Content Database checkbox
- Click the OK button
What is happening here?
SharePoint requires a target web application for ALL content databases. Why? Because the web application determines which features are supported and installed for all content hosted by that web application. When the actual migration process occurs, the upgrade software scans the content database for all of the features being used by the content (I.E. lists, document repositories, third party, web parts, etc) and then determines if the target web application supports that feature.The problem we encounter is that SharePoint has nicely created an empty content database which we are never going to use because we already HAVE a content database. So, we need to perform a little bit of cleanup work.
Step#4 – Validate the SharePoint 2007 content database can be upgraded
SharePoint contains a PowerShell cmdlet which will validate the content database against the web application created in Step#3.
- Launch SharePoint Powershell
Start –> All Programs –> Microsoft SharePoint 2010 Products –> Management Shell - At the prompt, type the following PowerShell command
Test-SPContentDatabase –Name “Database Name” –WebApplication [url]Example
Test-SPContentDatabase –Name “Content DB” –WebApplication http://test.site.com
Will test the content database named Content DB against the existing web application http://test.site.com - Review the output for any issues listed as Upgrade Blocked: Yes
Any issue listed as Upgrade Blocked will need to be corrected.
Step#5 – Mount the database onto the web application created in Step#3
This step will upgrade and mount the database against your newly created web application
- Launch SharePoint Powershell
Start –> All Programs –> Microsoft SharePoint 2010 Products –> Management Shell - At the prompt, type the following PowerShell command
Mount-SPContentDatabase –Name “Database Name” –WebApplication [url]
And that is all there is to it.
Happy migrations!
Hello,
I’ve created a tool which provides a detailed information by parsing the Test-SPContentDatabase output.
With this tool you will exactly know where your custom web parts are located and even more.
http://dev4side.com/projects/sharepoint-2010-extended-migration-db-attach-report.aspx
It would be great if you can report a feedback/bugs on the codeplex site: http://sp2010extmigrareport.codeplex.com/discussions
Pingback: Migración de Sharepoint 2007 a 2010 | My freelancer life
Great Guide – thanks!
One thing I found, after doing a dummy migration to test, then following the exact same procedure for a live migration is that once you have mounted/converted a 2007 content DB into a web application, it will not work a second time. It loses its master page so the visual upgrade will not work, and various other files go missing during the process. I found that I had to delete the web application and recreate it before the migration to get it to work successfully.
Thanks again!
Thanks for the wonderful insight. You can use this visual guide to migrate from SharePoint 2007 to SharePoint 2010
http://www.sharepointdiary.com/2011/09/migrate-from-moss-2007-to-sharepoint-2010.html
To migrate from SharePoint 2010 to SharePoint 2013:
http://www.sharepointdiary.com/2013/09/migrate-from-sharepoint-2010-to-2013-step-by-step.html