Planning data migration is not supported in Lifecycle Management.
Some Planning artifacts have dependencies; for example, forms have dimension dependencies. Instead of migrating only the dimension members required for a form, Lifecycle Management migrates the entire dimension. See Migrating Artifacts.
Lifecycle Management migration to and from Planning is a long-running operation.
Essbase must be in Shared Services mode to use Lifecycle Management.
Essbase artifacts and the Business Rules artifacts display under the Planning application node.
The source and destination applications must have exactly the same settings for Plan Type, Calendar, and Single- or Multi-currency.
In previous releases, Shared Services Console provided an “Include Dependent Artifacts” option for Planning. This option is no longer available. Instead, you must manually select any necessary dependencies.
If Planning does not exist in the target environment, you can use Lifecycle Management to create an application shell. See Creating a Planning Application Shell.