Contents of the Migration Set

You use the Migration page to create a set of configurations and extensions made to an environment, download the set, and then upload it into another environment. This migration set includes configurations across all product families.

What It Includes

The migration set includes, but isn't limited to these changes:

  • Application changes done using Application Composer:

    • Object UI extensions

    • Object server scripts

    • Saved searches

    • Workflows

    • Global functions

    • Object model extensions

    • Relationships

    • Role security privileges to access objects

    • E-mail templates

    • Custom subject areas

    • Smart actions

    Note: Saved searches created only at the site layer are migrated, not those created at the user or job role layers. So, you need to manually create the saved searches at the user and job role layers in the target environment.
  • Changes made in Oracle Fusion Cloud ERP using Application Composer
  • Changes in functional security settings made in Application Composer, including functional privileges that control access to custom objects. However, not all security changes are migrated.

    Note: If you migrate any functional security associated with roles in the source to a target instance, and the corresponding role doesn't exist in the target instance, an error occurs on import. To avoid these errors, you can selectively create these roles in the target environment when you import your migration set.
  • Changes made to application artifacts using these tools:

    • Page Composer

    • Appearance

    • Structure

    • User Interface Text

    • Page Integration

  • Changes in these artifacts of the Applications Core Setup application:

    • Messages

    • Lookups

    • All data security policies for standard and custom objects, including standard and custom policies.

      Note: Data security policies that are created using these tasks in the Setup and Maintenance work area aren't migrated:
    • Descriptive, extensible, and key flexfields, and value sets that have been deployed

    • Deep links

  • All published configurations within sandboxes

  • Changes in Reports and Analytics, such as regeneration of SOAP services, including user-defined attributes

What It Might Include

Depending on what modules you select during export, your migration set might include these changes:

  • Changes in CRM email templates created in Application Composer

  • Changes in flexfields and value sets

  • Changes in the Enterprise Scheduler Service (ESS) module:

    • Job definitions

    • Job sets

    • Job schedules

    • Incompatibilities

    • Work shifts

    • Work assignments

    • Work assignment schedules

    • Job request parameters

  • Changes in Service Oriented Architecture (SOA) artifacts, such as configurations done using SOA Composer

  • Changes done using Oracle Transactional Business Intelligence, including but not limited to these features:

    • Oracle Analytics Answers

    • Oracle Analytics Delivers

    • Business Intelligence Composer

    • Dashboard Builder

    • Oracle Analytics Publisher

    Note: You can move configurations done using business intelligence tools only if the Business Intelligence in Configuration Set Migration Disabled profile option is set to No.

What It Doesn't Include

Your migration set doesn't include these items:

  • The following Application Composer changes:

    • Object artifacts that were generated to make extensions available for importing and exporting (generated either automatically when you publish a sandbox or manually from the Import and Export page in Application Composer)

    • User names and passwords for secured SOAP web service connections

    • The enabled attachment feature for custom objects

  • Personalizations

  • Application extensions created using Visual Builder Studio. You must deploy application extensions to the production environment instead of migrating them.

  • Changes in activity types and subtypes

    Note: Activity types and subtypes are performance metrics that managers use to track the performance of their team members. For example, email is an activity type that sales managers can use to track the performance of their salespeople. The subtypes of this activity type can be outbound and inbound. Managers can use activity subtypes to track more details about an activity type.
  • Deletions, for example, the migration set doesn't include the removal of a custom object. After you import a configuration set into the target environment, you must examine the environment for any deletions that you must make manually.

  • Profile options

  • Roles or role hierarchy changes

  • Custom roles that aren't assigned to custom objects in Application composer

  • Security Console changes, including these changes made directly in the Security Console:

    • Enterprise roles

    • New duty roles

    • Role hierarchy changes

    You must migrate your custom role and role hierarchy changes from the source environment to the target environment using a .csv file.