SharePoint Server 2007 end of support roadmap

This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.

On October 10, 2017, Microsoft Office SharePoint Server 2007 reached end of support. If you haven't migrated from SharePoint Server 2007 to Microsoft 365 or a newer version of SharePoint Server on-premises, now's the time to start planning. This article provides resources to help you migrate data to SharePoint Online or upgrade your SharePoint Server on-premises.

What does end of support mean?

SharePoint Server, like most Microsoft products, has a support lifecycle, during which Microsoft provides new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the product's initial release. The end of this lifecycle is known as the product's end of support. After the end of support, Microsoft no longer provides:

  • Technical support for problems that may occur.

  • Bug fixes for issues that may impact the stability and usability of the server.

  • Security fixes for vulnerabilities that may make the server vulnerable to security breaches.

  • Time zone updates.

Your SharePoint Server 2007 farm will still be operational after October 10, 2017, but no further updates, patches, or fixes will be released for the product, including security patches/fixes. Microsoft Support has fully shifted its support efforts to more-recent versions of the product. Because your installation is no longer supported or patched, you should upgrade the product or migrate important data.

Tip

If you haven't already planned for upgrade or migration, see: SharePoint 2007 migration options to consider for some examples of where to begin. You can also search for Microsoft Partners who can help with upgrade or Microsoft 365 migration (or both).

For more information about Office 2007 servers and the end of support, see Resources to help you upgrade from Office 2007 servers and clients.

What are my options?

Your first stop should be the Product Lifecycle site. If you have an on-premises Microsoft product that's aging, check its end of support date so that you have a year or so to schedule an upgrade or migration. When you choose the next step, consider what product features would be good enough, better, and best. Here's an example:

Good Better Best
SharePoint Server 2010
SharePoint Server 2013
SharePoint Online
SharePoint Hybrid
SharePoint Server 2016
SharePoint Hybrid

If you choose a "good enough" option, you'll soon need to begin planning for another upgrade after migration from SharePoint Server 2007 is completed.

Note

End-of-support dates are subject to change. Check the Product Lifecycle site.

Where can I go next?

SharePoint Server can be installed on-premises on your own servers. Or you can use SharePoint Online, which is an online service that's part of Microsoft 365. Your options are:

  • Migrate to SharePoint Online.

  • Upgrade SharePoint Server on-premises.

  • Do both of the above.

  • Implement a SharePoint hybrid solution.

Be aware of hidden costs associated with maintaining a server farm, maintaining or migrating customizations, and upgrading the hardware that SharePoint Server needs. Having an on-premises SharePoint Server farm is rewarding if it's necessary. But if you run your farm on legacy SharePoint Servers without heavy customization, you can benefit from migration to SharePoint Online.

Important

There's another option if the content in SharePoint 2007 is infrequently used. Some SharePoint Administrators choose to create a Microsoft 365 subscription, set up a new SharePoint Online site, and then cut away from SharePoint 2007 cleanly, taking only essential documents to the fresh SharePoint Online sites. Data can then be drained from the SharePoint 2007 site into archives. Consider how your users work with data from your SharePoint 2007 installation. There may be creative ways to manage your needs.

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 + devs/admins)
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 Microsoft 365, the one-time move will have a heavier cost up-front, while you organize data and decide what to take to the cloud and what to leave behind. But future upgrades will be automatic, and you'll no longer need to manage hardware and software updates. Also, the up time of your farm will be backed by a Microsoft Service Level Agreement (SLA).

Migrate to SharePoint Online

Make sure that SharePoint Online has all the features you need. See Microsoft 365 and Office 365 service descriptions.

You can't migrate directly from SharePoint 2007 to SharePoint Online. Your move to SharePoint Online would be done manually. If you upgrade to SharePoint Server 2013 or SharePoint Server 2016, you might use the SharePoint Migration API (to migrate information into OneDrive for Business, for example).

Online pro Online con
Microsoft supplies SPO hardware and all hardware administration.
Available features may differ between SharePoint Server on-premises and SPO.
You're the global administrator of your subscription and can assign administrators to SPO sites.
Some actions available to a farm administrator in SharePoint Server on-premises don't exist or aren't necessarily included in the SharePoint Administrator role in Microsoft 365.
Microsoft applies patches, fixes, and updates to underlying hardware and software.
Because there's no access to the underlying file system in the service, customization is 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.
Microsoft 365 meets many industry standards: Microsoft compliance offerings.
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.
Microsoft Support engineers and datacenter employees won't have unrestricted admin access to your subscription.
There can be additional costs if hardware 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.
Online products are updated automatically. Although features may deprecate, there's no true end of support.

If you've decided to create a new Microsoft 365 site and will manually migrate data to it as is needed, check your Microsoft 365 options.

Upgrade SharePoint Server on-premises

There's no way to skip versions in SharePoint Upgrades. Upgrades go serially:

  • SharePoint 2007 > SharePoint Server 2010 > SharePoint Server 2013 > SharePoint Server 2016

To go from SharePoint 2007 to SharePoint Server 2016 means a significant investment of time and will involve costs in hardware (SQL servers must also be upgraded), software, and administration. Customizations will need to be upgraded or abandoned.

Note

It's possible to maintain your end-of-life SharePoint 2007 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). But beware of some of the pitfalls of manual moves, such as moves of documents replacing the last-modified account with the alias of the account doing the manual move. Also consider the work that must be done ahead of time, such as recreating sites, subsites, permissions, and list structures. Consider in advance what data you can move into storage or delete to reduce the impact of migration.

It's important to clean up your environment before you upgrade. Be certain your existing farm is functional before you upgrade, and certainly before you decommission!

Remember to review the supported and unsupported upgrade paths:

If you have customizations, it's critical to have a plan for each step in the migration path:

On-premises pro On-premises con
Full control of all aspects of your SharePoint Farm, from the server hardware up.
All breaks and fixes are the responsibility of your company (you can engage paid Microsoft Support if your product is not past 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, and all maintenance of SharePoint Server managed on-premises.
Full access for greater customization.
Microsoft compliance offerings must be manually configured on-premises.
Security testing, and server performance tuning is carried out on your premises (under your control).
Microsoft 365 may make features available to SharePoint Online that don't 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 won't automatically use SSL/TLS certificates as is seen in SharePoint Online.
Full control of naming conventions, back up and restore, and other recovery options in SharePoint Server on-premises.
SharePoint Server on-premises is sensitive to product lifecycles.

Upgrade resources

Make sure your environment meets hardware and software requirements, and then follow supported upgrade methods.

Create a SharePoint hybrid solution between SharePoint Online and on-premises

If the answer to your migration needs is somewhere between the self-control offered by on-premises and the lower cost of ownership offered by SharePoint Online, you can connect SharePoint Server 2013 or 2016 farms to SharePoint Online through hybrids. Learn about SharePoint hybrid solutions.

If you decide that a hybrid SharePoint Server farm will benefit your business, familiarize yourself with the existing types of hybrids and how to configure the connection between your on-premises SharePoint farm and your Microsoft 365 subscription.

Option Description
Microsoft compliance offerings
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.
Microsoft Support engineers and data center employees don't 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.
Online products are updated automatically across the service. Though features may deprecate, there's no true end of support.

If you've decided to create a new Microsoft 365 site and will manually migrate data to it as is needed, check your Microsoft 365 options.

Upgrade SharePoint Server on-premises

There's no way to skip versions in SharePoint Upgrades. Upgrades go serially:

  • SharePoint 2007 > SharePoint Server 2010 > SharePoint Server 2013 > SharePoint Server 2016

To go from SharePoint 2007 to SharePoint Server 2016 will mean a significant investment of time and will involve costs for hardware (SQL servers must also be upgraded), software, and administration. Customizations will need to be upgraded or abandoned.

Note

It's possible to maintain your end-of-life SharePoint 2007 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). But beware of potential pitfalls of manual moves, such as moves of documents replacing the last-modified account with the alias of the account doing the manual move, and the work that must be done ahead of time, such as recreating sites, subsites, permissions and list structures. Consider what data you can move into storage or delete to reduce the impact of migration.

Clean your environment prior to upgrade. Be certain your existing farm is functional before you upgrade and certainly 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, from the server hardware up.
All breaks and fixes are the responsibility of your company. (You can engage paid Microsoft Support if your product isn't past 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, and all maintenance of SharePoint Server managed on-premises.
Full access for greater customization.
Microsoft compliance offerings must be manually configured on-premises.
Security testing and server performance tuning are carried out on your premises under your control.
Microsoft 365 may make features available to SharePoint Online that don't interoperate with SharePoint Server on-premises
Partners can help migrate 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, back up and restore, and other recovery options in SharePoint Server on-premises.
SharePoint Server on-premises is sensitive to product lifecycles.

Upgrade resources

Make sure that your environment meets hardware and software requirements. Then follow the supported upgrade methods.

Create a SharePoint hybrid solution between SharePoint Online and on-premises

If the answer to your migration needs is somewhere between the self-control offered by on-premises and the lower cost of ownership offered by SharePoint Online, you can connect SharePoint Server 2013 or 2016 farms to SharePoint Online through hybrids. Learn about SharePoint hybrid solutions

If you decide that a hybrid SharePoint Server farm will benefit your business, familiarize yourself with the existing types of hybrids and how to configure the connection between your on-premises SharePoint farm and your Microsoft 365 subscription.

One good way to see how this works is to create a Microsoft 365 dev/test environment, which you can set up with Test Lab Guides. After you get a trial or purchased Microsoft 365 subscription, you can create the site collections, webs, and document libraries in SharePoint Online to which you can migrate data. You can migrate manually, by use of the Migration API, or, if you want to migrate My Site content to OneDrive for Business, through the hybrid wizard.

Note

Remember that to use the hybrid option, your SharePoint 2007 farm will need to be upgraded, on-premises, to either SharePoint Server 2013 or SharePoint Server 2016.

Troubleshoot and resume upgrade (Office SharePoint Server 2007)

Troubleshoot upgrade issues (SharePoint Server 2010)

Troubleshoot database upgrade issues in SharePoint 2013

Search for Microsoft Partners to help with Upgrade

Resources to help you upgrade from Office 2007 servers and clients