Do not use Lifecycle Management as your only means of backup and recovery. See Backup and Recovery.
Deployment metadata artifacts contain physical server names and configuration information for the deployment. This information should not be migrated from one environment to another (for example, from Dev to Test). Migrating this data would corrupt the configuration information on the destination environment and would make the system unusable. See Deployment Metadata and Lifecycle Management.
Lifecycle Management migration fails for artifacts and folders with the same name as a Windows-reserved name; for example, CON, PRN, AUX, NUL, and so on. (For a complete list of reserved names, refer to the vendor's site for your operating system.)
Financial Management data migration is not supported in Lifecycle Management. For information on migrating Financial Management data, see the Oracle Hyperion Financial Management Data Migration white paper located at http://www.oracle.com/technetwork/middleware/bi-foundation/resource-library-090986.html.
Planning data migration is not supported in Lifecycle Management.
When performing a Planning migration, it is recommended that you perform the import operation in a specific order. See Migration Order Best Practices for Planning.
When performing a Reporting and Analysis migration, you must manually recreate clients/data sources for Production Reporting and Interactive Reporting on the target machine. See Configure the Production Reporting Job Service Properties on the Destination Application and Create Interactive Reporting Data Access Service Data Sources in the Destination Application.