Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

3.
Plan how you intend to meet the time and
space requirements for the migration
• You will need a large database to upgrade SQL,
content databases, Site Settings, customizations,
Web Parts, Workflows, etc.
• Hence create double or triple the size of the
existing SharePoint 2010 database as it will
reduce the time needed, as well as help in
managing changes after the upgrade
• Schedule your tests and upgrades during off-
peak hours

4.
Perform dry runs, test the results and repeat
the dry runs till satisfied
• Always execute dry runs to identify upgrade
bottlenecks
• Identify the points where upgrade can seize up,
test the level of end user functionality after the
upgrade, check areas that need to be mapped
properly in order to assign correct permissions,
check shortcomings that need to be rectified in
order to bring the data up-to-date, etc.

5.
Identify and prioritize
SharePoint 2010 customizations
• Identify and clearly map user defined
customization so that subsequent to the
upgrade, SharePoint 2013 users can continue to
work as usual
• Identify all the Custom Content
Types, Workflows, Web
Applications, Themes, Document
Templates, Lists, Metadata columns, public
URLs, Site Collections, Web Parts and all the
possibilities in the Site Content

6.
Use PowerShell scripts if and
wherever necessary
• Tasks like attaching the databases or mounting
them are better performed through scripts