Migrating older versions of Project Server and Windows SharePoint Services

  • Article

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

In this article:

  • Migrating from Project Server 2002 to Office Project Server 2007

  • Migrating from Project Central to Office Project Server 2007

  • Migrating from SharePoint Team Services

  • Migrating complex datasets and licensing

This article describes the procedures required to migrate from two earlier versions of Project Server to Microsoft Office Project Server 2007:

  • Project Server 2002

  • Project Central (used with Project 2000)

  • This article also describes the process of migrating your project workspace data, for those who have been using SharePoint Team Services (also called Windows SharePoint Services 1.0) with Project Server 2002.

Migrating from Project Server 2002 to Office Project Server 2007

Following are the high-level steps:

  1. Migrate to Project Server 2003: Follow the instructions in Upgrading to Project Server 2003 from Earlier Versions of Microsoft Project (https://go.microsoft.com/fwlink/?LinkId=78241\&clcid=0x409). In the documentation, there are references to a "Support" folder on the Project Server 2003 CD. This folder corresponds to the Utilities\Migration folder on the Office Project Server 2007 CD, which contains all the SQL files required for migration.

  2. Apply Project Server 2003 Service Pack 2a: For more information about the service pack, see the Knowledge Base article named Description of Project Server 2003 Service Pack 2a (https://go.microsoft.com/fwlink/?LinkId=78242\&clcid=0x409). All the SQL files required for applying the Project Server 2003 SP2a database upgrade are available in the Utilities\Migration\Database\PS03SP2a folder.

    Note

    You do not need to upgrade the Project Server 2002 application itself to Project Server 2003.

    To migrate from To Use

    Project Server 2002

    Project Server 2003

    SQL script UPG10DB (in the Utilities\Migration\Database folder on the Office Project Server 2007 installation media)

    Project Server 2003

    Project Server 2003 SP2a

    Command script Upgdb112.cmd (in the Utilities\Migration\Database\PS03SP2a folder on the Office Project Server 2007 installation media)

    The following illustration shows the process.

    Upgrade path from Project Server 2002

    Warning

    Make sure to use a backup copy of your Project Server 2002 database when running the UPG10DB SQL script. If you migrate the Project Server 2002 active database to Project Server 2003, Project Server 2002 will no longer function.

Migrating from Project Central to Office Project Server 2007

Following are the high level steps:

  1. Migrate to Project Server 2003: Follow the instructions in Upgrading to Project Server 2003 from Earlier Versions of Microsoft Project (https://go.microsoft.com/fwlink/?LinkId=78241\&clcid=0x409). In the documentation, there are references to a "Support" folder on the Project Server 2003 CD. This folder corresponds to the Utilities\Migration folder on the Office Project Server 2007 CD, which contains all the SQL files required for migration.

  2. Apply Project Server 2003 Service Pack 2a: For more information about the service pack, see the Knowledge Base article named Description of Project Server 2003 Service Pack 2a (https://go.microsoft.com/fwlink/?LinkId=78242\&clcid=0x409). All the SQL files required for applying the Project Server 2003 SP2a database upgrade are available in the Utilities\Migration\Database\PS03SP2a folder.

    To migrate from To Use

    Project Central

    Project Server 2002

    SQL script UPG09DB (in the Utilities\Migration\Database folder on the Office Project Server 2007 installation media)

    Project Server 2002

    Project Server 2003

    SQL script UPG10DB (in the Utilities\Migration\Database folder on the Office Project Server 2007 installation media)

    Project Server 2003

    Project Server 2003 SP2a

    Command script Upgdb112.cmd (in the Utilities\Migration\Database\PS03SP2a folder on the Office Project Server 2007 installation media)

    The following illustration shows the process.

    Upgrade path from Project Central

    Warning

    Use a backup copy of your Project Central database when running the UPG09DB SQL script. If you migrate the Project Central active database to Project Server 2002, then Project Central will no longer function.

Migrating from SharePoint Team Services

Project Server 2002 integrates with SharePoint Team Services (also known as Windows SharePoint Services 1.0).

SharePoint Team Services provides project workspace functionality for Project Central. When migrating from Project Central to Office Project Server 2007, you can also migrate your project workspace data.

Following are the high-level migration steps:

  1. Upgrade project workspaces on SharePoint Team Services to Windows SharePoint Services 2.0. (Project Server 2003 integrates with Windows SharePoint Services 2.0.) Follow the instructions in Upgrading to Project Server 2003 from Earlier Versions of Microsoft Project (https://go.microsoft.com/fwlink/?LinkId=78241\&clcid=0x409). In the documentation, there are references to a "Support" folder on the Project Server 2003 CD. This folder corresponds to the Utilities\Migration folder on the Office Project Server 2007 CD, which contains all the SQL files required for migration.

  2. Upgrade project workspaces in Windows SharePoint Services 2.0 to Windows SharePoint Services 2.0 SP2.

  3. Upgrade Windows SharePoint Services 2.0 SP2 to Windows SharePoint Services 3.0. (Project Server 2007 integrates with Windows SharePoint Services 3.0.) For more information, see Upgrading to Windows SharePoint Services 3.0.

Migrating complex datasets and licensing

If you are migrating from older versions of Project Server and just running the database update scripts (as described above), you do not need to purchase licenses for Project Server 2002 and Project Server 2003 — because you are simply upgrading the database to Project Server 2003 SP2a format, not the actual application binaries.

But if you have a complex dataset (a number of custom fields, complex master sub-project relationships, and so forth), we recommend that you check your data after every step of the migration — and this would involve not just upgrading the database, but upgrading the server as well (requiring you to purchase a license for the product). For example, after upgrading your database from Project Central to Project Server 2002, we recommend that you also upgrade the server to Project Server 2002 and verify that your data looks correct (requiring you to purchase a license for Project Server 2002). If the data is not correct, apply any fixes or workarounds related to this upgrade. Once this is verified, then upgrade your database to Project Server 2003 SP2a, also upgrade the server to Project Server 2003 SP2a, and verify your data again. Then, as the last step, migrate to Office Project Server 2007. Although time-consuming, this method is the safest way to proceed when migrating from a version other than Project Server 2003. This method allows you to narrow your troubleshooting tasks if the migration to Office Project Server 2007 should fail. For example, if the migration from Project Server 2003 SP2a to Office Project Server 2007 fails, you might think it is an issue with the Office Project Server 2007 migration tool, when in fact it might be an issue with the previous migration from Project Central to Project Server 2002, or when migrating from Project Server 2002 to Project Server 2003 SP2a.

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.