Live Chat
Click to Call
1-866-716-2040
Project Server 2010 Vs Project Server 2013 Comparison Table
Custom Permissions Exchange integration with Project ServerIn-place Upgrade Submit Your Requirements
| Features | Project Server 2010 | Project Server 2013 |
| Multi-tenancy support – The ability to accommodate multiple tenants when used in conjunction with the SharePoint Server 2013 multi-tenancy feature. This gives you the ability to have multiple customers, business units, or departments on the same SharePoint Server and Project Server farm and infrastructure.
|  |  |
| Database consolidation – All four Project Server databases (Draft, Publish, Reporting, and Archive) are consolidated into a single database, the Project Web App database (default name: ProjectWebApp). A reduction in the number of databases reduces the costs associated to maintain the data (update, backup, disaster recovery, and so on).
|  |  |
| Project site – When a project site is part of a site collection that is associated with Project Server, it can also be used to capture issues, risks, and deliverables, and it can be switched to full control (versus managed mode) for more robust Project Server functionality.
|  |  |
| Project mobile availability – A support for mobile access to your project data. A web-based mobile site is now included, which enables team members and project managers to view project status at a glance on a mobile device. By using the touch-enabled mobile site, you can access and edit relevant project documents and do lightweight editing of project plans from your Windows Phone 7.5 (using the Internet Explorer 9 browser), Apple iPhone, or Android device.
|  |  |
| Improvements in Workflow and Demand Management – Demand Management is the area of collecting “demand” for project ideas and proposals, and gathering information on those proposals.
| In Project Server 2010, workflows could be created and edited in Visual Studio. | A key improvement in Project Server 2013 is the ability to use SharePoint Designer and the workflow engine in SharePoint Server 2013 to create Project workflows for Demand Management. |
| OData service for better reporting – Project Server 2013 introduces an OData service for online and on-premises access. The online reporting tables and views are exposed only by the OData interface; for on-premises use, you can use the OData interface or directly access the reporting tables and views in the ProjectService database in the SharePoint farm.
|  |  |
| Project Apps – An app is typically a self-contained, interactive program that performs a small number of related tasks. A Project app can be a task pane app for the Project Standard 2013 or Project Standard 2013 clients, or an app for Project Server 2013 or Project Online.
|  | For Project 2013, apps can be made available for purchase and download from the public Office Store or distributed within a private app catalog on SharePoint. |
| Scheduling
| In Project Server 2010 in order for the schedule web part to reschedule the tasks the user would need to click on the calculate button. | With Project Server 2013, this is no longer the case, with the schedule being updated automatically. |
| REST feeds
| REST feeds were sort of available in Project Server 2010, but only to get at the SharePoint content such as lists in the PWA site | With Project Server 2013, these feeds now allow you to get at actual Project Server reporting data, including project, task and assignment lists. |
| Better Metro style user interface – The new visual tiles in Project Web App (PWA), your web app to access Project Server, to quickly begin or flex project portfolio management capabilities.
|  |  |
| Custom Permissions – Custom security permissions to access specific Project Server features or extensions were supported in Office Project Server 2007
| In Project Server 2010, custom permissions still work but are deprecated. | In Project Server 2013, custom permissions do not work with the default SharePoint permission mode for on-premises installations. |
| Administrative Settings user interface changes
| Microsoft Project Server 2010 administrators must manage many tasks in the Microsoft Project Web App (PWA) Server Settings page for users to access and interact effectively with data. | In Project Server 2013, Administrative controls that are more IT-related were moved from the Project Web App Server Settings page to the SharePoint Central Administration site. |
| Exchange integration with Project Server
| Exchange integration with Project Server was introduced in Project Server 2010. It provides the ability for team members or resources on a project to view, update, delete, and report status on their published tasks in Outlook, Outlook Web App (OWA), or any other application that is capable of syncing tasks from Exchange Server. | The Exchange integration feature in Project Server 2013 allows you integrate project task management by using SharePoint Server 2013 with Exchange Server 2013. This allows team members anywhere that have access to Exchange Server to interact with task management data in Outlook or Outlook Web App and even using an Exchange-connected mobile device (by using either Windows Phone 7.5 or Apple IOS v5). |
| Resource calendars
| Project Server 2010 introduced the ability to integrate task updates through Exchange Server | with Project Server 2013, the Project team have taken it up a notch, allowing synchronisation of your ‘Out of Office’ with your resource calendar. |
| SharePoint task-list projects and enterprise projects
| The Project Application Service in Project Server 2013 can be associated with a SharePoint site collection in which the project sites are SharePoint task-list projects. | |
| Active Directory synchronization – Active Directory Enterprise Resource Pool synchronization is used to create or update multiple Project Server enterprise resources at the same time. | In Project Server 2010, you have access to Project Server through Project Web App. | In Project Server 2013, big improvements have been made to synchronization and timer job performance. Introduced smarter scheduling: Synchronization jobs now run more during low usage times. Active Directory sync timer jobs can be scheduled through the Central Administration site.Reduced the number of RDB updates: Reporting synchronization jobs are more expensive to run than other job types. Reductions have been made in the number of jobs being run, and also in the types of jobs that are run. |
| In-place Upgrade – When you start the in-place upgrade process, Setup takes the entire farm offline and the Web sites and Microsoft Project Web App sites are unavailable until the upgrade is finished, and then Setup restarts the server. After you begin an in-place upgrade, you cannot pause the upgrade or roll back to the previous version.
| Yes In-place upgrade is supported. | Full database-attach upgrade is the only available upgrade method when you upgrade to Project Server 2013. In-place upgrade is not supported for upgrading to Project Server 2013. |
| Backward compatibility – Backward compatibility mode (BCM) is a feature that assists in the upgrade of your Enterprise Project Management environment
| Supported | Not Supported |
| Client compatibility
| Users can connect to Project Server 2010 with both Project Professional 2007 and 2010 clients. | Project Server 2013 will only accept connections from Project Professional 2013. |
