Introduction to SharePoint 2013 Migration:
If you want migrate SP2010 to SP2013,you need to follow the below steps.
To identify and evaluate the customizations in your environment, and determine whether you will upgrade them, and how.
- Remove the Old Version(Previous) of SharePoint
- Use your existing Hardware
-> Uninstall Old SharePoint version and other dependent products
More References on Hardware and Software Requirements
Hardware and Software Requirements
End Client Software Requirements
Office 2010 or Office 2013
==>Full Offline and integrated experience
==>SPD 2010 only works for SP version 14 sites
==>SPD 15 works for both SP versions 14 and 15 sites
==>Internet Explorer 8 or higher
==>Firefox (Latest version)
==>Chrome (Latest version)
==>Apple Safari (Latest version)
1) Content Database(When you upgrade from SharePoint 2010 Products to SharePoint 2013, you must use a database attach upgrade, which means that you upgrade only the content for your environment and not the configuration settings. After you have configured the SharePoint 2013 environment, copied the content and service application databases, and upgraded the service applications, you can attach and upgrade the content databases to SharePoint 2013.)
Supported Databases for Database Attach Method
a). Content Databases
b). Project Databases
c). Search Admin Databases
d). Profile Databases
e). Social Databases
f). Managed Metadata Databases
g). Secure Store Databases
h). Access Databases
Unsupported Databases for Database Attach Method
a). Configuration Databasesb). Sync Databases c). Search Index Databases
2)In-place Upgrade(An upgrade to SharePoint Server 2010 or SharePoint Foundation 2010 provides an option to install the new version over the earlier version on the same hardware. This is called an in-place upgrade.SharePoint 2013 does not support in-place upgrade for an existing environment.).
Prepare new environment
a). Install and configure SharePoint 2013 and any language packs
b). Configure service applications
c). Configure general farm settings
Click here for Create SharePoint New form
Back up and restore databases
a). Record the passphrase for the Secure Store service application
b). Set the previous version databases to be read-only
c). Back up databases
d). Export the encryption key for the User Profile service application
e). Restore a backup copy of the databases
f). Set the restored databases to be read-write
Click here for backup and restore steps.
Upgrade service application databases
a). Start the service application instances
b). Upgrade the Secure Store service application
c). Upgrade the Business Data Connectivity service application
d). Upgrade the Managed Metadata service application
e). Upgrade the User Profile service application
f). Upgrade the PerformancePoint Services service application
g). Upgrade the Search service application
h). Verify that all of the new proxies are in the default proxy group
Click here for upgrade service application
Create web applications
a). Create and configure web applications
b). Reapply server-side customizations
c). Verify custom components
List down all customization
Attach and upgrade content databases
a). Attach a content database to a web application
b). Verify upgrade for the first database
c). Attach remaining databases
d). Monitor upgrade progress
e). Monitor upgrade progress
f). Verify upgrade for the remaining database
Plan Upgrade Performance
Complete post-upgrade steps
a). Verify that site collections are working as expecting in 2010 mode
b). Migrate user accounts to claims authentication, if it is necessary
c). Update links that are used in any upgraded InfoPath form templates
d). Configure your Search topology
e). Start a full crawl
f). Back up your farm
Migrate Content Database, Service Application Databases & Site Collections to SharePoint 2013 Using Power Shell Commands
STSADM Comand tool does not support SharePoint 2013
securityadmin fixed server role on the SQL Server instance.
db_owner fixed database role on all databases that are to be updated.
Please Verify that the user account member of the db_owner fixed database role for the databases.
a). Mount-SPContentDatabase -Name DatabaseName -DatabaseServer ServerName -WebApplication URL
DatabaseName is the name of the database that you want to upgrade.
ServerName is server on which the database is stored.
URL is the URL for the web application that will host the sites.
b). Test-SPContentDatabase -Name DatabaseName -WebApplication URL
DatabaseName is the name of the database that you want to test.
URL is the URL for the web application that will host the sites.
Deferred Site Collection Upgrade
-->It is the replacement of Visual Upgrade feature
-->Visual upgrade preserves old master pages, CSS and HTML files only where deferred site
collection upgrade preserves many things, even Features.
-->This upgrade allows you to use previous version of SharePoint UI seamlessly.
-->Main difference – Site Collection (SPSite) UI will be upgraded granularity instead of Site
“Once the site collection is upgraded then it cannot be rolled back.”
Customizations and SharePoint 2013 User Experience
Back-end Service Applications
3rd Party Customizations
SharePoint 2013 User Experience
SP Mode 14
SP Mode 15
SharePoint 2013 can host sites in both SharePoint 2010 Products and SharePoint 2013 modes. The installation for SharePoint 2013 contains both SharePoint 2010 Products and SharePoint 2013 versions of many elements. The directories on the file system are duplicated in both the 14 and 15 paths, for example:
Web Server Extensions/14/TEMPLATE/Features
Web Server Extensions/15/TEMPLATE/Features
There are also two versions of the IIS support directories: _Layouts, _Layouts/15 and _ControlTemplates, _ControlTemplates/15.
Be sure to install customizations to the correct location in your new farm. For example, additional style sheets for SharePoint 2010 Products should be installed in the /14 path, not the new /15 path so that site collections that you haven’t upgraded can use them. If you want a solution to be available to both paths, install it two times, and the second time use the CompatibilityLevel parameter when you install it, and it will be installed to the /15 path.
Reapply all customization:
During upgrade is that the new environment does not have customized features, solutions, or other elements. Make sure that all custom elements from the SharePoint 2010 Products environment are installed on your front-end web servers before you upgrade any content databases.
Manually transfer all customizations to your new farm. Make sure to install any components that your sites depend on to work correctly, such as the following:
->Custom site definitions
->Custom style sheets, such as cascading style sheets, and image
->Custom Web Parts
->Custom Web services
->Custom features and solutions
->Web.config changes (such as security)
Ensure that you transfer all unique settings from the Web.config files for each web application to the new servers.
Click Here For more information SPSolution
->Administrator-approved form templates (.xsn files) and data connection files (.udcx files) for InfoPath. InfoPath is available in SharePoint Server 2010 only.
->Any other components or files on which your sites depend.
Verify the Upgrade Status:
After attaching a database, use the Upgrade Status page in Central Administration to check the status of upgrade on databases. After the upgrade process is complete, review the upgrade log file to see whether upgrade produced issues, use a Windows PowerShell cmdlet to check the upgrade status for all the content databases.
Click here for more Information
Upgrade error log file and the upgrade log file are located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\15\LOGS. and also check the event logs.
The upgrade log file contains more detailed information than the upgrade error log.
The logs are text files named in the following format:
YYYYMMDD is the date
HHMMSS-SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds)
How to Migrate from MOSS 2007 to SharePoint 2013?
It is Possible...
There is no need to stop at SharePoint 2010
Fact – “There is no direct migration from MOSS 2007 to SharePoint 2013”
First thing Migrate Moss 2007 Farm/Web Application to SharePoint 2010 Farm/Web Application then you can migrate to SP2010 Farm/Web Application to SharePoint 2013 Farm/Web Application