Share via

  • Article

Project Server VME: Migrate the Enterprise Global data

 

Applies to: Project Server 2010

Topic Last Modified: 2013-12-18

After running the migration verification in the Project Server virtual migration environment (VME), you must migrate the Microsoft Office Project Server 2003 Enterprise Global data to Microsoft Office Project Server 2007 before you migrate the project data. The virtual migration environment uses the migration tool and calls on a pre-configured configuration file to migrate the Enterprise Global data. The VME automates this process for you.

Single database migration uses the P12SingleMigrationEG.ini configuration file when you run the migration tool to migrate your Enterprise Global file. Split database migration uses P12SplitMigrationEG.ini.

Note

If you need to change the default settings in the migration configuration file, see Configure the migration tool (Project Server).

Migrating your Enterprise Global data is the second step in the VME migration phase. For additional steps, see Project Server VME: Migration phase.

To migrate your Enterprise Global data

  1. On the VME desktop, click Start Migration Process. This opens a Windows Explorer window that displays the contents of drive E.

  2. In Windows Explorer, double-click the following folder:

    • If you have one Project Server 2003 database, open the Migrate_Proj_2003_Single_DB folder.

    • If you have split Project Server 2003 database, open Migrate_Proj_2003_Split_DB.

  3. Click 2-Run EntGlobal-ResPool Migation to start the migration tool. This opens a Command Prompt window that displays the status of the Enterprise Global data migration as it occurs.

  4. When the Enterprise Global migration is completed successfully, the End Summary displays Project Migration successful.

If you encounter an error, check the migration log file for more information about the problem. The specific migration log file for this migration is displayed in the first few lines (for example, "Using log file: E:\MigrationLogs\Batch1-20100503-1704.log"). You can view the log in a text editor such as Notepad.