SharePoint 2010: Checklist for Migrating from 2007 to 2010

 

This checklist is provided to you to make it easier to migrate from SharePoint 2007 to SharePoint 2010. Some of the information is from TechNet and other parts are my own contributions. Please feel free to comment and improve it.

[ ]	Take a full backup of your Environment	Use SQL backup to backup SQL databases and verify that you have a fresh full backup of your Web Front End Server(s) and your application server(S) inclusive system state, 12 Hive and GAC
[ ]	Validate your full backups!	It is critically important that you validate your backups BEFORE you go any further!
[ ] [ ] [ ] [ ]	Run the pre-upgrade checker Run the pre-upgrade checker and address any issues. Use the report that is generated by the tool to fill out the Upgrade planning worksheet. Detailed steps:Run the pre-upgrade checker (SharePoint Server 2010). If SP2 is not installed Install WSS 3.0 SP2 Install MOSS 2007 SP2 stsadm -o preupgradecheck	Perform this step multiple times as you clean up your environment and test your upgrade process. Running the checker takes only a few minutes, but addressing any issues might take days or weeks. The operation is available with Office SharePoint Server 2007 Service Pack 2 and has been updated in the October 2009 Cumulative Update for Windows SharePoint Services 3.0 and Office SharePoint Server 2007 %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\LOGS\PreUpgradeCheck_YYYYMMDD-HHMMSS-SSS-random-number.htm (Se bilaga 1) Check the issues: http://support.microsoft.com/kb/960577
[ ] [ ]	Create an inventory of server-side customizations in the environment Create an inventory of the server-side customizations in your environment (solutions, features, Web Parts, event handlers, master pages, page layouts, CSS files, and so on). Much of this information is reported when you run the pre-upgrade checker. Record all customizations needed for your environment in the upgrade worksheet. Detailed steps:Identify and install customizations in the "Use a trial upgrade to find potential issues" article. stsadm -o enumallwebs -databasename <Your_Database> -databaseserver <Your_Databaseserver>	Perform this step for the whole environment. Check each Web server to make sure that you don't miss any customizations. Keep the inventory up to date as you prepare for the upgrade. This operation lists an ID for each site collection and subsite in your environment and the templates that the site relies on. This operation was first introduced in Office SharePoint Server 2007 with Service Pack 2 (SP2)
[ ] [ ] [ ]	Clean up your environment Before you begin upgrading, you should make sure that your environment is functioning in a healthy state and that you clean up any content that you do not have to upgrade. Clean up any orphaned sites or data, address any large lists and large ACLs, remove extraneous document versions, and remove any unused templates, features and Web Parts. Detailed steps:Cleaning up your environment before upgrade (SharePoint Server 2010). stsadm -o databaserepair -url http://<URL_of_WindowsSharePointServices_Site> -databasename <name of database that contains the orphan item> stsadm -o databaserepair -url http://<URL_of_WindowsSharePointServices_Site> -databasename <name of database that contains the orphan item that is to be deleted> -deletecorruption	Perform this step once for the whole environment. This process might take days or weeks to complete. Detect orphan posts and items in an database Delete Orphan data
Prepare the new environment Also seePrepare the new SharePoint Server 2010 environment for a database attach upgrade.
[ ]	Install and configure SharePoint Server 2010 and any language packs Install the prerequisite software, and then install and configure SharePoint Server 2010.	Perform these steps on each server in your farm. This step might take one or more hours, depending on how many servers are in your environment.
[ ]	Configure service applications Enable and configure the services you need in your new environment. Do not configure the User Profile service application yet. You will enable and configure the User Profile service application when you upgrade the Shared Services Provider (SSP) database.	Perform this step once for the whole environment.
[ ]	Configure general farm settings Reapply any general farm settings that you must have from your previous farm — such as blocked file types and e-mail and quota settings — and add users or groups to the Farm Administrators group. Configure new settings such as usage and health data collection, diagnostic logging, and mobile accounts. Important: If you had disabled the Workflow Auto Cleanup timer job in your Office SharePoint Server 2007 environment, make sure that you disable this timer job in your new environment also. If this timer job is enabled in the new environment and disabled in the previous version environment, you might lose workflow associations when you upgrade. For more information about this timer job, seeDisable preservation of workflow history (SharePoint Server 2010).	Perform this step once for the whole environment. To disable automatic workflow cleanup Verify that you have the following administrative credentials: To disable automatic workflow cleanup, you must be a member of the Farm Administrators SharePoint group. From the Central Administration Web site, on the Quick Launch, clickMonitoring. On the Monitoring page, in the Timer Jobs section, clickReview job definitions. On the Job Definitions page, in theTitle column, click the Workflow Auto Cleanup link that is associated with the Web application for which you want to disable automatic workflow cleanup. On the Edit Timer Job page, clickDisable to disable the Workflow Auto Cleanup feature. Note: If you later decide that you want to enable automatic workflow cleanup, access this page again and then clickEnable to enable automatic workflow cleanup.
[ ]	Create and configure Web applications Create a Web application for each Web application that existed in the old environment.	Perform this step once for the whole environment.
[ ]	Reapply server-side customizations Manually transfer all server-side customizations into your new farm. Refer to the inventory you created in the upgrade worksheet to make sure that you install any components that your sites depend on to work correctly.	Make sure that you reapply customizations to all Web servers in the farm.
[ ]	Verify the new environment After you set up the new environment, you can perform tests to make sure it contains all the components you have to have before you upgrade your data.	Perform this step once for the whole environment.

Perform the upgrade

Follow these steps in order during a database attach upgrade. Steps required for database attach with read-only databases are also included.

Detailed steps: Attach databases and upgrade to SharePoint Server 2010.

Perform the database attach upgrade		Notes
[ ]	Run the pre-upgrade checker Run the pre-upgrade checker again to identify any new or remaining issues before you set the databases to read-only or back up the databases. Detailed steps: Run the pre-upgrade checker (SharePoint Server 2010).	Running the checker takes only a few minutes, but addressing any issues might take longer.
[ ]                   [ ]	Set the previous version databases to be read-only (database attach with read-only databases) If you want your original environment to remain available to users in a read-only state, set the databases to read-only before you back them up. Stsadm –o setsitelock –URL <your site> -lock readonly	Perform this step for each content database in your environment. Depending on your organization, you might need a database administrator to perform this task.
[ ]	Back up databases Back up all of your content and SSP databases before you begin the database attach upgrade process.	Perform this step for each content database and SSP database in your environment. This step can take an hour, several hours, or longer, depending on your data set and your environment. Depending on your organization, you might need a database administrator to perform this task.
[ ]	Detach the previous version databases (standard database attach) If you are going to upgrade the original databases (rather than a backup copy), detach the original databases from the instance of Microsoft SQL Server so that you can move them to the new environment.	Perform this step for each content database and SSP database in your environment. Depending on your organization, you might need a database administrator to perform this task.
[ ]	Restore a backup copy of the database (database attach with read-only databases) If you are going to upgrade a copy of the databases, restore the databases from the backup.	Perform this step for each content database and SSP database in your environment. This step can take an hour or longer, depending on your data set and your environment. Depending on your organization, you might need a database administrator to perform this task.
[ ]	Verify custom components Use the Test-SPContentDatabaseWindows PowerShell cmdlet to verify that you have all the custom components that you need for that database.   Test-SPContentDatabase –Name <database name> -WebApplication <URL	Perform this step for each content database in your environment. Running the cmdlet takes only a few minutes, but addressing any issues might take longer.
[ ]	Verify permissions Ensure that the account that you use to attach the databases is a member of the db_owner fixed database role for the content databases that you want to upgrade.
[ ]                         [ ]     [ ]	Attach a content database to a Web application Attach the first content database that you want to upgrade. You must perform this action from the command line. You can use the Mount-SPContentDatabaseWindows PowerShell cmdlet or the AddContentDB Stsadm operation.   stsadm -o addcontentdb -url <URL> -databasename <database name>   cls	Perform this step for one content database in your environment. This step might take an hour, several hours, or longer, depending on your data set and hardware on the Web servers, database servers, and storage subsystem.
[ ]                   [ ]	Verify upgrade for the first database Verify that upgrade succeeded for the first database, and review the site to see if there are any issues. Detailed steps: Verify upgrade and review upgraded sites (SharePoint Server 2010).   Stsadm -o localupgradestatus	Perform this step for the content database you just attached.   The Setup.exe log file for SharePoint Server 2010. The Setup log file is stored in the temp directory for the user account that is running Setup (%USERTEMP% or %WINDIR%\Users\user account\AppData\Local\Temp). It is named SharePoint Server Setup(YYYYMMDDHHMMSSSSS).log, where YYYYMMDD is the date and HHMMSSSSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds). The SharePoint Products Configuration Wizard (Psconfig.exe) log file. The Psconfig.exe log files are located at %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\14\LOGS. The logs are named in the following format: PSCDiagnostics_MM_DD_YYYY_HH_MM_SS_SSS_randomnumber.log, where MM_DD_YY is the date and HH_MM_SS_SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds), and the random number is used to differentiate between possible simultaneous attempts to run the Psconfig.exe program. The upgrade log file and the upgrade error log file. The upgrade log file and the upgrade error log file are located at %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\14\LOGS. The logs are named in the following format: Upgrade-YYYYMMDD-HHMMSS-SSS.log, where YYYYMMDD is the date and HHMMSS-SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds). The upgrade error log file combines all errors and warnings into a shorter file and is named Upgrade-YYYYMMDD-HHMMSS-SSS-error.log.
[ ]	Upgrade the SSP database and configure user profiles Before you upgrade any My Site Web sites, you need to upgrade the SSP database and configure the User Profile service application.	Perform this step for each SSP that you had in your original environment. This step might take an hour or more to complete, depending on your data set and hardware on the Web servers, database servers, and storage subsystem.
[ ]	Upgrade My Site Web sites Configure the My Site host URL and upgrade the My Site Web sites.	Perform this step for each content database that contains My Site Web sites in your environment. This step might take an hour, several hours, or longer, depending on your data set, whether you are upgrading multiple databases in parallel, and the hardware on the Web servers, database servers, and storage subsystem.
[ ]	Attach remaining databases Attach and upgrade the remaining content databases in your environment. You must perform this action from the command line.-n	Perform this step for each of the remaining content databases in your environment. This step might take an hour, several hours, or longer, depending on your data set, whether you are upgrading multiple databases in parallel, and the hardware on the Web servers, database servers, and storage subsystem.
[ ]	Monitor upgrade progress Use the Upgrade Status page in SharePoint Central Administration to monitor progress as your sites are upgraded. Detailed steps: Verify upgrade and review upgraded sites (SharePoint Server 2010).	Perform this step for each content database that you upgrade. This step might take an hour, several hours, or days, depending on your data set.
[ ]	Verify upgrade for the remaining database Verify that upgrade succeeded for the remaining databases, and review the sites to see if there are any issues. Detailed steps: Verify upgrade and review upgraded sites (SharePoint Server 2010).	Perform this step for each of the remaining content databases in your environment. This step might take an hour, several hours, or days, depending on your content.

Perform post-upgrade steps

Follow these steps in order after you perform a database attach upgrade.

Post upgrade steps for database attach upgrade		Notes
[ ]	Reapply administrator permissions for services By default, farm administrators have permissions to all services when you perform a database attach upgrade. If you want to apply more restrictive permissions, do so now.	Perform this step for any services that require restricted permissions.
[ ]	Upgrade profile properties to taxonomy data and update the photo store for User Profile services Data in profile properties in Microsoft Office SharePoint Server 2007 that had multiple values was stored in the SSP database as part of the Profile Services data. For SharePoint Server 2010, this data must be converted to taxonomy data and be stored in the managed metadata database. When you upgrade, any photos that were stored as profile pictures must be updated. If you do not update the photo store data, either no photos will be displayed or some photos might appear distorted. You perform these actions from the command line by using Windows PowerShell cmdlets. Detailed steps: Upgrade profile properties to taxonomy data and update the photo store for Profile Services	Perform this step once for each User Profile service application in your environment. This step contains a lot of smaller steps. Depending on the complexity of your user profile data and your configuration, this might take an hour or several hours to complete.
[ ]	Create and configure the Secure Store service application and migrate SSO data to the Secure Store service The SSO service that was available in Office SharePoint Server 2007 has been replaced with the Secure Store service in SharePoint Server 2010. There is no direct upgrade path for the data and settings from SSO to the Secure Store service, but you can migrate data from the SSO database to a new Secure Store database. Excel Services Application needs the Secure Store service account to function correctly. Detailed steps: Create and configure the Secure Store service application and migrate SSO data to the Secure Store service	Perform this step for each Secure Store service application that needs data from a previous SSO service.
[ ]	Upgrade solutions that depend on the Business Data Catalog If you used the database attach method to upgrade and you want to continue to use the external data that is accessed through one or more application definitions, you perform several additional tasks. Detailed steps: Upgrading solutions that depend on the Business Data Catalog	Perform this step once for your entire environment.
[ ]	Update links that are used in any upgraded InfoPath form templates For a database attach upgrade, you exported and imported any InfoPath form templates in your environment when you created the new environment. After upgrade, you can now update the links that are used in those upgraded form templates to point to the correct URLs by using a Windows PowerShell cmdlet. Detailed steps: Update links that are used in any upgraded InfoPath form templates	Perform this step once for your entire environment.
[ ]	Verify upgrade and review upgraded sites Review sites to be sure that they have been upgraded successfully and are ready for users to view. Detailed steps: Verify upgrade and review upgraded sites (SharePoint Server 2010).	Perform this step for every upgraded database and site collection in your environment. This step might take an hour, several hours, or days, depending on your content. You should also have site owners review their sites and report any issues.
[ ]	Start a full crawl After all content is upgraded and all settings are configured, you can start a full search crawl of your content. This might take several hours or several days to complete, depending on how much content exists in your environment.	Perform this step once for your entire environment. Performing a full crawl can take several hours or days to complete, depending on the amount of content in your environment.