Deciding When To Upgrade Your Microsoft Project Software

I receive a lot of questions from customers asking if they should upgrade to the latest version of Microsoft Project.

As of right now I am working with customers who have all of these versions: Microsoft Project 2003, 2007, 2010, 2013, 2016, and Project Pro for Office 365.

Making the Case for the Upgrade

Here are some reasons why you might want to upgrade:

  • You have experienced a software bug that is fixed in a later version.
  • Your company has software assurance and upgrades are included with this service.
  • Your current version is out of the support period by Microsoft and service pack updates or bug fixes are no longer available.
  • You feel a new feature could solve a problem you are having or could add business value.
  • You have Project Server or Project Online and you need to keep your Microsoft Project versions aligned with your enterprise software.

Here is an example in Excel showing what you might find regarding Software End of Life:

End of Life Example

Reference obtained from:

Making the Case for Staying with the Same Version

Here are some reasons why you might want to keep the same version:

  • Lots of larger corporations upgrade software only every three years.
  • If you are not using Project Server or Project Online, you may not need critical updates to continue running your projects.
  • Software bugs have workarounds that you are satisfied with.
  • You would have to incur an additional software or hardware expense to deploy the update.
  • You have budget restrictions.
  • You do not have software assurance and you are trying to get the most out of your existing purchase.

The next time you have this discussion internally, I hope you will think about these points.



twitterlinkedinby feather
Facebooktwitterlinkedinyoutubeby feather