Importing to a destination system

Updated: 2009-04-30

In this article:

After the application has been exported from the source environment, you are now ready to import it into the destination environment.

The following sections are high-level procedures required to import to a destination system.

First-time migration

Install PerformancePoint Planning software. Refer to the PerformancePoint Server 2007 Deployment Guide for complete installation and deployment details.
Create a new application shell by using Planning Administration Console.
Manually execute the four scripts that were generated.
Run Planning Command Utility with the migrate and import option to import the Planning essential structural metadata from the source system to the destination. (See details below.)
Migrate reference data, which includes dimension, hierarchy, and fact data.

Note

If you want to save changes, bring the application online or put the application in an "Async-Offline" state.
Manually set up and import workflow, security, and report data.
Deploy all model sites at the destination system.
Bring the application online or put it in Async-Offline mode if you want to save the changes but do not want the system online and in a live production environment.
Verify application migration.

Lock the application by using Planning Administration Console.
Run Planning Command Utility with the migrate and import option to import the Planning essential structural metadata from the source system to the destination. (See details below.)
Migrate reference data, which includes dimension, hierarchy, and fact data.
Manually set up and import workflow, security, and report data if needed.
Manually setup Data Sources and Data destinations as needed.
Deploy all model sites at the destination system.
Unlock the application.
Bring the application online.
Verify application migration.

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