Post-migration tasks after migrating your Project Server 2003 data

Project 2010

Applies to: Project Server 2010

Topic Last Modified: 2011-09-11

After you have run the migration tool to migrate Microsoft Office Project Server 2003 data to Microsoft Office Project Server 2007, there are several post-migration tasks that need to be addressed. These tasks include:

This article also includes information about how to roll back migration.

Look at the migration tool command line or the migration log to verify that the migration was successful. If it was not successful, make corrections and re-run the migration tool. If there is an irrecoverable problem, make changes in Project Server 2003, restore the clean Office Project Server 2007 databases, and retry the migration. If the migration process appears to have been successful, ensure that the data migrated correctly to Office Project Server 2007 by doing the following kinds of tests:

  • Verify project data: Open the migrated projects, make changes to them, add enterprise resources, publish them, accept status updates, and so on

  • Verify Project Web Access data: Fill in timesheets, create proposals, build a cube, and so on

We highly recommend that you have a migration checklist specific to your needs and that you test those items after migration.

As explained in Data that cannot be migrated to Project Server 2007, all data from Project Server 2003 may not be migrated to Office Project Server 2007. Therefore we highly recommend that you go over all the Office Project Server 2007 server settings and make sure that they are as you want them to be. Some specific areas are listed below:

  1. Security settings: There are some security permissions (global and category) that are new in Office Project Server 2007. These permissions may not get migrated. You may want to review each one and make a decision on whether to give users that permission. For more information, see Introduction to permissions in Microsoft Office Project Server 2007 (

  2. Project Web Access view definitions: The "Filter by" and "Group by" clauses are not migrated from Project Server 2003. You may need to re-create these. Also, some Project Web Access view fields do not migrate. You may want to make sure that all the fields of interest to you are available in the migrated views.

  3. Merge and rename similar security groups, categories, and templates and Project Web Access view definitions: If there is a name clash during migration of security templates, view definitions, and security groups and categories, the migration tool attaches a prefix or suffix to the clashing names. This action is taken to preserve both Project 2007 entities and Project 2003 entities in one system. Then you can select which one to keep or elect to merge them, as appropriate. We recommend that you resolve them so that end users do not become confused.

This is a required step to make sure that the migrated forms-authenticated users work in Office Project Server 2007. For more information, see Configure SQL Membership Provider forms authentication for Project Server 2007 (

The migration tool resets the Automatically Provision option in the Project Workspace Provisioning Settings page of Server Settings to Manually Create a workspace for each project in Office Project Server 2007. This setting ensures that the migration process does not provision duplicate workspaces for projects that may already have workspaces that are yet to be migrated.

After running the migration tool, check the Project Workspace Provisioning settings located in the Operational Policies section of Project Web Access Server Settings. Verify that the Site URL and the Automatic Provisioning options are configured correctly per your needs. If you want Office Project Server 2007 to automatically create a workspace when a project is published, reset the Automatically Provision option to Automatically create a workspace for the project when a project is published in Office Project Server 2007 after the migration tool is run.

The Manage Groups page in Project Server 2003 does not display inactive users by default. But in Office Project Server 2007, inactive users are displayed by default. Therefore, after the migration process (which migrates the inactive users as well), you may see extra users in the Manage Groups Project Web Access page in Office Project Server 2007.

You can permanently delete the inactive users if needed.

To permanently delete the inactive users:

  1. In Project Web Access, click Server Settings.

  2. In the Database Administration section, click Delete Enterprise Objects.

  3. In the Delete Enterprise Objects page, in the What do you want to delete from Project Server section, select Resources and Users.

  4. In the list of users that displays, select the users you want to permanently delete, and then click Delete.

It is a known issue that project currencies are not migrated correctly. Run the following SQL query on the Project Server 2003 Project Tables database to get a list of projects and their currencies. This information can be used to manually correct the currency settings post migration.

  from dbo.MSP_PROJECTS where PROJ_TYPE in (0, 1, 2)

If you had any local Windows accounts (for example, ComputerName\Brad Joseph), and the computer names are no longer valid, make sure you go to Project Web Access Server Settings and use the Manage Users options to edit those accounts so that they are valid.

Multilanguage lookup tables are not updated correctly after migration. Run the following SQL statements on the Office Project Server 2007 Published database to correct this problem.






If you are using Microsoft Office Project Portfolio Server 2007 with Office Project Server 2007, it is especially important to run these SQL statements to update the tables. If the statements are not run, you may encounter a “GeneralUnhandledException” error when performing an export from Office Project Portfolio Server 2007 to Office Project Server 2007. The error would look like this and would appear in the ULS logs:

PSI: LookupTable.ReadLookupTablesMultiLang Undefined Attibutes: PSError: GeneralUnhandledException Underined attributes list: System.Data.ConstraintException: Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints....

You may want to roll back if one of the following situations occurs:

  • Migration fails in the middle of the process

  • A lot of data changes in Project Server 2003 after migration. If so, the migration process should be done again from scratch.

Because migrating to Office Project Server 2007 is not an in-place upgrade, no Project Server 2003 data is modified during the process. Therefore, a rollback is equivalent to restoring a clean instance of Office Project Server 2007 Project Web Access. (It may be from a backup.) You can then run the migration again.

If you want to re-migrate a few projects (perhaps because they changed in Project Server 2003), the roll-back method is to delete the projects in Office Project Server 2007 and re-migrate them.

If the global data migration process stops in the middle, it needs to be run again from the beginning. The migration tool may stop in the middle because of an error in Project Server 2003 data (for example, a particular resource does not have a valid value for a resource outline code). The way to fix this problem is to open ResGlobal in Project Professional 2003, fix the issue, and retry migration. Repeat this process until the global migration process proceeds to completion. Once it finishes successfully, you know that the Project Server 2003 data is clean. Next, you need to clean up the Office Project Server 2007 data and re-migrate the global data again from scratch.