Migration Tips and Considerations

• When using Import From Source or Connect To Destination to migrate content, both sites must use the same major update. The migration of content can only occur across minor updates within the same major update.

  • "Major update" = Update 23A

  • "Minor update" = Update 23A Patch 1

• When using Migration Packages, content from 19A and forward can be uploaded to the latest site version.

• Oracle CPQ does not recommend migrating between blank and Standard Processes due to dependencies and validation issues. The following methods are recommended:
  1. The preferred method is to perform granular migration of only attributes and actions that don't exist in the Standard Process.
     1. The source attributes and actions should not have any customizations or dependencies with other attributes, actions, or rules.
     2. All customizations need to be manually added to the target Standard Process.
  2. The second and more secure option is to manually create everything from scratch in the Standard Process.

• Only deployed data can be migrated. The Migration Center shows the differences between the deployed data in both sites. On the target site, migrated components are automatically deployed. For example, if a Commerce Process is migrated from source to target, the Process will be deployed on the target site after the migration is finished.
• When migrating Configuration items administrators should deploy all product families prior to a Configuration migration to ensure that All Product Family items are implemented across all Product Families and do not cause orphan issues during migration.
• In order to migrate a Commerce Process, Allow Commerce Processes to be Cloned and Migrated must be set to Yes on the Commerce Settings page.

• Large Document Designer templates should be migrated individually.

• A migration cannot be performed while a Rollback is in progress or while a Snapshot is being applied.
• Only one migration can be performed at a time.
• A Package cannot be imported or downloaded while a migration is in progress, a Rollback is progress, or a Snapshot is being applied.
• Data Columns can be deleted through Migration. Deletion of a Data Column via Migration will have the same effect on Transaction Manager Views and Reports on the target site as if it were deleted in a Rollback.

• A component created manually or through bulk services on the source and target instances are not considered equivalent for migration purposes, even if they have the same variable name.

  For example, a Commerce Process on the source site with the variable name "myProcess" is not equivalent to a Commerce Process created manually on the target site with the same variable name. The process "myProcess" should have been created on the target site through migration, for it to be equivalent to the Process with the same variable name on the source site.

  Attempting a migration in this case will throw an error. To proceed, delete the manually created component on the target instance and then perform the migration.

• Items not available in the Migration Center can be migrated by using Bulk Upload/Download. Some examples include Accounts, Commerce Transactions, and Parts. See the topics Bulk Downloads and Bulk Uploads for more information.

Before migrating, be aware of dependencies. For example:

• Migrate Util Libraries used in Product Families and Commerce Processes before, or with, a Configuration or Commerce migration.
• When migrating, Util Libraries that are referenced by selected Commerce Processes and Configuration Product Families will be listed in the Dependencies dialog box. An individual Util Library will be shown even if it was selected in the main window at the start of migration. Select the Util Library in the dialog box even if it has already been selected in the main window.
• Upload Data Tables before migrating Util Libraries, Configuration, or Commerce.
• Migrate Product Definitions before Catalog data.
• Migrate Configuration data after migrating Catalogs.
• For newly created Commerce Processes, migrate the Commerce Process before migrating Documents.
• When performing granular migration of Commerce UI Layouts that have a dependency on elements other than layout-level elements, those elements (such as formulas, steps, etc.) must be selected or migrated prior to the migration of the Commerce UI Layouts. During the Commerce UI migration the entire layout on the target site is replaced with the one imported from the source site or an import package. If a dependent element, such as a table, is not available on the destination site, the Migration Log displays an error.

• Nominate one FullAccess user to perform migrations. When a Migration fails the admin will receive an email containing a log of the failed Migration stage and the reason for failure.
• Establish a process for migration.
• Migrations should always be performed in one direction. For example, always migrate from the test site to the production site and not the other way around.
• The URL of the source site can be set to auto-populate when connecting to a source site from the target site target site. Open a ticket on My Oracle Support to set the URL that should auto-populate.