Administering Cloud EPM: The Platform Beneath the Business Processes · Module 5 · Business Processes and Migration
Migration: the concepts
Lesson 55 of 201 · 2 min
Migration here means moving an application, or its artefacts, from one environment to another. Typically test to production, production to test, or from a legacy platform into a current one. The vehicle is a snapshot. Module 12 covers snapshots properly. For now: a snapshot is what you move. Three journeys. Within an estate — test to production, production to test. Routine. From a legacy subscription — older platform snapshots into current environments. Between business processes — for instance, from Profitability and Cost Management into Enterprise Profitability and Cost Management. VERSION COMPATIBILITY IS THE SINGLE MOST COMMON MIGRATION SURPRISE. A snapshot from an older release may or may not import into a newer environment, and the rules are specific. Check before promising. Some things are environment-specific and are not carried by a snapshot. Know the list for the business process you are working with — it is a different list per…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 5 · Business Processes and Migration
- 1One environment, one business process
- 2Creating from the Standard landing page
- 3Creating from the Enterprise landing page
- 4Switching business processes
- 5Migration: the concepts
- 6Migration paths by business process
- 7Performing a migration
- 8Transitioning the data management business process to standalone
- 9Essbase in Cloud EPM
- 10What breaks
- 11Lab: create, migrate, and write the plan