1. Use the Stsadm to perform the pre upgrade check on the MOSS 2007 environment, this option is available in MOSS 2007 SP2.
Run the following command
Stsadm –o PreUpgradeCheck
, check the resulting reports to identify the following:
a. Information & Configuration
i. Content Sources & Start addresses
ii. Farm & Search Topology
iv. Upgrade Types
v. AAMs, Large Lists & Libraries
b. Important Issues and Dependencies
i. Site Definition (referenced & missing)
ii. Installed Language Pack
iii. Features (referenced & missing)
iv. Custom List Views & Custom Field Types, Web.Config entries
2. I used the “attach content database” migration option. So you need to take a backup of all the content databases in your MOSS 2007 server farm.
3. Restore the content databases to your new SharePoint 2010 server farm. Using the simple SQL server attach database option.
4. You can also use a backup/ restore database option.
5. Make sure that you have the same language pack on MOSS 2007 and SharePoint 2010.
6. Create a new empty SharePoint 2010 web application on the new SharePoint farm. You can do this from SharePoint 2010 central administration
7. Perform the “attach content database” command as shown in the below figure. You can do this from the SharePoint 2010 Management power shell
STSADM -o addcontentdb -url http://itweb.contoso.com/ -databasename SP_2007_Content -databaseserver Demo2010
8. Change the site collection owner of the new restored site collection to a suitable user account, as well as the secondary site collection owner. You can do this from the SharePoint 2010 Management power shell using the below command line
stsadm.exe -o siteowner -url http://SiteURL:Port -ownerlogin doamin\username -secondownerlogin domain\secondusername
9. Merge the compiled source code to the new virtual directory of your web application. You can find details about this source code and its upgrade in the following part 1 of this post:
10. Finally perform the visual upgrade from the site sittings menu (as shown in the below figure) or using the SharePoint 2010 Management power shell. I recommend taking a full backup of you site collection before performing visual upgrade to be able to recover in case of this step encounters any errors.