Project Server 2007 migration quick reference

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 article provides a high-level overview of the procedures needed to migrate Microsoft Project Server 2003 to Microsoft Office Project Server 2007. It does not cover Microsoft Windows SharePoint Services migration and does not give you detailed guidance on each procedure or information on how to troubleshoot problems. For detailed information, refer to the content elsewhere in this guide.

General migration procedure for Office Project Server 2007

  1. Install Office Project Server 2007 and provision a Microsoft Office Project Web Access site.

  2. Back up your clean Office Project Web Access databases (all four of them). If you run into problems, you can restore the databases and start over again.

  3. Prepare your Project Server 2003 database. Restore an existing Project Server 2003 database onto the same computer running SQL Server as the one hosting the Office Project Server 2007 database. If this not possible, in SQL Server you can also create a linked server on the Office Project Server 2007 SQL Server and link it to the Project Server 2003 SQL Server.

  4. Do the pre-migration verification and cleanup. (For more information, see Pre-migration verification and cleanup.)

  5. Install Microsoft Office Project Professional 2007 and in the Advanced option in setup, choose Install migration tool. (This option is cleared by default).

  6. Change the default migration initialization file that is installed with Project Professional. (You can find it at \Program Files\Microsoft Office\Office12\P12MIGRATION.INI.SAMPLE.) Specify the correct values for Project Server 2003 databases, Project Server 2003 linked SQL Server, Project Server 2007 Project Web Access, and so on.

  7. Run the migration tool: "<drive>:\Program Files\Microsoft Office\OFFICE12\p12migrationtool.exe" -c "<location>\p12migration.ini".

  8. Look at the command prompts and the migration log to make sure that there are no errors. If there are errors, make corrections and re-run the migration tool. If there is an irrecoverable problem, make changes in Project Server 2003 and try again. If the global migration failed at any point, re-run migration from the beginning after restoring the clean Office Project Server 2007 databases.

  9. If you have any local Windows accounts (for example, <ComputerName\Brad Joseph>), and the computer names are no longer valid, make sure you edit those accounts in Office Project Web Access so that they are valid.

  10. In Office Project Web Access Server Settings, in the Operational Policies section, select Project workspace provisioning settings and choose Automatically create a project workspace. This is the more common option. If you do not want workspaces to be created automatically, you need not do this.

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.