Migration overview and considerations (Project Server 2010)
Applies to: Project Server 2010
Topic Last Modified: 2012-12-19
Summary: Read about migration from Project Server 2003 to Project Server 2010, including server requirements and client-compatibility requirements.
Important
Upgrading from the Project Server 2010 public Beta to the Project Server 2010 released version is explicitly blocked and not supported. This restriction applies to both the in-place and database-attach upgrade methods.
Migration from Microsoft Office Project Server 2003 to Microsoft Project Server 2010 is a two-step process:
Migrate from Project Server 2003 to Microsoft Office Project Server 2007
Migrate from Office Project Server 2007 to Project Server 2010
Migrating from Project Server 2003 to Project Server 2007
Migration from Project Server 2003 to Office Project Server 2007 can be done in one of two ways:
Standard migration: A standard migration requires you to install Office Project Server 2007 and then migrate your data from Project Server 2003 through a utility known as the Migration tool.
Virtual Migration Environment (VME): A fully configurable environment that has Office Project Server 2007 with SP2 and that is packaged in a Hyper-V image. It can be run as a stand-alone environment for the sole purpose of migrating Project Server 2003 data to the Office Project Server 2007 data format. The VME provides Project Server 2003 you a way to migrate to Project Server 2010 without having to set up an intermediate Office Project Server 2007 environment.
Migrating data from Project Server 2003 to Office Project Server 2007 is done by the "migration tool" (which can be installed from the Microsoft Office Project Professional 2007 installation disk). This is a command-line tool.
.gif "Migration architecture diagram")
The migration tool reads data from the Project Server 2003 database, cleanses and reformats the data and saves it to Office Project Server 2007. Some data, including projects and enterprise resources, is saved to the computer running Office Project Server 2007 through the Project Server Interface (PSI). Other data, including all Office Project Web Access data and upgrade metadata, is directly written to the Office Project Server 2007 database.
If Project Server 2003 is integrated with Windows SharePoint Services 2.0, you must upgrade Windows SharePoint Services 2.0 to Service Pack 2 (SP2) and then upgrade it to Windows SharePoint Services 3.0. Both the data (issues, risks, documents) and the links between Project items and Windows SharePoint Services items are upgraded at the end of the migration process.
You can only migrate data to Office Project Server 2007 from a Project Server 2003 database with Service Pack 2a (SP2a) or a subsequent service pack applied. The most current service pack for Project Server 2003 is Service Pack 3.
Note
Windows SharePoint Services 2.0 was an optional component for Project Server 2003 (Office Project Web Access did not depend on Windows SharePoint Services 2.0). But Windows SharePoint Services 3.0 is a required component for Office Project Server 2007 (Office Project Web Access for Office Project Server 2007 is built on top of Windows SharePoint Services 3.0, and Office Project Server 2007 deployment is based on the Windows SharePoint Services farm infrastructure). That is the reason that Office Project Server 2007 and Windows SharePoint Services 3.0 are represented on the same server in the diagram above.
Note
The command-line migration tool can be thought of as a specialized version of Office Project Professional 2007 without any user interface — so Microsoft Project Professional and the migration tool cannot be running on the same computer at the same time.
For detailed documentation for migrating from Project Server 2003 to Office Project Server 2007, see Upgrade to Project Server 2010 from Project Server 2003.
Migrating from Project Server 2007 to Project Server 2010
Migrating from Office Project Server 2007 to Project Server 2010 can be done through two methods:
In-place: The Office Project Server 2007 installation is upgraded to Project Server 2010 on the same computer on which it is installed.
Database attach: The Office Project Server 2007 databases are backed up and then restored on the computer that is running SQL Server that will host the Project Server 2010 databases. Office Project Server 2007, installed on another computer, then upgrades the databases by provisioning a Microsoft Project Web App instance using the restored Office Project Server 2007 databases.
When migrating from Project Server 2003 to Office Project Server 2007 in order to upgrade to Project Server 2010, you can use either method described above.
If you plan to use the database attach method of upgrading:
Use the database attach full upgrade method if you need to migrate your Office Project Web Access site data plus your project data. For more information about this method, see Database-attach full upgrade to Project Server 2010.
Use the database attach core upgrade method if you only need to migrate your Office Project Server 2007 project data. For more information about this method, see Database-attach core upgrade to Project Server 2010.
Important
If you intend to do an in-place upgrade of Project Server 2010, your Office Project Server 2007 installation must be on a Windows Server 2008 64-bit platform. For more information about requirements, see the Server requirements section in this article. For more information about in-place upgrade, see In-place upgrade to Project Server 2010.
Note
If you are planning to upgrade through the Virtual Migration Environment when it becomes available, note that after using it to migrate from Project Server 2003 to Office Project Server 2007, you will only be able to upgrade to Project Server 2010 using the database attach method.
For more information about Project Server 2010 upgrade methods, see Project Server 2010 upgrade overview.
Server requirements
When you are planning to upgrade from Project Server 2003 to Project Server 2010, it is important to plan for server requirements needed for Project Server 2003 and Office Project Server 2007.
A major difference between Project Server 2003 and Office Project Server 2007 is the availability of 32-bit and 64-bit versions of the application software. For Office Project Server 2007, we already recommend that you deploy 64-bit versions of the application, both on the front-end Web server and on the application server roles. In Project Server 2010, only a 64-bit version of the application is available.
A 64-bit version of Microsoft SQL Server is highly recommended for Office Project Server 2007, and it is mandatory for Project Server 2010. The 64-bit applications benefit from a much larger addressable memory space, which improves the performance under medium to heavy workloads.
It is also important to note that Microsoft SharePoint Server 2010 Enterprise edition is a requirement for installing Project Server 2010.
The official support of virtualized environments is also a new benefit of Office Project Server 2007 and Project Server 2010.
| Project Server 2003 | Office Project Server 2007 | Project Server 2010 | |
|---|---|---|---|
Operating System |
Windows Server 2000 SP3 32-bit Windows Server 2003 32-bit |
Windows Server 2003 SP1 32-bit or 64-bit Windows Server 2008 32-bit or 64-bit |
Windows Server 2008 64-bit Windows Server 2008 R2 64-bit |
SharePoint Products and Technologies |
Windows SharePoint Services 2.0 (optional) |
Windows SharePoint Services 3.0 32-bit or 64-bit |
SharePoint Server 2010 Enterprise Edition 64-bit |
SQL Server |
SQL Server 2000 SP3 |
SQL Server 2000 SP3 SQL Server 2005 SP3 with CU6 SQL Server 2008 |
SQL Server 2005 SP3 CU3 64-bit SQL Server 2008 SP1 CCU2 64-bit |
Virtualization |
Not supported. |
Supported |
Supported |
Using the Virtual Migration Environment (VME) to upgrade from Project Server 2003 to Office Project Server 2007 requires you to have the Hyper-V feature on Windows Server 2008 or Hyper-V Server 2008.
Cross-version compatibility between client and server products
When migrating to Project Server 2010, you must also plan for client compatibility requirements. The following table shows cross-version capability between Microsoft Project Professional client versions to Project Server versions. You will need to verify that all Microsoft Project Professional users have the proper version to access Project Server after the upgrade.
| This client version | Only connects to this server version |
|---|---|
Office Project Professional 2003 |
Project Server 2002, Project Server 2003 |
Office Project Professional 2007 |
Office Project Server 2007, Project Server 2010 Note Office Project Professional 2007 only connects to Project Server 2010 when Backwards Compatibility Mode (BCM) is enabled on the server. For more information about BCM, see Project Server 2010 upgrade overview. |
Microsoft Project Professional 2010 |
Project Server 2010 |
The following table describes supported browsers required for Project Web App for each version of Project Server. If you are upgrading from Project Server 2003 to Project Server 2010, verify that your Project Web App users have the required browser to access their data after the upgrade.
| Project Web App version | Required browser |
|---|---|
Project Server 2003 |
Internet Explorer 5.5, 6.0, 7.0, and 8.0 |
Office Project Server 2007 |
Internet Explorer 6.0, 7.0, 8.0, and 9.0 |
Project Server 2010 |
Internet Explorer 7.0, 8.0, and 9.0 |
Custom field and lookup table name conflicts
There are certain custom fields and lookup tables name that are reserved in both Office Project Server 2007 and Project Server 2010. If any of these names are used in the current Project Server 2003 database, the custom fields and outline codes must be changed in Project Server 2003 before proceeding further with the migration. Use Microsoft Office Project Professional 2003 connected to a Project Server 2003 instance to validate and take corrective action.
| Outline code or custom-field name that is reserved | Type | Office Project Server 2007 | Project Server 2010 |
|---|---|---|---|
Cost Type |
Resource |
X |
X |
Health |
Task |
X |
X |
State |
Project |
X |
X |
Team Name |
Resource |
X |
X |
Approved Finish Date |
Project |
X |
|
Approved Start Date |
Project |
X |
|
Areas affected |
Project |
X |
|
Assumptions |
Project |
X |
|
Business Need |
Project |
X |
|
Compliance Proposal |
Project |
X |
|
Flag Status |
Task |
X |
|
Goals |
Project |
X |
|
Post-Implementation Review Date |
Project |
X |
|
Post-Implementation Review Notes |
Project |
X |
|
Primary Objectives |
Project |
X |
|
Project Departments |
Project |
X |
|
Proposal Cost |
Project |
X |
|
Proposed Finish Date |
Project |
X |
|
Proposed Start Date |
Project |
X |
|
Resource Department |
Resource |
X |
Additionally, make sure to see Verify your Project Server 2003 data for additional things you can check for before migrating your Project Server 2003 data.