SharePoint Migration: A Step-by-Step Guide from SharePoint 2013 to SharePoint 2016

Introduction

Since its launch in 2001, Microsoft SharePoint has undergone significant evolution, transitioning from Windows SharePoint Services (WSS 3.0) to the latest version, SharePoint 2019. With each iteration, Microsoft has introduced advanced features to meet the growing demands of users and organizations. As a result, many organizations are upgrading from older versions to newer ones to leverage these improvements.

SharePoint migration generally falls into two categories:

1. Upgrading from one version of SharePoint to a higher version
2. Migrating from another Enterprise Content Management (ECM) system to SharePoint (e.g., from Lotus Notes)

In this guide, we'll focus on the first category: Upgrading from one version of SharePoint to a higher version, specifically from SharePoint 2013 to SharePoint 2016.

Migration Approaches

There are multiple ways to migrate to a newer version of SharePoint:

• Using Third-Party Tools: Tools like DocAve, Sharegate, and Metalogix (Quest) simplify the migration process with user-friendly interfaces and advanced features.
• Manual Migration (Native Migration Approach): This involves using built-in methods like in-place upgrades or the database attach method.

When choosing a migration approach, consider factors such as the need to restructure content, the ability to perform incremental migrations, cost implications, and the speed of migration. Third-party tools offer flexibility and advanced features but come with additional costs. Manual migration is cost-effective but may lack some functionalities and can be time-consuming, especially when skipping multiple versions.

Native Migration Approach: Step-by-Step

Migrating from SharePoint 2013 to SharePoint 2016 using the manual approach involves several key steps:

1. Analyze the SharePoint 2013 Farm

Before initiating the migration, it's crucial to assess the current SharePoint 2013 environment. Microsoft provides the SharePoint Migration Assessment Tool (SMAT) for this purpose. SMAT scans the farm and generates comprehensive reports, including:

• SharePoint version and Farm ID
• Number of sites and overall size
• Custom solutions and features
• Potential migration issues

These reports help identify areas that may require attention during the migration process.

2. Clean Up the SharePoint 2013 Environment

Performing a cleanup of the existing SharePoint 2013 sites is an optional but recommended step. Removing unused content, solutions, or features that are no longer needed can simplify the migration and result in a cleaner, more efficient SharePoint 2016 environment.

3. Backup Content Databases and Custom Solutions

Create backups of your content databases and any custom solutions:

• Content Databases: Use SQL Server Management Studio to back up the content databases from the SharePoint 2013 environment.
• Custom Solutions: Export any custom-developed solutions or features that need to be available in the new environment.

4. Restore Content Databases to SharePoint 2016

In the SharePoint 2016 environment:

• Restore Databases: Use SQL Server Management Studio to restore the backed-up content databases.
• Prepare for Mounting: Ensure that the restored databases are ready to be attached to the new SharePoint 2016 web application.

5. Create a New Web Application in SharePoint 2016

Set up a new web application in SharePoint 2016. If your SharePoint 2013 web application used specific managed paths or site collections, replicate these in the new environment to maintain consistency.

6. Attach the Restored Databases

Attach the restored content databases to the new web application:

• Detach Existing Databases: If there are any default content databases associated with the new web application, detach them to avoid conflicts.
• Attach Restored Databases: Attach the restored SharePoint 2013 content databases to the SharePoint 2016 web application.
• Upgrade Process: SharePoint will automatically perform an upgrade process on the content databases to align them with the 2016 schema and features.

7. Test and Verify the Migration

After attaching the databases:

• Check for Issues: Review any logs or reports generated during the upgrade process to identify and resolve issues.
• Test Functionality: Navigate through the migrated sites to ensure that content, features, and functionalities are working as expected.
• Identify Missing Customizations: If certain features or customizations are missing, note them for the next step.

8. Deploy Custom Solutions

Deploy any custom solutions or features that were part of your SharePoint 2013 environment:

• Add Custom Solutions: Import custom solution packages into the SharePoint 2016 farm.
• Install and Deploy: Install the solutions to the appropriate web applications or site collections.
• Activate Features: Activate any necessary features to restore full functionality.

9. Final Testing and Validation

Conduct thorough testing to validate the success of the migration:

• User Acceptance Testing: Involve end-users to test the migrated environment and provide feedback.
• Performance Checks: Monitor system performance to ensure that the new environment meets organizational requirements.
• Documentation: Document any changes or issues encountered during the migration for future reference.

Conclusion

Migrating from SharePoint 2013 to SharePoint 2016 using the manual approach is a detailed process that requires careful planning and execution. By following these steps, organizations can successfully upgrade their SharePoint environments without incurring the additional costs associated with third-party tools.

We hope this guide assists you in your SharePoint migration journey. Your feedback and suggestions are welcome to help us improve future guides.

‍