I finally completed my first sharepoint 2013 migration from2010 version. Though I have seen a lot of posts on the upgrade, I would like toshare my step-by-step approach towards the migration.
Before you start please read this post on Things to Consider before you do your 2013 migration
Basically, as Microsoft recommends Icreated and configured a SharePoint 2013 farm and then copied, attached andupgraded the content databases from the SharePoint 2010 farm into the new 2013farm.
Step 1: Created a new sharepoint 2013 farm (WindowsServer 2012, Mounted the sharepoint 2013 ISO file and the installation is verystraight forward). I am not going to detail this here.
Step 2: Took a back-up of the content Databaseof the web application that I wanted to upgrade. I did this late in the nightand ensured no one is online. The best approach is to make the Sharepoint 2010farm read-only and start the back-up.
Step 3: created a new web application in the Sharepoint 2013farm with a host header intranet.shopsharepoint.com.
Step 4: Created a new db called intranet_contentDB in thenew environment and Copied the content DB from 2010 and restored the copy inthe new sharepoint 2013 environment. The Restore was successful.
Step 5: Performed a quick test to check the Content databasefor upgrade. Use the Test-SPContentDatabase suggested by Microsoft.
Step 6: I had a few custom solutions on my old Sharepoint 2010web application. Some of them are custom webparts, surveys, custom solutionsetc,. I got the below messages when I executed the Test-SPContentDatabasepowershell command. As you could see below, the yellow box doesn’t block theUpgrade as the content DB upgrade just upgrades the schema and nothing else.But, the red box tells us that there are few items that can make your Upgradefail (UpgradeBlocking : True)..not good.
Step 7: Tried to analyze these failed categories and checkedeach one of them in the Sharepoint 2010 web application. Found that one of the survey(Buggylist) didn’t open in sharepoint 2010 (though the survey is part of thesite). It’s advisable to have the site thoroughly tested in sharepoint 2010before performing an upgrade. So, I went back to the Sharepoint 2010environment again and ran a powershell command to remove the buggy survey.
Step 8: To double confirm that, I went back to the SP 2010SQL database & confirmed that that the buggy survey is removed.
Step 9: I also have to open the sharepoint Upgrade log tofigure out what other errors are. It looked like the below. There were somecustom solutions that were part of the Sharepoint 2010. For the time being, I deactivatedthese custom solutions to avoid the upgrade.
Step 10: Since I made some changes to SP 2010 web site, Ijust need to re-do the entire steps 2,4 and 5 until I see all the categories toshow (UpgradeBlocking : False).
Step 11: I got to a point where all the categories that’sshown after executing Step 5 PS command.
Step 12: I then mounted this tested content DB for theintranet site (intranet.shopsharepoint.com) using the Mount-SPContentDatabasein the new sharepoint 2013 farm.
Step 13: The Mount was successful but I did saw a promptcoming out when I tried to browse the site. I realized that’s because of thehost header issue. (Remember the article - http://support.microsoft.com/kb/896861).Yes, I do need to perform those registry operation before I see the site blossomedin 2013 (in 2010 version).
Step14: Tried the Demo Upgrade. It said, it will take a dayor two to perform the demo upgrade. I'll let you know about the further progress shortly
