SharePoint migration from 2013 to 2016

It's a euphoric moment that SharePoint 2016 is here with loads for out-of-the-box features. Migration to SharePoint 2016 as well is quite an easy process. To do this, all you need is transfer the data from SharePoint 2013 single server farm to newly introduced SharePoint 2016 farm. SharePoint 2013 content database will be mounted against a production ready web application.

Here are few Advantages of SharePoint 2016 over SharePoint 2013

User Improvements
  • >> Support for Open Office Documents.
  • >> Files shared via Durable Links will reference a site ID and document ID, so renamed or moved files will not result in broken links.
  • >>File name length and other character restrictions are being removed.

System Improvements
  • >> Optimizations within the server roles to reduce latency and traffic between servers.
  • >>Reliability improvements to Distributed Cache (still relies on AppFabric 1.1 and will continue to be supported for SharePoint 2013 and 2016's lifecycles)
  • >>SharePoint Logging API (SLAPI) allows easier ability to record and report on analytics and telemetry across a whole range of objects in the Farm.

Hybrid Improvements
  • >>eDiscovery and Legal Hold will now traverse SharePoint Online in O365.
  • >> Search Service can query SharePoint Online in O365 and provide a single ranked results set with integrated relevancy (no separate verticals).
  • >>Consolidation of Social features to ensure followed on premise and online content appears in a single social profile.
  • Delve and Office Graph API can surface content from on premise services along with content in O365 (will be released for 2013 this year) .
  • Item level encryption using Azure AD Rights Management Services .

Patching Improvements
  • >> Patches will be much smaller – currently 37 MSIs and down to 4 MSIs in a single patch.
  • >> Can be applied to servers online with zero downtime to the Farm and no disruption to the users, but HA needs to be there.

Scalability Improvements
  • >> Content DBs will scale into TBs .
  • >>100,000 Site Collections per database
  • >>List view threshold will reach >5,000 items
  • Maximum upload size has increased from 2GB to 10GB

Performance Improvements
  • >>500 million maximum items per search index partition (was 10 million).
  • >>BITS now replacing FSS over HTTP and Cobalt to reduce IO between servers and bandwidth to the end user.
  • >>Traffic Management endpoint automatically routes user requests based on server health.


By continuing to navigate on this website, you accept the use of cookies. For more information, please read our  Privacy Policy.         X