What Can Be Migrated?

Overview

The tables below provide a list of the categories and components and can and can't be migrated.

The table below provides a list of the categories and components that can be migrated. It will also tell you if you can view detailed differences between the components on the source site and the target site.

Component	Description	Detailed Differences	Notes
Util Library	Contains a list of the Util Library functions that can be individually migrated from one environment to another.	Available	Add and modify selected Util Libraries through migration. Delete is not permitted through migration.
Product Definition	Contains a list of the Product Families that can be individually migrated from one environment to another.	Not Available	Add and modify specific Product Families through migration. Regular attributes can be deleted through migration.
Catalog Definition	Contains a list of the Product Lines and their subsequent Models that can be individually migrated from one environment to another. This only migrates the catalog hierarchy.	Not Available	Add and modify Product Lines and Models in specific Product Families. Product Lines and Models can be deleted through migration, but Product Families cannot be deleted through migration.
Configuration (See Notes Below)	Contains a list of all the rules and attributes associated with each Product Family. Included are Configuration attributes, rules, Configuration Flows, Search Flows, Integration XSLs, and stylesheets. All Product Family level attributes, rules and stylesheets are included.	View detailed differences between rules by clicking Configuration. View detailed differences of code changes.	Add and modify attributes, rules and layout in specified product families. Attributes and Rules can be deleted through migration, but Product Families cannot be deleted through migration.
Commerce (See Notes Below)	Contains a list of all the Commerce Processes that can be individually migrated from one environment to another.	View detailed differences between actions, attributes and rules View detailed differences of code changes.	Add and modify all component elements of a specific Commerce Process through migration. Components can be deleted via migration, but Commerce Processes cannot be deleted via migration.
Document Engine	Contains a list of Document Engine templates (sorted by Commerce Process) that can be individually migrated from one environment to another.	Not Available	Add and modify templates through migration. Templates cannot be deleted via migration.
Email Templates	Contains a list of Email Templates (sorted by Commerce Process) that can be individually migrated from one environment to another.	Not Available	Add and modify templates through migration. Templates cannot be deleted via migration.
Document Designer	Contains a list of Document Designer templates (sorted by Commerce Process) that can be individually migrated from one environment to another.	Not Available	Add and modify templates through migration. Templates cannot be deleted via migration.
Data Tables (See Notes)	Contains a list of all Data Tables that can be individually migrated from one environment to another.	View low-level differences between Data Tables. View Data Table schema changes	The admin can see the last user to modify each Data Table and when the modification took place, if the Data Table has since been deployed. Data changes will not be shown in the Migration Center, but will be migrated
File Manager	Contains a list of files and files folders from the File Manager that can be migrated one at a time.	Not Available
Part Custom Fields	Contains a list of part custom fields that can be migrated.	Not Available

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.

What Can't be Migrated?

The following site components cannot be migrated using the Migration Center.

Component	Sub-Component
Accounts
Configuration	File Attachment Attributes
Header & Footer
Home Page	Punch-Ins Access Rights
Integration Settings
Mobile Home Page	Images
Native Reports & Commerce Manager Views
Page Templates
Partner Organizations
Parts	Part Associations Price Books Favorites
Process Invocations
Serial Number area	Includes custom fields
Settings	Configuration Settings Commerce Process Settings General Settings, including: Countries & States Email Signature Favorites General Site Options Navigation Menus Host Company
Stylesheets
Text Administration
Transactions
Users & User Groups

Notes

Product Definition/Catalog/Configuration

All deployed changes within the selected Product Family are migrated. Changes to Product Definition or Catalog Definition must be made prior to migrating Configuration data.
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.
When migrating a new Product Family, the administrators must Activate the Product Family and Deploy the Home Page on the target site to enable the new Product Family in the Configuration flow. Refer to Setting Up Product Families detailed instructions.

Administrators should use caution when using migration packages that contain Configuration layouts and rules. All Product Family attributes are deleted from the target Configuration if a source migration package that contains Configuration layouts or rules without All Product Family references is migrated to a Configuration with All Product Family references. This will cause deployment and Configuration Flow errors for Configurations that reference the deleted All Product Family attribute.

Commerce

Clicking the name of modified Commerce Processes allows you to view specific components of the Commerce Process. If only a translation has been added or modified, the change is not shown in the Migration Center. Translations will be migrated when the Commerce Process is migrated.
Beginning in Oracle CPQ 23A individual selection and migration of Commerce User Interface Layouts (JET Responsive Layouts) is supported. Administrators can now select the Commerce JET Responsive Layouts at the main and sub-document levels and migrate using one of two migration modes: import by source or import package. In addition, if necessary, administrators can roll back the migrated Commerce UI layout. The Commerce UI Layout migration migrates the entire layout including layout elements, attributes, actions, and settings.

Prior to performing granular Commerce User Interface Layout migration, administrators need to evaluate the Commerce UI Layouts for dependencies. If the layouts have a dependency on elements other than layout-level elements, such as formulas, steps, etc., those elements 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.

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.

Data Tables

When migrating Configuration or Commerce, a list of dependent Data Tables will be displayed in a pop-up window. If these Data Tables are not selected, migration will fail. This pop-up will only appear when menu attribute validations are mapped to a Data Table, but not when the Data Table is used in rules using BMQL.
Administrators must include all Data Tables related to Foreign Key relationships in the migration package. This ensures the Data Tables are deployed together for data integrity purposes. Administrators must resolve the error messages in the migration log before they can successfully migrate Data Tables with Foreign Key relationships.

When migration changes attribute menu values, if you delete an attribute or menu value, the link will be removed from the Data Table.

Only deployed changes (to Configuration, Commerce, Data Tables, Email Templates, Document Designer Templates, etc.) will be migrated.