Check for reserved custom field, lookup table, or outline code name conflicts (Project Server)
Applies to: Project Server 2010
Topic Last Modified: 2010-05-18
The first pre-migration task that you have to do in the Project Server virtual migration environment (VME) is to check your Microsoft Office Project Server 2003 data for reserved custom field, lookup table, and outline code names that may cause the migration to fail. There are certain of these names that are reserved in both Microsoft Office Project Server 2007 and Microsoft Project Server 2010. Verify that your Project Server 2003 data does not have custom field, lookup table, or outline code names that conflict with the names reserved for Office Project Server 2007 and Project Server 2010. If any of these names are used in the current Project Server 2003 database, the names must be changed before you continue with the migration.
You have to correct the Project Server 2003 database through Microsoft Office Project Professional 2003 in your Project Server 2003 environment. After making corrections, make a backup copy of the Project Server 2003 database, and use the procedures in Load data to the Project Server VME to restore the updated database to the VME virtual machine.
For more information about the Project Server VME, see Overview of the VME for Project Server 2010.
Reserved outline code/lookup table names
Outline code name | 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 |
Department |
X |
||
Flag Status |
X |
Reserved custom field names
Custom field name | 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 |
Sample Approved Finish Date |
Project |
X |
|
Sample Approved Start Data |
Project |
X |
|
Sample Areas Impacted |
Project |
X |
|
Sample Assumptions |
Project |
X |
|
Sample Business Need |
Project |
X |
|
Sample Compliance Proposal |
Project |
X |
|
Flag Status |
Task |
X |
|
Sample Goals |
Project |
X |
|
Sample Post-Implementation Review Date |
Project |
X |
|
Sample Post-Implementation Review Notes |
Project |
X |
|
Sample Primary Objectives |
Project |
X |
|
Project Departments |
Project |
X |
|
Project Impact |
Project |
X |
|
Sample Proposal Cost |
Project |
X |
|
Sample Proposed Finish Date |
Project |
X |
|
Sample Proposed Start Date |
Project |
X |
|
Relative Importance |
Project |
X |
|
Resource Departments |
Resource |
X |