• Article

Run the migration tool (Project Server)

 

Applies to: Project Server 2010

Topic Last Modified: 2010-06-14

In this article:

  • Migrate global data

  • Migrate projects (full migration)

  • Migrate projects (gradual migration)

This article describes the steps involved in running the migration tool to migrate global data or projects from Microsoft Office Project Server 2003 to Microsoft Office Project Server 2007.

Migrate global data

Before migrating projects either through a full migration or a batch of gradual migrations, we recommend as a best practice that you make an initial run of the migration tool to migrate global data such as the enterprise global template, enterprise resources, and Project Web Access data. Once you verify that the data has migrated correctly, you can then migrate projects.

In order to migrate only global data, the migration configuration file must have the following parameters set correctly:

  • MigrateAll=   Leave this value empty.

  • [Project Names to Save]   Do not enter any project names in this section.

  • [Project names to Save and Publish]   Do not enter any project names in this section.

    Note

    After initially running the migration tool to migrate global data, subsequent attempts to migrate global data will not overwrite or update the data in Office Project Server 2007. Global data migration can only occur once. If there are any incremental changes to the Project Server 2003 global data, they must be applied manually to Office Project Server 2007.

    Important

    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 (restore the Office Project Server 2007 databases to a clean state) and re-migrate the global data again from scratch. You should re-migrate the global data to a new Office Project Server 2007 instance.

    For information about restoring Office Project Server 2007 databases, see Troubleshoot migration to Project Server 2007.

    Important

    Once you have upgraded Project Server 2003 workspaces, then you need to configure the Project Workspace provisioning settings. Once global data migration finishes successfully:

    1. In the migrated Project Web Access site, click Server Settings.

    2. On the Server Settings page, in the Operational Policies section, click Project Workspace Provisioning Settings.

    3. In the Site URL section, make sure that Default Web Application and Site URL points to the SharePoint site with the upgraded workspaces. If this value is not set, the link from projects, tasks, and assignments to issues, risks, and documents will not be fixed correctly when projects are migrated and published.

Migrate projects (full migration)

When running the migration tool to migrate all projects at one time (full migration), the migration configuration file's MigrateAll= parameter must be configured with one of the following two options:

  • MigrateAll=Save   All projects in Project Server 2003 are migrated to Office Project Server 2007 and none of them are published.

  • MigrateAll=Publish   All projects in Project Server 2003 are migrated to Office Project Server 2007 and the published projects in Project Server 2003 are automatically published in Office Project Server 2007.

You can also enter all the project names manually in the [Project Names to Save] or [Project Names to Save and Publish] sections.

Note

It is a best practice to migrate and save projects first (by adding them to the [Project Names to Save] section), verifying that the migration worked correctly, and then publishing the projects (by adding them to the [Project Names to Save and Publish] section). If a project is added to the [Project Names to Save and Publish] section and the project already exists in Office Project Server 2007, then it is only published.

Note

When entering project names in both of these sections of the migration configuration file, you must specify the complete name (as stored in the PROJ_NAME column of the MSP_PROJECTS table of the Project Server 2003 database). For example, do not simply specify "Project1." Instead, specify "Project1.Published."

Migrate projects (gradual migration)

When migrating Project Server 2003 data to Office Project Server 2007 with the purpose of migrating to Microsoft Project Server 2010, in some cases you might want to migrate your projects in batches (gradual migration) as opposed to all at one time (full migration). For example, you might have several thousand projects, and as a best practice you want to migrate them in batches of 1,000. Another example is if you want to migrate all subprojects first before migrating a master project.

When running the migration tool to migrate subsets of projects in a series of batches (gradual migration), the MigrateAll= parameter is left empty. The migration tool is run once for each batch of projects you wish to migrate. The names of the projects you want to migrate for each batch must be entered into the migration configuration file in either of the following sections:

  • [Project Names to Save]   Type the project names of the projects you want saved after migrating them to Office Project Server 2007.

  • [Project Names to Save and Publish]   Type the project names of the projects you want saved and published after migrating them to Office Project Server 2007. Only published projects (with the ".published" extension) in Project Server 2003 can be published to Office Project Server 2007. Versioned projects specified in this section are saved but not published.