Migrating from SharePoint On-Premise to SharePoint Online often starts with frustration: ageing servers, high maintenance costs, and increasingly complex security updates. If you’re facing the same issues, then you are not alone. Many organizations mail us, saying that we are stuck at some point in the migration, and now what to do next. That’s why we created this step-by-step guide, which outlines how to migrate SharePoint On Premise to Online according to the versions, i.e, 2010, 2013, 2016, 2019, and SharePoint Server SE.
We provide a complete SharePoint on premise to online migration checklist to prevent common challenges throughout the transition. By the end of the discussion, we guarantee that you have all the answers related to this migration.
Table of Contents
Why Migrate SharePoint On Premise to Office 365?
Most of the organizations need to migrate data from on-premise to online, not due to trends, but out of necessity. The Microsoft 365 Copilot app provides various benefits, i.e,
- Lower infrastructure costs.
- Migrate SharePoint On Premise to Online for seamless integration with other Microsoft 365 services.
- Automatic updates and patches.
- Enhanced collaboration tools like Microsoft Teams, OneDrive, and SharePoint
- Improved remote access and real-time collaboration.
- Minimise the risk of data loss due to hardware failure.
- Enough cloud storage helps to free up the hard disk.
- Easy access to data from anywhere, on any device.
- Pay only for what you need, Office 365 comes with various plans.
Not only these, but there are more benefits to make this switch. Next, we will explore a comprehensive checklist to ensure a seamless transition.
Checklist to Migrate SharePoint On Premise to Online Hassle-free
Here are the step-by-step best practices that cover the entire SharePoint On Premise to online migration process from pre-migration to post-migration validation. Let’s see the visual diagram to understand quickly:
#Pre-Migration:
- Inventory sites, libraries, custom solutions, workflows, and permissions.
- Backup SharePoint Online to Local Storage.
- Choose the migration solutions from the list below.
- Define the scope and timeline. If possible, schedule the transition in off-peak hours to minimise downtime and productivity.
- Remove unused sites, unwanted content, and broken links to minimise the time of migration. Use SharePoint Duplicate Analysis Tool for quick results.
- Create target site collections and structure.
- Ensure enough space in the target to migrate content error-free.
- Set up user permissions and groups.
#Migration Phase Checklist
- First, migrate sample data or minimum files to prevent issues in the actual transition.
- Validate data integrity, structure, and permissions.
- Use incremental migration for large data sets.
- Watch logs and reports for issues to address errors (if they occur).
#Post-Migration Checklist
- Verify content, metadata, SharePoint Online Permissions, and version history.
- Inform users where to access the migrated content.
- When everything is done, plan for secure decommissioning(optional).
How to Migrate SharePoint On Premise to Online (Version-Specific Guide)
We researched and reviewed numerous articles on this topic, but we found that there is no precise knowledge or solution available online. That’s why we created the following sections, organized by SharePoint on-premise version, so users can easily identify their setup and proceed with the migration process.
This guide covers:
- SharePoint 2010
- SharePoint 2013
- SharePoint 2016
- SharePoint 2019
- SharePoint Server Subscription Edition (SE)
The details of the solutions for SharePoint On Premise to online migration are provided below:
Method 1. Using SPMT (SP 2010, 2013, 2016, 2019 & SE)
SPMT is a native solution designed by Microsoft to migrate SharePoint on premise to online. This helps in the transition of SharePoint data in the same tenant or online version. The latest version of SPMT supports SP 2010, 2013, 2016, 2019 & SE. Below is the official confirmation of these supported versions:
- Download & Install SPMT from Microsoft.
- Launch SPMT and sign in using your Microsoft 365 account.
- Select Source Location: Point to the on-prem document library or site path.
- Select Destination: Enter the SharePoint Online site URL.
- Map metadata and users (optional).
- Run the migration.
Now, wait until the migration completes. When a confirmation message is prompted, go to the destination and see if all the data has been migrated.
Note: The migration time depends on your data volume; it can take even a month to completely move data.
Method 2. Migrate SharePoint On Premise to Online Via Download & Upload (Supports All SP Versions)
We tried this solution, and it effectively works, but with a small volume of data. It seems time-consuming and becomes frustrating, which is why it is not recommended for organisations with large content. Still, you can see the guidelines for this:
- Open the source document library in Explorer View or download files.
- Upload content manually to the target SharePoint Online library.
- Reconfigure metadata, views, and permissions manually.
Note: It lacks to preserve version history and metadata.
Method 3. Using PowerShell & PnP PowerShell (Supports SP 2013 and Later)
This is an automated solution for SharePoint On Premise to online migration, and as SharePoint migration experts, we recommend it for organizations handling large volumes of data. However, it does not support 2010 directly. So we provide the steps below to upgrade from 2010 to 2013, as continuing to use SharePoint 2010 poses security and compatibility risks.
#SharePoint 2010
Perform Database-Attach Upgrade to SP 2013:
Mount-SPContentDatabase -Name "WSS_Content" -WebApplication http://sp2013webapp
Then use SP 2013 migration scripts (see below).
#SharePoint 2013 / 2016 / 2019 / SE to SharePoint Online
For this you need to install PnP PowerShell or Update SharePoint Online Management Shell. Setting up Execution Policy:
Set-ExecutionPolicy RemoteSigned
Note: This creates a .cmp package. It cannot be directly imported into SharePoint Online. You must re-upload content using PnP or a migration tool (like SPMT).
SharePoint On Premise to Online Migration Challenges & Solutions
Many users email us about issues they face while trying to migrate SharePoint on premise to online. Here are those with solutions:
- Custom web parts are not working in SharePoint Online.
Solution: Some users are facing this issue, and to resolve this, we suggest redeveloping using SPFx or Power Platform.
- Workflow compatibility issues, especially classic workflows.
Solution: For this query, the only option is to rebuild in Power Automate.
- Data volume limitations are causing timeouts.
Solution: Manual migration causes this issue; it is suggested to use the SPMT tool for better results.
- Metadata and permission mismatches during transfer.
Solution: This issue occurs because of the incorrect mapping of metadata and permissions. To fix this, ensure the mapping settings are correct, whether using SPMT or PowerShell.
- The user struggles to adopt the new modern UI.
Solution: Before migration, it is necessary to provide training to the users of SharePoint Online to unlock the full potential.
Final Thoughts
Migrating from SharePoint on-premises to online is a flawless task. With proper planning and the right tools, you can easily migrate SharePoint On Premise to Online simultaneously. If you’re planning your next move, refer back to this SharePoint on premise to online migration checklist to ensure any crucial steps won’t overlook.