Overview of Migration
You can move your configurations from the test environment, which is the source, to the production environment, which is the target. You can also update your target environment with application extensions made using Visual Builder Studio.
You use the Migration page to create a migration set and export it from the source environment, and then import it into the target environment. A migration set is a JAR file that contains all your configurations across all product families, such as Oracle Metadata Services repository, JEDI, CRM, and BI. Changes you export from the source environment can't be merged with any changes you manually make in the target environment. As such, you must never configure the target environment directly.
When you migrate your configurations, you have the option to migrate only new changes from the source environment to the target environment. For migrating only new changes, you must synchronize both environments by registering the target environment in the source environment. When you register the target environment, your migration set is automatically set to the target environment for import. Otherwise, you have to manually download the migration set from the source environment, and manually upload it into the target.
Your migration set is imported into a sandbox instance before it's applied to the target environment. You can preview your configurations in this sandbox instance before applying them to the mainline.