1. Migration of configurations includes:
   • Classes
   • Structure
   • Unit of Measure
   • Approved Manufacturer List (AML)
   • Change Orders
2. Three paths can be used for the migration of configurations 
   • Agile to Cloud
   • GoStart to the final template (used for new implementation)
   • Dev platform to next

Agile PLM to Oracle PLM Cloud Workflow 

1. Using Agile PLM, GoStart is populated  
   • A Configuration Package is exported from Oracle Product Development Cloud and configurations are exported from Agile Product Lifecycle Management using Agile Configuration Propagation (ACP) in .agl format
   • Using the Configuration Migrator, configurations are converted to GoStart format
2. A customer review with GoSaaS takes place to customize GoStart and discuss the mappings & limitations in the movement from Agile PLM to Oracle PLM Cloud
3. The template (GoStart) is then ready to be applied to Oracle PLM Cloud using the Configuration Migrator
   • The Configuration Migrator uses the configurations in GoStart and updates the Configuration Package 
   • The updated Configuration Package is then uploaded to Oracle Product Development Cloud

New implementation Workflow  

1. The user starts off with a pre-configured industry specific template, GoStart, as a basis for configurations
2. After a customer review to make GoStart completely according to the customer, it is ready to be imported to Oracle PLM Cloud using the Configuration Migrator after which validations take place.
   • A Configuration Package is exported from Oracle Product Development Cloud and GoStart is populated with configurations consisting of Parts, Value Sets, BOM, Manufacturer Parts, Change Order, UOM Class, and Unit of Measure
   • The GoSaaS Migrator uses the configurations in the GoStart and updates the Configuration Package
   • The updated Configuration Package is then ready to be uploaded to Oracle Product Development Cloud