Migrating Planning Server data

Updated: 2009-04-30

You can use PerformancePoint Planning to customize your application to support your business requirements, thus building an environment that matches your needs. Create complex customizations using PerformancePoint Planning Business Modeler on your development environment and then migrating it to your test environment. Then, following the Planning migration process, customized metadata on your test environment can successfully be migrated to your production environment, thus eliminating the need to duplicate the work after the migration is complete.

Planning Server data migration is a one-way flow, meaning that all new additions to your Planning Server environment should first be placed in a development or test environment before you move it to the production environment. You should not attempt a reverse migration of Planning Server data from your production environment to any other environments. The migration process should be done in one direction only, from development and test environments to the production environment.

The development environment is where you should create applications and build the associated models. The development environment can be a single computer or several computers in a development group. Next you will migrate the new data to your test environment where the new applications and models changes are tested. The test environment can also be a single server computer or a mirror of your production environment, depending on your requirements. Finally you can migrate the Planning Server data from the test environment to your production environment.

Note that Business Rule conflicts or errors can occur if you migrate any existing Business Rules between environments. For example, if you create Business Rules in your production environment and then migrate Planning Server data from your test environment to the production environment, this can cause errors because the new Business Rules do not exist in your test environment.


All new additions to the Planning Server data should be done prior to your migrating data to the production environment so the changes can be tested thoroughly before the final migration.

Security issues can also occur during a migration. For example, if you create a Business Role with custom security and add users to this role but do not move the users to the new server environment when you migrate the data, the role will no longer work correctly.

After you have completed the customization work and have tested the system in a nonproduction environment, you are ready to deploy the customized Planning. Because most testing environments cannot duplicate the topology and hardware configurations that comprise a fully built production environment, it is unlikely that you can simply use a backup and restore procedure or the Planning mirroring technique described in Mirroring the Planning Server to migrate your system.

The Planning migration process facilitates this process and is detailed in this chapter.


PerformancePoint Planning supports initial system migration and incremental system migration. However, it supports migration at the application level only, not at the model site level.

As with any project, it is important to thoroughly test Planning in a safe test environment before deploying to a production environment.

Overview steps to migration

The major steps involved in migrating Planning to a new destination are shown in following table.

Step Description

Exporting from a source system

Steps and procedures as to what will be migrated from the source system, and how to export from the source system.

Importing to a destination system

Steps and procedures on importing data to the destination system.

Export data from the source system

Steps for exporting reference data and fact data from the source system.

Prepare the staging area

Steps to exporting data from the source system, preparing the staging area, and loading the prepared data.

Load import workflow, security, and report data

Steps to manual import or load import workflow, security, and report data.

Deploy all model sites in the destination system

Steps to deploy all model sites.

Bring the migrated application online

Steps on how to bring a newly migrated application online.

Verify the application migration

Procedures to quickly test application data after the migration is complete.

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 PerformancePoint Planning Server.

See Also