Share via

  • Article

Data that cannot be migrated to Project Server 2007

 

Applies to: Project Server 2010

Topic Last Modified: 2010-06-14

This article describes data in Microsoft Office Project Server 2003 that is not migrated at all or that requires attention when being migrated to Microsoft Office Project Server 2007.

Project Server 2003 data that is not migrated

Project Server 2003 item not migrated Comment

Outstanding status updates

Outstanding status updates are not migrated if the StopProjectUpdatesIfUpdatesPending setting in the migration configuration file is set to Yes (which is the default option). It is a best practice to make project managers accept or reject project status updates before running the migration tool.

Timesheet history

Timesheet history data is not migrated. Timesheet data in the following tables is not migrated:

  • MSP_WEB_WORK

  • MSP_WEB_ADJUSTED

  • MSP_WEB_TRANSACTIONS

However, timesheet periods are migrated. Also, all status data entered by team members (for example, Tom worked eight hours on assignment X), does get migrated. If you have a reporting system based on timesheet history, then your reports will be affected and will need to be redone.

Status reports

Status report definitions and responses are not migrated.

To-do lists

The related feature in Office Project Server 2007 is called project proposals. Project proposal assignments affect resource availability, whereas to-do list assignments in Project Server 2003 do not. If you are manually shifting from to-do lists to project proposals, you need to take this situation into account.

View filters

Each filter in each view that is not upgraded is noted in a log file. These log entries can help the administrator to recreate the filters manually in Office Project Server 2007.

Project versions

Office Project Server 2007 does not have the concept of project versions. The version name from Project Server 2003 is appended to the project name as part of migration. For example, Project1, version 'target', becomes Project1_target after migration. Project2, version 'published', becomes Project2_published after migration.

Status update rules

Not migrated.

Extra tables or fields added to the database

Any extra tables or fields added to the database file by customers or partners are not migrated. They must be manually migrated to Project Server 2010.

Project Web Access links and Saved Links

You must manually create your links to Project Web Access after migration. This includes the Saved Links feature in Project Server 2003.

Project Server 2003 data that is migrated with caveats

Project Server 2003 data Comment

Non-project time

Project Server 2003 administrative projects are migrated as Office Project Server 2007 administrative projects. They are not migrated into the new non-project time infrastructure in Office Project Server 2007UNRESOLVED_TOKEN_VAL().

Security

Security settings are migrated all at once, but the project-to-category mappings are migrated gradually. When projects are gradually migrated, they become part of the migrated categories with which they are associated, and this behavior can be controlled by the FixUpSecurityCategories configuration parameter in the migration configuration file.

For more information on this parameter, see Configure the migration tool (Project Server).

Value lists (for both local and enterprise custom fields)

Migrated as lookup tables

Project Server 2003 users with assignments (not part of the enterprise resource pool)

Migrated as Office Project Server 2007 enterprise resources.

Note

In Project Server 2003, you can publish projects without saving them as enterprise projects. A non-enterprise mode does not exist in Office Project Server 2007, and users can have assignments only if it is an enterprise resource. Therefore, users with assignments in Project Server 2003 are converted to enterprise resources in Office Project Server 2007, so that the assignment information is not lost.

Alert preferences

Migrated to notifications.

Enterprise resources

Enterprise resource migration is a very important part of migration. Following are examples of conflicts that may occur during enterprise resource migration:

  • Case 1: When a Project 2003 enterprise resource matches with a Project 2007 enterprise resource (by name or Windows NT account):

    1. The Project 2003 enterprise resource is not migrated.

    2. The resource is replaced by the Project 2007 enterprise resource.

  • Case 2: When a Project 2003 enterprise resource matches with a Project 2007 enterprise user (by name or Windows NT account):

    1. The Project 2003 enterprise resource is not migrated.

    2. The resource is converted to a local resource in Project 2007.

  • Case 3: When a Project 2003 local resource matches with a Project 2007 enterprise resource (by name)

    • The local resource is not converted to an enterprise resource.

  • Case 4: When a Project 2003 enterprise resource of type X (say, generic resource) matches with a Project 2007 enterprise resource of type Y (say, a material resource) (by name)

    1. The Project 2003 enterprise resource is not migrated.

    2. The resource is converted to a local resource.

Enterprise resource pool Active Directory group mappings

Mappings from Project Server 2003 security groups to enterprise resource pool Active Directory groups are not migrated to Office Project Server 2007. However, users and resources added by using Project Server 2003 Active Directory synchronization are migrated. After migration, use the migration log file to assist in manually setting up the mappings for Active Directory groups to the enterprise resource pool and Project Server security groups in Office Project Server 2007.

Note

Synchronizing to an organization unit — while supported in Project Server 2003 — is not supported in Office Project Server 2007. In Office Project Server 2007, you should synchronize with an Active Directory group because there is not a group-member size limitation as there is in Project Server 2003.

Project Server users

If there is a Project Server user in Office Project Server 2007 either with the same name or Windows NT account as a Project Server 2003 user, then the Project Server 2003 user's details (for example, name, e-mail address, security settings) are not migrated. (In other words, the Office Project Server 2007 data prevails in the case of a conflict).