Preupgradecheck will provide us the invaluable information regarding the SharePoint 2007 farm and actions that may be required to be taken prior to upgrading to SharePoint 2010\/SharePoint 2013
Run the preupgradecheck as below in command prompt:
stsadm.exe -o preupgradecheck<\/p>\n\n\n\n
Once you get \u201cOperation completed successfully\u201d, it will launch the \u201cSharePoint Products and Technologies Pre-Upgrade Check Report\u201d. It can also be located under the following location;
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\12\\Logs\\<\/p>\n\n\n\n
Analyze the report and Fix the following settings:
\u2022 Identify any third party components used and deploy them to SharePoint 2010 and SharePoint 2013 site. E.g. Nintex, 3rd party features, including web parts, solutions and custom workflows
\u2022 Setup Incoming\/Outgoing email settings in SharePoint 2010 and SharePoint 2013environment
\u2022 Modified Web.Config entries
\u2022 Configure Alternate Access Mappings (AAM)
\u2022 Find the missing webpart, event receivers or features if any and delete them<\/p>\n\n\n\n
Take the Content Database Backup from MOSS 2007<\/strong> \u2022 Traverse to Databases node by expanding the tree Backup the database:<\/strong> \u2022 In the SQL Server Backup dialog box, specify a name for the backup, select Back-up type \u2013 Full, select a destination, and then Click OK to start the backup process.<\/p>\n\n\n\n Restore the Backup on SharePoint 2010 SQL server<\/strong> \u2022 Specify the Database name, Restore Source, Destination, File names in the screens. Create web application in SharePoint 2010<\/strong> Remove content database of the newly created web application in SharePoint 2010<\/strong><\/p>\n\n\n\n Now, we need to delete the content db of the newly created web application in order to avoid any URL conflicts. Run the below stsadm command: Attach restored database with the newly created web application in SharePoint 2010<\/strong> \u2022 Or you can use the PowerShell cmd-let: Mount-SPContentDatabase Migrate from Classic Mode to Claims mode<\/strong> Refer this Tech-net guide on how to migrate to claims \u2013 http:\/\/technet.microsoft.com\/en-us\/library\/gg251985.aspx<\/p>\n\n\n\n Post Migration fixes<\/strong> \/\/Use this for entire webapplication \/\/Use this for individual site Similarly to migrate content from SharePoint 2010 to SharePoint 2013, follow the steps from 1 \u2013 8. Once all the operations are done, browse the migrated site and check the functionality.<\/p>\n\n\n\n References:<\/p>\n\n\n\n http:\/\/technet.microsoft.com\/en-us\/library\/ee947141(v=office.15)<\/a><\/p>\n\n\n\n http:\/\/www.sharepointdiary.com\/2013\/09\/migrate-from-sharepoint-2010-to-2013-step-by-step.html<\/a><\/p>\n\n\n\n
Set the databases to read-only before taking backups.
\u2022 On the MOSS 2007\u2019s database server, click Start, point to All Programs, Microsoft SQL Server, and then click SQL Server Management Studio.<\/p>\n\n\n\n![\"\"](\"https:\/\/viewmyprojects.com\/winwirewp\/wp-content\/uploads\/2023\/11\/SQL-Server-Management-Studio.webp\")
<\/figure>\n\n\n\n
\u2022 Right-click the name of the database that you want to set to read-only, and then click Properties.
\u2022 In the Properties dialog box, click the Options tab.
\u2022 Under State, select the Database Read-only to True, and then click OK<\/p>\n\n\n\n
Follow these steps to take back-up:
\u2022 Traverse to Databases node by expanding the tree.
\u2022 Right-click the database you want to back up, point to Tasks, and then click Backup Database<\/p>\n\n\n\n![\"\"](\"https:\/\/viewmyprojects.com\/winwirewp\/wp-content\/uploads\/2023\/11\/Backup-Database.webp\")
<\/figure>\n\n\n\n
\u2022 Open the SQL Server Management studio, traverse to \u201cDatabases\u201d node. Then right click the \u201cDatabases\u201d node and choose \u201cRestore Database\u2026\u201d from the context menu.<\/p>\n\n\n\n![\"\"](\"https:\/\/viewmyprojects.com\/winwirewp\/wp-content\/uploads\/2023\/11\/Restore-Database.webp\")
<\/figure>\n\n\n\n
\u2022 Click \u201cOK\u201d to start the restore operation and Wait for the restore to complete! The time of restoring database depends upon the database size and server\u2019s capacity.
\u2022 Make the Read-Only database to false after restore<\/p>\n\n\n\n
\u2022 In the SharePoint Central Administration, click on \u201cApplication Management\u201d and click on \u201cCreate or extend Web application\u201d under \u201cSharePoint Web Application Management\u201d.
\u2022 Again click on \u201cCreate Web application\u201d. Set the settings according to the need.
\u2022 Don\u2019t create any site collection.
\u2022 Install & Copy the solutions, file system changes (like images, themes) from MOSS 2007 to SharePoint 2010 server.<\/p>\n\n\n\n
stsadm -o deletecontentdb -url <http:\/\/url> -databasename <MOSS2007_Migration_Content><\/p>\n\n\n\n
\u2022 Test the content database: Before attaching the content databases to the Web applications, use the Test-SPContentDatabase PowerShell cmdlet to verify that all of the custom components that you need for that database. It checks for all artifacts such as feature, setup files, web parts etc. that are referred in the content database are installed in the farm and provide you with a report.
\u2022 Test-SPContentDatabase -Name <DatabaseName> -WebApplication <URL>
\u2022 Delete the corrupted objects
\u2022 stsadm -o databaserepair -url <URL of SharePoint site> -databasename <name of database> -deletecorruption
\u2022 Attach the Content DB to Webapplication
\u2022 Finally, we need to attach the restored MOSS 2007 database to SharePoint 2010 by running the STSADM command
o The Content DB containing the root site collection is always applied first.
o The other content DBs can be applied in any order. Attach the Content DB of the Root Site collection First. And then Attach the Content DBs of other Site Collections.
stsadm.exe -o addcontentdb -url <URL of SharePoint site> -databasename <MOSS2007_Portal_Content><\/p>\n\n\n\n
Mount-SPContentDatabase -Name <DatabaseName> \u2013 databaseServer <ServerName> -WebApplicationURL<\/p>\n\n\n\n
SharePoint 2013 authentication mode is by default Claims mode, so during migration from any previous versions, make sure to migrate authentication from Classic to Claims mode. If the authentication type is Claims already, then ignore this step.<\/p>\n\n\n\n
Once the content database attachment process is over, we have to manually fix the below things:
\u2022 Migrate any List\/Site stp\u2019s present from previous version to next version
\u2022 Migrate InfoPath forms and change the url \u2019s to the new url and then publish forms
\u2022 Perform the Visual upgrade to get the look and feel of the next version
o Following are the commands used in PowerShell to do visual upgrade
o SharePoint 2010 visual upgrade using PowerShell<\/p>\n\n\n\n
$w = get-spweb http:\/\/server\/site
$w.webs | ForEach-Object {$_.UIversion = 4; $_.UIVersionConfigurationEnabled = $false; $_.update()}<\/p>\n\n\n\n
$web = Get-SPWeb http:\/\/server\/site
$web.UIVersion = 4
$web.UIVersionConfigurationEnabled = 0
$web.Update()
SharePoint 2013 visual upgrade using PowerShell
Upgrade-SPSite \u201chttp:\/\/server\/site\u201d \u2013VersionUpgrade<\/p>\n\n\n\n