We recently worked with a customer to improve its existing Microsoft Project Server implementation. This customer has over 12000 users actively using the PPM solution. Many of them were experiencing issues due to the way the solution was set up and configured. Once we successfully completed the assignment, the customer’s PMO department sought our advice on Project Server migration.

We made a recommendation based on our analysis of its baseline implementation of the current Project Server version and their future needs. Overall considerations have been composed to consider the various components that can be utilized in an upgrade deployment along with some high-level considerations that should be contemplated.

The following entry is part of the recommendation document. If you are considering a Project Server migration, this may support your decision process whether to upgrade to Project Server 2013 or Project Server 2016.

Overall Considerations

The components that go together to make up a Project Server deployment should be considered when contemplating deploying Project Server 2013 versus Project Server 2016. Additionally,

The following table details components that should be taken into consideration when considering upgrading to either Project Server 2013 or Project Server 2016.

Project Server Deployment Components

Item Project Server 2013 Project Server 2016 Comments
OS Version(s) Windows Server 2008 R2

Windows Server 2012 R2

Windows Server 2012 R2

Windows Server 2016

Windows Server 2008 & 2012, R2 settled versions, Windows Server 2016 new
SQL Server SQL Server 2012, R2 SQL Server 2014, SP1

SQL Server 2016 RTM

SQL Server 2012, R2, SQL Server 2014, SP1 settled versions, SQL Server 2016 new
SharePoint SharePoint Server 2013 SQL Server 2016 SharePoint Server 2013, settled version, SharePoint Server 2016 new
Project Server Project Server 2013, SP1 Project Server 2016 Project Server 2013, SP1 settled version, Project Server 2016 new
Project Client Project Professional 2016

Project Online Desktop

Project Professional 2013

Project Professional 2016

Project Online Desktop

Project Professional 2013

Both Project Server 2013 and Project Server 2016 can leverage all 3 versions of the Project Professional client application

Project Server Deployment Components

High-Level Considerations:

  • SharePoint Version: The Project Server version deployed should be tied into the most commonly deployed version of SharePoint Server that is supported by the organization. Project Server is a SharePoint Services, so a sizable portion of the support will be derived from SharePoint Technical Support.
  • Migration Steps: Whether migrating from Project Server 2010 to Project Server 2013 or Project Server 2016, a Project Server 2013 environment will need to be built out. Project Server 2016 can only be upgraded from a Project Server 2013 environment, so an interim Project Server 2013 instance will need to be configured, prior to the Project Server 2016 migration process.
  • Version Maturity: There are good reasons for waiting a minimum of 1 year (preferably 2 years) after the release of a major Project Server version, before upgrading to the latest version. Taking time to get familiar with Project Server 2013, while waiting for the Project Server 2016 version to mature is worth considering.
  • Infrastructure Planning: Irrespective of the version of Project Server that is selected, it is highly recommended that the infrastructure for at least a Production, Test and Development Environment be built out.
  • Portfolio Analysis: There has been little change in all three versions (Project Server 2010, 2013 and 2016), in the ‘Portfolio Analysis’ features, which include ‘Demand Management’, ‘Portfolio Prioritization’, ‘Portfolio Selection’ and ‘Capacity Planning (Skill Level)’.
  • Schedule Management: Project Server 2013 added or updated features:
    • Schedule Entire Project Plan
    • Cost and Material Resource assignments
    • Tasks assigned to Deadlines
    • Immediate Formula Field Updates
    • Full function Fixed Work or Effort-Driven Task Types
    • Timeout Setting upon Project editing
    • Visual Timeline on PWA Gantt charts
    • Mobility features

In terms of feature comparison, the set of features that are available between Project Server 2013 and Project Server 2013 versions have not changed a lot. Many of the updates have related to improvements in the way existing features operate. If you are interested in Feature Comparision, drop us a note, we can send you a table that provides a comparison between the features of Project Server 2010, Project Server 2013 and Project Server 2016.

Our team has performed numerous Project Server upgrade and migration, as well as foreign PPM application migration to Microsoft PPM. If you need help, contact us at https://epmsolutions.com/contact/. Or, just call for more information at 415-818-2600.