Share Point 2010 to 2013 Up Gradation & Custmization Effect

SharePoint 2013 is the next Version of Microsoft’s famous Collaboration and Document Management Software called SharePoint. Below is some information given for up gradation effect of SP 2010 to  2013.

Note :The information is taken from MS Tech Net site.

Up gradation and customization Effect

The following table describes types of customizations and the kind of effect they can have during upgrade.

Category of customization	Types of customizations	Potential effect on upgrade
Visually-affecting	Master pages Themes Web Pages Web Parts Custom JavaScript Custom CSS files	Should not affect database upgrade. For site upgrades: likely to work well in 2010 mode, but need changes to work in 2013 mode. Test carefully in both modes.
Data structure affecting	Content types List types Web templates Site definitions	Can affect database upgrade if content or list type names conflict with new content or list types in the product, or if templates or definitions are missing.
Non-visually affecting	Web services Windows services HTTP handler HTTP module	Might not be compatible with SharePoint 2013. Test carefully to determine effect. Be prepared to remove or replace.

Up gradation Practice

• Ensure that the environment is fully functioning before you begin to upgrade.
• An upgrade does not solve problems that already exist in your environment. Therefore, make sure that the environment is fully functioning before you start to upgrade. For example, if you are not using web applications, unextend them before you upgrade. If you want to delete a web application in Internet Information Services (IIS), unextend the web application before you delete it. Otherwise, SharePoint 2013 will try to upgrade the web application even though it does not exist, and the upgrade will fail. If you find and solve problems beforehand, you are more likely to meet the estimated upgrade schedule.
• Perform a trial upgrade on a test farm first.
• Copy your databases to a test environment and perform a trial upgrade. Examine the results to determine the following:
• Whether the service application data was upgraded as expected
•  The appearance of upgraded sites
• The time to allow for post-upgrade troubleshooting
• The time to allow for the upgrade process
•  Try a full search indexing crawl. For more information, see Use a trial upgrade to SharePoint 2013 to find potential issues.
• Plan for capacity.
• Ensure that you have enough disk, processor, and memory capacity to handle upgrade requirements. For more information about system requirements, see System requirements for SharePoint 2013. For more information about how to plan the disk space that is required for upgrade, see Plan for performance during upgrade to SharePoint 2013 and Plan for performance and capacity management in SharePoint Server 2013
• Clean up before you upgrade
• Issues in your environment can affect the success of upgrade, and unnecessary or very large amounts of data can affect upgrade performance for both databases and site collections. If you don't need something in your environment, consider removing it before upgrade. If there are issues detected, try to resolve them before you start to upgrade. For more information, see Clean up an environment before an upgrade to SharePoint 2013.
•  Back up your databases.
•  Perform a full backup of your databases before you upgrade. That way, you can try upgrade again if it fails.
• Optimize your environment before upgrade.
•  Be sure to optimize your SharePoint 2010 Products environment to meet any limits or restrictions, either from your business or governance needs or from the SharePoint 2013 boundaries and limits before upgrade. This will help reduce errors during the upgrade process and prevent broken lists or sites after upgrade. For more information about limits in the product, see Software boundaries and limits for SharePoint 2013. For more information about large lists and how to address the lower limit on site collections, see Clean up an environment before an upgrade to SharePoint 2013.
•  (Optional) Set the original databases to read-only if you want to keep your original environment available while you upgrade.
• If you expect a long outage period while you upgrade, you can set the databases in the original environment to read-only. Users can continue to access the data but cannot change it. For more information, see Upgrade content databases to SharePoint 2013.
•  After upgrade, review the Upgrade Status page and upgrade logs to determine whether you must address issues. Then review the upgraded sites.
• The Upgrade Status page reports on the upgrade progress, and the upgrade logs list any errors or warnings that occurred during the upgrade process. Verify all the sites and test them before you consider the upgrade finished. For more information, see Verify database upgrades in SharePoint 2013 and Review site collections upgraded to SharePoint 2013.
• Defer upgrade for site collections until you can get updated customizations to support 2013 mode.
• If you wait until the customizations are available, you can complete the initial upgrade of database and services without significantly affecting use of the existing sites in 2010 mode.
• Make sure that the appropriate service pack or update is applied to your 2010 environment. If you are using remote blog storage (RBS) in your environment, you must be running Service Pack 1 for SharePoint 2010 Products in your environment before you start the upgrade process.