Best practices for migrating Planning Server data

The importance of including test, development, and production environments in your PerformancePoint Planning Server operation cannot be overstated. This system allows you to build in the development environment, test your changes in the test environment, and then perform real world work in the production environment.

 Planning Server data should be migrated in one direction only, from the development environment to the test environment to the production environment. Do not migrate data backwards, from your production environment to test and development.  Backward migration can cause problems with business rules, permissions, and roles that can exist in the production environment but not in the other environments.

Migrating Planning Server data involves a source environment and a destination environment. All new additions to the environment should be performed at the source environment prior to migrating to the destination environment.