Upgrading from SharePoint 2010
On Oct 13, 2020, Microsoft Office SharePoint Server 2010 reaches end of support. This article details resources to help people migrate their existing SharePoint Server 2010 data to SharePoint Online, or upgrade your SharePoint Server on-premises.
What is end of support?
When your SharePoint Server 2010, and SharePoint Foundation 2010 software reaches the end of its support lifecycle (the time during which Microsoft provides new features, bug fixes, security fixes, and so on) this is called the software's 'end of support', or, sometimes, its 'Retirement'. Upon the end of support (or EOS) of a product, nothing actually shuts down or stops working; however, at the end of support of software, Microsoft no longer provides:
Technical support for problems that may occur;
Bug fixes for issues that are discovered and that may impact the stability and usability of the server;
Security fixes for vulnerabilities that are discovered and that may make the server vulnerable to security breaches;
Time zone updates.
That means, there will be no further updates, patches, or fixes will be shipped for the product (including security patches/fixes), and Microsoft Support will have fully shifted its support efforts to more recent versions. As the end of support of SharePoint Server 2010 approaches, you should take advantage of opportunities to trim data you no longer need prior to upgrading the product, and/or migrating your important data.
A software lifecycle typically lasts for 10 years from the date of the product's initial release. You can search for Microsoft Partners who can help with upgrade to the next version of your software, or with Office 365 migration (or both). Be certain you're aware of end of support dates on critical underlying technologies as well, particularly of the version of SQL server you're using with SharePoint.
What are my options?
First, check the date at which support ends on the Product Lifecycle site. Next, be sure to plan your upgrade or migration time with knowledge of this date. Remember that your product won't stop working at the date listed, and you can continue its use, but that, since your installation will no longer be patched after that date, you'll want a strategy that will help you more smoothly transition to the next version of the product.
This matrix helps plot a course when it comes to migrating product features and user data:
|end of support product||Good||Best|
|SharePoint Server 2010
||SharePoint Server 2013
||SharePoint Server 2016 (on-premises)
|SharePoint Cloud Hybrid Search
If you choose options on the low end of the scale (good options), you'll need to start planning for another upgrade soon after migration from SharePoint Server 2010 completes. (end of support for SharePoint Server 2010 and SharePoint Foundation 2010 are scheduled for Oct 13, 2020, but please be aware you should always check the Product Lifecycle site for your most accurate dates!)
Where should I go next?
SharePoint Server 2013 and SharePoint Foundation 2013 can be installed on-premises on your own servers. Otherwise, you can use SharePoint Online, which is an online service that is part of Microsoft Office 365. You can choose to:
Migrate to SharePoint Online
Upgrade SharePoint Server or SharePoint Foundation on-premises
Do both of the above
Implement a SharePoint hybrid solution
Be aware of hidden costs associated with maintaining a server farm going forward, maintaining or migrating customizations, and upgrading the hardware upon which SharePoint Server depends. If you're aware and have accounted for all of these, it will be easier to continue upgrading on-premises. Otherwise, if you run your farm on legacy SharePoint Servers without heavy customization, you could benefit from a planned migration to SharePoint Online. It's also possible that on-premises SharePoint Server shops might opt to put some data in SharePoint Online to reduce the amount of hardware management keeping all their data on-premises involves. It may be more economical to move some of your data into SharePoint Online.
SharePoint Administrators may create an Office 365 Subscription, set up a brand new SharePoint Online site, and then cut away from SharePoint Server 2010, cleanly, taking only the most essential documents to the fresh SharePoint Online sites. From there, any remaining data may be drained from the SharePoint Server 2010 site into on-premises archives.
|SharePoint Online (SPO)||SharePoint Server on-premises|
|High cost in time (plan / execution / verification)
||High cost in time (plan / execution / verification)
|Lower cost in funds (no hardware purchases)
||Higher cost in funds (hardware purchases)
|One-time cost in migration
||One-time cost repeated per future migration
|Low total cost of ownership / maintenance
||High total cost of ownership / maintenance
When you migrate to Office 365, the one-time move will have a heavier cost in time spent planning, up-front (while you're organizing data and deciding what to take to the cloud and what to leave behind). However, once your data is migrated, upgrades will be automatic from that point, seeing as you will no longer need to manage hardware and software updates, and the up-time of your farm will be backed by a Microsoft Service Level Agreement (SLA).
Migrate to SharePoint Online
Be sure SharePoint Online offers all the features you need by reviewing the associated service description. Here's the link to all Office 365 Service Descriptions:
There isn't currently a means by which you can directly migrate from SharePoint Server 2010 (or SharePoint Foundation 2010) to SharePoint Online, so much of the work is manual. This does give you the opportunity to archive and prune data and sites that are no longer needed, before the move. You can archive other data into storage. Also remember that neither SharePoint Server 2010 nor SharePoint Foundation 2010 will stop working at end of support, so administrators can have a period during which SharePoint is still running if their customers forget to move some of their data.
If you upgrade to SharePoint Server 2013 or SharePoint Server 2016, and decide to put data into SharePoint Online, your move might also involve using the SharePoint Migration API (to migrate information into OneDrive for Business).
|Online Pro||Online Con|
|Microsoft supplies SPO hardware and all hardware administration.
||Available features may be different between SharePoint Server on-premises and SPO.
|You are the global administrator of your subscription, and may assign administrators to SPO sites.
||Some actions available to a Farm Administrator in SharePoint Server on-premises do not exist (or are not necessary) in the SharePoint Administrator role in Office 365, but SharePoint Administration, Site Collection Administration, and Site Ownership are local to your org.
|Microsoft applies patches, fixes and updates to underlying hardware and software (including SQL servers on which SharePoint Online runs).
||Because there is no access to the underlying file system in the service, some customizations are limited.
|Microsoft publishes Service Level Agreements and moves quickly to resolve service level incidents.
||Backup and restore and other recovery options are automated by the service in SharePoint Online - backups are overwritten if not used.
|Security testing and server performance tuning are carried out on an ongoing basis in the service by Microsoft.
||Changes to the user interface and other SharePoint features are installed by the service and may need to be toggled on or off.
|Office 365 meets many industry standards: Office 365 Compliance.
||FastTrack assistance for migration is limited.
Much of the upgrade will be manual, or via the SPO Migration API described in the SharePoint Online and OneDrive Migration Content Roadmap.
|Neither Microsoft Support Engineers nor employees in the datacenter have unrestricted admin access to your subscription.
||There can be additional costs if hardware infrastructure needs to be upgraded to support the newer version of SharePoint, or if a secondary farm is required for upgrade.
|Partners can assist with the one-time job of migrating your data to SharePoint Online.
||Not all changes to SharePoint Online are within your control. After migration, design differences in menus, libraries, and other features may temporarily affect usability.
|Online products are updated automatically across the service meaning that though features may deprecate, there is no true end of support Lifecycle.
||There is an end of support Lifecycle for SharePoint Server (or SharePoint Foundation) as well as underlying SQL servers.
If you've decided to create a new Office 365 site, and will manually migrate data to it as is needed, you can look at your Office 365 options right here:
Upgrade SharePoint Server on-premises
As of the latest version of the SharePoint on-premises product (SharePoint Server 2016), SharePoint Server upgrades must go serially , that means there is no way to upgrade from SharePoint Server 2010 to SharePoint Server 2016, directly.
|Serial upgrade path: SharePoint Server 2010 > SharePoint Server 2013 > SharePoint Server 2016|
If you choose to follow the entire path from SharePoint 2010 to SharePoint Server 2016, this will take time and planning. Upgrades involve a cost in terms of upgraded hardware (be aware that SQL servers must also be upgraded), software, and administration. Also, customizations may need to be upgraded, or even abandoned. Be sure that you collect notes on all of your critical customizations before you upgrade your SharePoint Server farm.
It's possible to maintain your end of support SharePoint 2010 farm, install a SharePoint Server 2016 farm on new hardware (so the separate farms run side-by-side), and then plan and execute a manual migration of content (for downloading and re-uploading content, for example). There are potential pitfalls to these manual moves (such as documents coming from 2010 having a current last modified account with the alias of the account doing the manual move), and some work must be done ahead of time (recreating sites, sub-sites, permissions and list structures). It's a good time to consider what data you can move into storage, or no longer need. This can reduce the impact of migration. Either way, clean your environment prior to upgrade. Be certain your existing farm is functional before you upgrade, and (for sure) before you decommission!
Remember to review the supported and unsupported upgrade paths:
If you have customizations, it's critical you have a plan your upgrade for each step in the migration path:
|On-premises Pro||On-premises Con|
|Full control of all aspects of your SharePoint Farm (and it's SQL), from the server hardware up.
||All breaks and fixes are the responsibility of your company (but you can engage paid Microsoft Support if your product is not at end of support):
|Full feature set of SharePoint Server on-premises with the option to connect your on-premises farm to a SharePoint Online subscription via hybrid.
||Upgrade, patches, security fixes, hardware upgrades, and all maintenance of SharePoint Server and it's SQL farm are managed on-premises.
|Full access for greater customization options than with SharePoint Online.
||Compliance standards supported by Office 365 must be manually configured on-premises.
|Security testing, and server performance tuning, carried out on your premises (under your control).
||Office 365 may make features available to SharePoint Online that do not interoperate with SharePoint Server on-premises
|Partners can assist with migrating data to the next version of SharePoint Server (and beyond).
||Your SharePoint Server sites will not automatically use SSL/TLS certificates as is seen in SharePoint Online.
|Full control of naming conventions, backup and restore and other recovery options in SharePoint Server on-premises.
||SharePoint Server on-premises is sensitive to Product Lifecycles.
Begin by comparing hardware and software requirements. If you don't meet basic requirements for the upgrade on current hardware, that can mean you need to upgrade the hardware in the farm or SQL servers first, or that you may decide to move some percentage of your sites to the 'evergreen' hardware of SharePoint Online. Once you've made your assessment, follow supported upgrade paths and methods.
Hardware/software requirements for:
Software boundaries and limits for:
The upgrade process overview for:
Create a SharePoint hybrid solution between SharePoint Online and SharePoint Server on-premises
Another option (one that may be the best of both on-premises and online worlds for some migration needs) is a hybrid, you can connect SharePoint Server 2013 or 2016 farms to SharePoint Online to create a SharePoint hybrid: Learn about SharePoint hybrid solutions.
If you decide a hybrid SharePoint Server farm is your migration goal, be sure to plan what sites and users you should move to online, and which need to remain on-premises. A review and ranking of your SharePoint Server farm's content (determining what data is High, Medium, or Low impact to your company) can be helpful to making this decision. It may be that the only thing you need to share with SharePoint Online is (a) user accounts for login, and (b) the SharePoint Server search index -- this may not be clear until you look at how your sites are used. If your company later decides to migrate all of your content to SharePoint Online, you can move all remaining accounts and data online and decommission your on-premises farm, and management/administration of the SharePoint farm will be done through Office 365 consoles from that point on.
Be sure to familiarize yourself with the existing types of hybrid and how to configure the connection between your on-premises SharePoint farm and your Office 365 subscription.
One good way to see how a hybrid SharePoint farm works is by creating an Office 365 dev/test environment. Once you have a trial or purchased Office 365 subscription, you'll be on your way to creating the site collections, webs, and document libraries in SharePoint Online to which you can migrate data (either manually, by use of the Migration API, or - if you want to migrate My Site content to OneDrive for Business - through the hybrid wizard).
Remember that your SharePoint Server 2010 farm will first need to be upgraded, on-premises, to either SharePoint Server 2013 or SharePoint Server 2016 to use the hybrid option. SharePoint Foundation 2010 and SharePoint Foundation 2013 cannot create hybrid connections with SharePoint Online.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.