Migrate Catalog Definitions

Use this topic to understand how you can migrate catalog definitions from one Launch application to another.

All the entities migrated are assigned to a single project to manage the publish process. The migration process is flexible and enables you to migrate entities individually or you can migrate an entity along with its references. There's an option to include references (migrate with references) in the migration process. When you select migrate with references, all the references of the entities are migrated and included as a part of the same initiative. You can select any entity separately or an entire initiative for migration. When you select an initiative, all the project items are migrated along with it.

You can migrate catalog definitions in the following ways:

• One at a time: Enables you to migrate one entity at a time. For example, a product specification, product line, simple offer, bundle offer, price list, and so on. However, you must ensure that the referenced entities are either in the same project or already in a lifecycle status of Active or Launched. For example, you could choose to migrate product specification, while ensuring that its dependent service specifications, usage specifications are in place. This also applies for the hierarchy while migrating product offer to have its associated product specifications in the application.
• The entire structure in one go using"migrate with references" option: For example, a Package type offer along with its bundles, both commercial and service bundles, simple offers, price lists, terms, product lines and category associations.

This is the sequence in which you must migrate catalog entities:

1. Project
2. Catalog
3. Category
4. Balance Element
5. Price List
6. Tax Service Provider
7. Customer Profile Specification
8. Custom Profile Specification
9. Usage Specification
10. Pricing Logic Algorithm Specification
11. Product Line
12. Product Offer Price
13. Product Offer
14. Pricing Logic Algorithm
15. Pricing Constraints
16. Product Rule
17. Promotion
18. Entitlement

Here are the steps to migrate:

1. Go to Administration > Job Management > Migration Jobs.
2. Click Create Migration Job and select Source as launch.
3. Select the entity type to migrate.
4. Select the option migrate with references. This is optional.
5. Add the query parameter and select ID and its value for the entity to be migrated.
6. Provide your configured source's preselection key in X-Source-Preselection.
7. Click Submit.

You can now track the migration job from the migration job landing page.

Set Up the Integration

To set up this integration, ensure that you've registered the source Launch instance and validated the integration between the applications.

For more information, see the article CX Industries Framework (Doc ID 2720527.1) on My Oracle Support.