How To Change Sharepoint Compatibility Mode To 14

SharePoint compatibility mode can be changed to version 14 by upgrading SharePoint 2010 mode sites to 2013 mode before mounting the database on SharePoint 2016. This process can be achieved using PowerShell commands to view and manage the upgrade settings for a web application or content database.

Site collection administrators have the ability to upgrade their own sites to SharePoint 2013, while server farm administrators have control over when and whether a site collection is upgraded. You can also control upgrade notifications and self-service upgrade settings for site collections.

Furthermore, you have the option to control the compatibility range for site creation modes, allowing you to specify which mode (2010 or 2013) can be used when creating a site collection. However, it is important to note that changing the compatibility level of User Profile Application databases is not supported.

By changing the compatibility level, you can minimize the time it takes to attach a content database to a destination SQL Server instance. This can greatly enhance your SharePoint experience and improve efficiency in managing and accessing your sites.

Upgrading SharePoint Sites to 2013 Mode

To change the compatibility mode to version 14, it is necessary to upgrade all SharePoint 2010 mode sites to 2013 mode before mounting the database on SharePoint 2016. This can be done using PowerShell commands to manage the upgrade settings for web applications or content databases. Site collection administrators have the ability to upgrade their own sites to SharePoint 2013, while server farm administrators have control over the timing and initiation of site collection upgrades.

By controlling the upgrade notifications and self-service upgrade settings for site collections, administrators can ensure a smooth transition to SharePoint 2013 mode. It is important to note that changing the compatibility level of User Profile Application databases is not supported.

Upgrading SharePoint Sites to 2013 Mode

When upgrading SharePoint sites to 2013 mode, there are a few key steps to follow:

  1. Before upgrading, ensure that all customizations and third-party solutions are compatible with SharePoint 2013.
  2. Use PowerShell commands to view and manage the upgrade settings for web applications or content databases.
  3. Site collection administrators can upgrade their own sites to SharePoint 2013, while server farm administrators have control over when and whether a site collection is upgraded.
  4. Control the upgrade notifications and self-service upgrade settings for site collections to manage the transition effectively.

By carefully following these steps, you can successfully upgrade your SharePoint sites to 2013 mode, improving the functionality and performance of your SharePoint environment.

Key Benefits of Upgrading to SharePoint 2013 Mode:
Improved collaboration and document management features
Enhanced search capabilities for better content discovery
Increased scalability and performance
Compatibility with the latest SharePoint features and updates

Controlling Compatibility Range and Creating Site Collections

Controlling the compatibility range of SharePoint site creation modes and managing site collections is crucial when changing the compatibility mode to version 14. By controlling the compatibility range, you can specify the mode (2010 or 2013) that can be used when creating a new site collection, ensuring a seamless transition.

However, it’s important to note that changing the compatibility level of User Profile Application databases is not supported. Therefore, it’s advisable to leave this aspect untouched to avoid any potential issues.

By managing site collections, you gain control over the upgrade process. As a site collection administrator, you have the ability to upgrade your own sites to SharePoint 2013. On the other hand, server farm administrators have the authority to decide when and whether a particular site collection should be upgraded.

When changing the compatibility mode, it may also be necessary to change the compatibility level to minimize the time it takes to attach a content database to a destination SQL Server instance. This optimization can greatly enhance efficiency and improve the overall SharePoint experience.

Meet the Author

Abdul Rahim has been working in Information Technology for over two decades. Learn how Abdul got his start as a Tech Blogger , and why he decided to start this Software blog. If you want to send Abdul a quick message, then visit his contact page here.