What's new in Project Server 2013 upgrade
Applies to: Project Server 2013
Topic Last Modified: 2013-12-18
Summary: Learn about key changes and considerations when you upgrade to Project Server 2013.
Upgrading to Project Server 2013 differs in many ways from upgrading to previous versions of Project Server. When you upgrade to Project Server 2013, it is important to consider the following:
When you upgrade to Project Server 2013, database-attach upgrade is the only supported method. Database-attach upgrade lets you attach your required databases to your Project Server 2013 farm, and then upgrade the databases. Database-attach upgrade requires you to install a "destination environment"—a Project Server 2013 farm.
|In-place upgrade (where the Project Server binary files are upgraded on the same hardware) is not a supported method for upgrading to Project Server 2013.|
When you upgrade to Project Server 2013, you are required to use the following databases from your Project Server 2010 environment:
Project Server 2010 Archive
Project Server 2010 Draft
Project Server 2010 Published
Project Server 2010 Reporting
SharePoint Content database containing the Project Web App site data
|When you upgrade to Project Server 2013, full database-attach upgrade (sometimes referred to as "five database-attach") is used. This means that the SharePoint Content database that contains the Project Web App site data, and the Project Server 2010 databases, is required for upgrade. The SharePoint Content database must be used, or else project details pages and workflows will not function. Also, all project workspaces will not be available, along with associated documents, lists, risks, issues, and deliverables.|
Project Server 2013 architecture has been improved to reduce total cost of ownership (TCO) for database maintenance. In Project Server 2010 and Office Project Server 2007, each PWA instance hosted a majority of its project data on the four Project Server databases (Draft, Publish, Reporting, and Archive). When you upgrade to Project Server 2013, your four Project Server 2010 databases are merged into a single Project Web App database (default name: ProjectWebApp). The reduction in the number of databases required to run Project Server 2013 equates to a reduction in the costs to maintain, update, back up, and plan for disaster recovery for your Project Server 2013 data.
|For information about recommended hardware requirements for your database tier in Project Server 2013, see Hardware and software requirements for Project Server 2013.|
There is no direct upgrade path from Office Project Server 2007 to Project Server 2013. When you upgrade from Office Project Server 2007, you must first upgrade to Project Server 2010, then upgrade the required databases to Project Server 2013.
For information about how to upgrade from Office Project Server 2007 to Project Server 2010, see the following resources:
Upgrade and Migration for Project Server 2010 TechNet Resource Center: This site contains links to all Project Server 2010 upgrade technical content on Microsoft TechNet.
Microsoft Project Server 2010 Upgrade SuperFlow: An interactive Help file that you can download and install on your local computer. It contains the Project Server 2010 TechNet upgrade content set, made viewable to the user through logically organized category tabs and sequential data flow objects.
Note the following in regards to Project Professional and Project Web App client compatibility to Project Server 2013:
Project Server 2013 will only accept connections from Project Professional 2013.
Project Web App users in Project Server 2013 will be able to use the all browsers that are supported for use with SharePoint Server 2013. These include the following:
Internet Explorer 10
Internet Explorer 9
Internet Explorer 8
Mac Safari 5
Google Chrome 17
|For more information about client connectivity, see Plan for upgrade to Project Server 2013.|
The release of Project Server 2013 is also paired with the release of a new service in Office 365 for enterprises, Project Online. With Project Online in Office 365, all operational maintenance is handled through an online service that is hosted in Microsoft datacenters. Project Online in Office 365 delivers full Project Portfolio Management (PPM) capabilities (Demand Management, Portfolio Management, Resource Management, Reporting, and so on). Portfolio managers, project managers, and team members can access Project Online from anywhere with an Internet connection.
Project Server 2010 customers may want to upgrade from their on-premises environment to Project Online in Office 365. Upgrading your on-premises environment to Project Online in Office 365 is done through 3rd party tools. For more information about available 3rd party tools, see the MSDN blog post Want to test-drive Project Online? How to migrate data from on-premises to Online.
The following are current known issues that occur when you upgrade to Project Server 2013:
Upon completing the upgrade from Project Server 2010 to Project Server 2013, if you click New in the PWA ribbon, you only see the Basic Project Plan Enterprise Project Type (EPT). You do not see other project types that are available in Project Server 2013. The workaround for this issue is to manually add the Project Server 2013 EPTs. For more information about this workaround, see Post-upgrade tasks (Project Server 2013).
When you upgrade your Project Server 2010 databases to Project Server 2013, your Project Server 2010 databases must be in native mode (not backward compatibility mode). If your Project Server 2010 databases are in backward compatibility mode (BCM) when you upgrade, you may experience some issues (such as missing pages) with your sites after upgrade, because BCM is not a supported feature in Project Server 2013. For more information about this issue, see Prepare your environment for an upgrade to Project Server 2013
Note: For more information about backward compatibility mode, see Project Server 2010 backward compatibility mode (BCM).
If your Project Server 2010 Published database contains resource accounts in which the
WRES_Accountfield contains an empty string (expected value is NULL), upgrade of this database will fail. We recommend that you check for this condition before attempting an upgrade, especially if you had upgraded resource accounts from Office Project Server 2007 to Project Server 2010 in the past. If your upgrade to Project Server 2013 fails because of this condition, you cannot use the same copies of your Project Server 2010 databases to fix the issue and retry upgrade. You must restore the original Project Server 2010 databases to the SQL Server, fix the condition, and then retry the upgrade.
To check for this condition, run the following SQL script on the backup copy of your Project Server 2010 Published database:
Use ProjectServer_Published select RES_Name, RES_TYPE, RES_ID from MSP_RESOURCES where WRES_ACCOUNT =''
If accounts with this condition are found, run the following SQL script on the same database to fix the accounts:
Use ProjectServer_Published Update MSP_RESOURCES set WRES_ACCOUNT = null where WRES_ACCOUNT =''
If you have additional questions, try the Project forums. The Project forums give you the chance to have your question discussed by other participants, Project MVPs, and Project community experts.
If you would like to provide feedback on this article, choose the Yes or No option for Did you find this article helpful? located at the end of this page, and then type your feedback in the box that appears.