Introduction: Project Server 2007 migration guide

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.


Topic Last Modified: 2016-11-14

This guide is about migrating data from previous versions of Project Server (Microsoft Office Project Server 2003, Project Server 2002, Project Central) to Microsoft Office Project Server 2007. Note that Office Project Server 2007 has new functionality and many new features. It also has fundamental architecture changes when compared to previous versions of Project Server. Therefore it is very important to carefully plan and execute your migration. This guide helps with that process, and we highly recommend that you read it thoroughly.

The migration process is complex, so therefore this guide is long — but it is structured in a way that you can only read the portions relevant to your migration rollout option. It has the following main sections:

  • Plan for migration   A conceptual section that deals with the planning process. Understanding the migration process and thoroughly planning for it is important for a successful migration — and it likely will consume around 60 percent of the overall migration effort.

  • Perform migration   The core section, detailing how to install and run the migration tool. It includes an important subsection with instructions to detect and fix invalid/corrupt data in Project Server 2003 and minimizes discovering such problems during migration. For example, this section helps you find the projects which are not checked in (they need to be checked in prior to migrating), projects with pending status updates (updates need to be accepted/rejected prior to migrating) and so on.

  • Post-migration tasks   Deals with tasks done after migration. For example, verifying if data was migrated correctly.

  • Troubleshoot migration   Details the common issues that may be encountered during migration and provides guidance on how to deal with them.

  • Migration best practices   Details some best practices for migration. For example, global migration should be performed first, before project migration.

  • Frequently asked questions   Answers frequently asked questions about migrating to Office Project Server 2007.

  • Migration quick reference   Provides a simple set of steps (without much detail) to get started. This section is meant for people who first want to run the tool (and see how it works) before reading through the other sections.

Upgrading from a previous version of Project Server is a data migration process

In the traditional sense, upgrading from a previous version is often thought of as an "in place" process in which the application's binaries and data are upgraded from the previous version to a newer version. For example, upgrading from Project Server 2002 to Project Server 2003 was an "in place" process. In contrast, upgrading to Office Project Server 2007 is a data migration process. In this process, Office Project Server 2007 is installed first (on the same computer as the previous version of Project Server or on a different one). Then data from the previous version is migrated. There is no actual upgrade of the binaries. The administrator then has the choice of running both versions concurrently or removing the older version.

Migration Architecture

Migrating data 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.

Migration architecture diagram

The migration tool reads data from the Project Server 2003 database, fixes 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 Project Web Access data and upgrade metadata, is directly written to the Office Project Server 2007 database.

If you had Project Server 2003 integrated with Windows SharePoint Services 2.0, you need to upgrade the Windows SharePoint Services 2.0 server to Service Pack 2 (SP2) and then upgrade it to the latest version, 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 the latest service pack, SP2a, applied. So, if you have other versions of Project Server, you need to upgrade your database to Project Server 2003 SP2a. Similarly, you need to upgrade from previous versions to Windows SharePoint Services 2.0 SP2 before migration.


Windows SharePoint Services 2.0 was an optional component for Project Server 2003 (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 (Project Web Access is built on top of Windows SharePoint Services 3.0, and Project Server deployment is based on the Windows SharePoint Services farm infrastructure). That is the reason Office Project Server 2007 and Windows SharePoint Services 3.0 are represented on the same server in the diagram above.


The SQL Server files necessary to upgrade from previous versions of Project Server are located on the Office Project Server 2007 installation disk. The files necessary to upgrade from SharePoint Team Services to Windows SharePoint Services 2.0 can be downloaded from the Web.


The command-line migration tool can be thought of as a specialized version of Office Project Professional 2007 without any user interface — so Project Professional and the migration tool cannot be running on the same computer at the same time.

Types of data migration to Project Server 2007

When migrating to Office Project Server 2007, there are three types of data that are migrated: global data, project data and Windows SharePoint Services data.

  • Global data   This includes the following:

    • Enterprise Global Template: This includes custom fields and lookup tables

    • Enterprise resources

    • Project Web Access data. This includes Project Web Access views, Project Server user properties, Project Server admin settings, Project Server security settings (groups, categories, templates) and so on

    Global data can be migrated only once — and this is the first step of the migration process. It is important to note that, once successfully migrated, the global data is never migrated again. If you make any changes to global data in Project Server 2003 after the initial run of the migration tool, it needs to be updated in Office Project Server 2007 manually.

  • Project data   This includes all the enterprise projects, administrative projects, and project templates stored on Project Server. Project data can be migrated gradually in several batches.

  • Windows SharePoint Services data   This includes all the issues, risks, and documents that are stored in the project workspaces, along with the associations between the Project items and Windows SharePoint Services items. Windows SharePoint Services data can be migrated gradually in batches.

Requirements for migrating to Office Project Server 2007

To ensure that your system is ready to migrate to Office Project Server 2007, do the following:

  • Make sure that you have an empty, working Office Project Server 2007 Project Web Access site to migrate into.


    Before you migrate your database for the first time, ensure that the Office Project Server 2007 instance into which you are migrating is clean — no project, no security settings, no enterprise custom fields, and so forth.

    To create a fresh Office Project Server 2007 site:

    1. Install Office Project Server 2007.

    2. Provision a brand new Project Web Access site.

    3. Add the migration administrator account (if it is not already there).

    4. Create a backup of the Project Web Access databases. You can use either the T_SQL BACKUP command or the backup and restore operations found in the Operations page of the SharePoint Central Administration Web site.

    5. Create a resource, create a project from Project Professional 2007, and make sure the newly provisioned Project Web Access site works correctly.

    6. Restore the backed-up Project Web Access databases.


      For more information on installing Office Project Server 2007, see Deploy Project Server 2007 to a server farm environment.

  • Verify that Project Server 2003 Service Pack (SP) 2a has been applied to your Project Server 2003 database.

    • If you have Project Server 2003 with SP2a, your database is ready to migrate.

    • If you have Project Server 2002, you need to migrate your database to Project Server 2003 with SP2a.

    • If you have Project 2000 (also known as Project Central), you need to migrate your database to Project Server 2002, and then again to Project Server 2003 with SP2a.

  • If you integrate with Windows SharePoint Services, make sure that the installation is upgraded to Windows SharePoint Services 2.0 SP2. Also make sure you update the templates to "Project Server 2003 SP2a" (there is a component of SP2a that applies to Windows SharePoint Services).

  • Verify that you have enough space for migration on the computer to which you plan to migrate the database to Office Project Server 2007. Plan for approximately a 1:1 ratio. For example, if your Project Server 2003 database is 10 gigabytes, be sure that you have at least 10 gigabytes of free space available for the migrated Project Server data.


    The Project Server 2003 database can be migrated to Office Project Server 2007 on the same database server computer, or to one located on a different computer.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

See the full list of available books at Downloadable content for Project Server 2007.