Project Server 2010 end of support roadmap

Project Server 2010 will reach end of support on October 13, 2020. If you are currently using Project Server 2010, note that these other related products have the following end of support dates:

Product end of support date
Project Portfolio Server 2010
October 13, 2020
Project 2010 Standard
October 13, 2020
Project 2010 Professional
October 13, 2020

For more information about Office 2010 servers reaching end of support, see Upgrade from Office 2010 servers and client products.

What does end of support mean?

Project Server, like almost all Microsoft products, has a support lifecycle during which we provide new features, bug fixes, and security updates. This lifecycle typically lasts for 10 years from the date of the product's initial release, and the end of this lifecycle is known as the product's end of support. When Project Server 2010 reaches its end of support on October 13, 2020, Microsoft will no longer provide:

  • 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.

Your installation of Project Server 2010 will continue to run after this date. However, because of the changes listed above, we strongly recommend that you migrate from Project Server 2010 as soon as possible.

What are my options?

If you are using Project Server 2010, you need to explore your migration options, which are:

  • Migrate to Project Online

  • Migrate to a newer on-premises version of Project Server (preferably Project Server 2019).

Here are the two paths you can take to avoid the end of support for Project Server 2010.

Project Server 2010 upgrade paths

Why would I prefer to migrate to Project Online? Why would I prefer to migrate to Project Server 2019?
I have mobile or remote users.
Costs to migrate on-premises servers are a big concern (hardware, software, hours and effort to implement, etc.).
After migration, costs to maintain my environment are a big concern (for example, automatic updates, guaranteed uptime, etc.).
Business rules restrict me from operating my business in the cloud.
I need control of updates to my environment.

Note

For more information about options for moving from your Office 2010 servers, see Resources to help you upgrade from Office 2010 servers and clients. Note that Project Server does not support a hybrid configuration since Project Server and Project Online cannot share the same resource pool.

Important considerations you need to make when planning to migrate from Project Server 2010

You need to consider the following when planning to migrate from Project Server 2010:

  • Get help from a Microsoft solution provider - Upgrading from Project Server 2010 can be a challenge and requires much preparation and planning. It can be especially challenging if you were not the one to setup and configure Project Server 2010 originally. Luckily, there are Microsoft solution providers you can turn to who do this for a living, whether you plan on migrating to Project Server 2019 or to Project Online. You can search for a Microsoft solution provider to help with your migration on the Microsoft solution provider center.

  • Plan for your customizations - Be aware that many of the customizations you have working in your Project Server 2010 environment might not work when migrating to Project Server 2019 or to Project Online. There are big differences in Project Server architecture between versions, as well as the required operating systems, database servers, and client web browsers that are supported to work with the newer version. Have a plan in place on how to test or rebuild your customizations as needed in your new environment. Planning for your upgrade will also be a good opportunity to verify if a specific customization is really needed as you move forward. Create a plan for current customizations during upgrade to SharePoint 2013 has some great general information about evaluating and planning for your current customizations when upgrading.

  • Time and patience - Upgrade planning, execution, and testing will take much time and effort, especially if you are upgrading to Project Server 2019. For example, if you are migrating from Project Server 2010 to Project Server 2019, you will first need to migrate from Project Server 2010 to Project Server 2013, and then check your data, and then do the same thing when you migrate to each successive version (to Project Server 2016 and then to Project Server 2019). You might want to check with a Microsoft solution provider to compare your estimated costs with their estimates of how long it will take for them to do it, and at what cost.

Migrate to Project Online

If you choose to migrate from Project Server 2010 to Project Online, you can do the following to manually migrate your project plan data:

  1. Save your project plans from Project Server 2010 to .MPP format.

  2. Using Project Professional 2016, Project Professional 2019, or the Project Online Desktop Client, open each .mpp file, and then save and publish it to Project Online.

You can manually create your PWA configuration in Project Online (for example, recreate any needed custom fields or enterprise calendars). Microsoft solution providers can also help you with this.

Key resources:

Resource Description
Get started with Project Online
How to setup and use Project Online.
Project Online Service Description
Information about the different Project Online plans that are available to you.

Migrate to a newer on-premises version of Project Server

While we strongly believe that you can achieve the best value and user experience by migrating to Project Online, we also understand that some organizations need to keep project data in an on-premises environment. If you choose to keep your project data on-premises, you can migrate your Project Server 2010 environment to Project Server 2013, Project Server 2016, or Project Server 2019.

We recommend that you migrate to Project Server 2019 if you can't migrate to Project Online. Project Server 2019 includes most of the key the features and advancements included with previous releases of Project Server, and it most closely matches the experience available with Project Online (although some features are available only in Project Online).

After completing each migration, you should check your data to make sure that it has migrated successfully.

Note

If you are considering only migrating to Project Server 2013 if you are limited to an on-premises solution, it is important to note that it only has a few more years of support left. Project Server 2013 with Service Pack 2 end of support date is 10/13/2023. For more information about end of support dates, see Microsoft Product Lifecycle Policy.

How do I migrate to Project Server 2019?

The architectural differences between Project Server 2010 and Project Server 2019 prevents a direct migration path. This means that you will need to migrate your Project Server 2010 data to the next successive version of Project Server until you upgrade to Project Server 2019.

You will need to do the following steps to upgrade Project Server 2010 to Project Server 2019:

  1. Migrate to Project Server 2013.

  2. Migrate from Project Serve 2013 to Project Server 2016.

  3. Migrate from Project Server 2016 to Project Server 2019.

After completing each migration, you should check your data to make sure that it has migrated successfully.

Step 1: Migrate to Project Server 2013

Your first step in migrating your Project Server 2010 data to Project Server 2019 is to first migrate to Project Server 2013.

For a comprehensive understanding of what you need to do to upgrade from Project Server 2010 to Project Server 2013, see Upgrade to Project Server 2013.

Key resources:

Overview of the Project Server 2013 upgrade process
Get a high-level understanding of what you need to do to upgrade from Project Server 2010 to Project Server 2013.
Plan to upgrade to Project Server 2013
Look at planning considerations you need to make when upgrading from Project Server 2010 to Project Server 2013, including System Requirements.

What's new in Project Server 2013 upgrade tells you some important changes for upgrade for this version, the most notable being:

  • There is no in-place upgrade to Project Server 2013. The database-attach method is the only supported method for upgrading from Project Server 2010 to Project Server 2013.

  • The upgrade process will not only convert your Project Server 2010 data to Project Server 2013 format, but will also consolidate the four Project Server 2010 databases to a single Project Web App database.

  • Both SharePoint Server 2013 and Project Server 2013 changed to claims-based authentication from the previous version. You will need to make considerations when upgrading if you are using classic authentication. For more information, see Migrate from classic-mode to claims-based authentication in SharePoint 2013.

Key resources:

Step 2: Migrate to Project Server 2016

After migrating to Project Server 2013 and verifying that your data has migrated successfully, the next step is to migrate your data to Project Server 2016.

For a comprehensive understanding of what you need to do to upgrade from Project Server 2013 to Project Server 2016, see Upgrade to Project Server 2016.

Key resources:

Overview of the Project Server 2016 upgrade process
Get a high-level understanding of what you need to do to upgrade from Project Server 2013 to Project Server 2016.
Plan for upgrade to Project Server 2016
Look at planning considerations you need to make when upgrading from Project Server 2013 to Project Server 2016.

Things you need to know about Project Server 2016 upgrade tells you some important changes for upgrading to this version, which include:

  • When you create your Project Server 2016 environment to which you will migrate your Project Server 2013 data, note that the Project Server 2016 installation files are included in SharePoint Server 2016. For more information, see Deploy Project Server 2016.

  • Resource plans are deprecated in Project Server 2016. Your Project Server 2013 resource plans will be migrated to Resource Engagements in Project Server 2016 and in Project Online. See Overview: Resource engagements for more information.

Step 3: Migrate to Project Server 2019

After migrating to Project Server 2016 and verifying that your data has migrated successfully, the next step is to migrate your data to Project Server 2019.

For a comprehensive understanding of what you need to do to upgrade from Project Server 2016 to Project Server 2019, see Upgrade to Project Server 2019.

Key resources:

Overview of the Project Server 2019 upgrade process
Get a high-level understanding of what you need to do to upgrade from Project Server 2013 to Project Server 2016.
Plan for upgrade to Project Server 2019
Look at planning considerations you need to make when upgrading from Project Server 2016 to Project Server 2019.

Things you need to know about Project Server 2019 upgrade tells you some important changes for upgrading to this version, which include:

  • The upgrade process will migrate your data from your Project Server 2016 database to the SharePoint Server 2019 Content database. Project Server 2019 will no longer create its own Project Server database in the SharePoint Server farm.

  • After upgrade, be aware of several changes in Project Web App. For a description of these, see What's new in Project Server 2019.

Other resources:

Summary of options for Office 2010 client and servers and Windows 7

For a visual summary of the upgrade, migrate, and move-to-the-cloud options for Office 2010 clients and servers and Windows 7, see the end of support poster.

This one-page poster is a quick way to understand the various paths you can take to prevent Office 2010 client and server products and Windows 7 from reaching end of support, with preferred paths and option support in Microsoft 365 Enterprise highlighted.

You can also download this poster and print it in letter, legal, or tabloid (11 x 17) formats.

Upgrading from SharePoint 2010

Upgrade from Office 2010 servers and clients