Migrate promotions

The Management Center Promotions tool updated in Feature Pack 4 significantly changes the promotion data model. This change requires that promotions made in earlier versions of WebSphere Commerce be migrated so that they work properly in the Promotions tool for the Feature Pack 4 Management Center. A promotion migration utility is provided for this purpose.

  • Promotion migration planning

    With Feature Pack 4, the Management Center Promotions tool uses a new data model for managing promotions. If you have existing promotions created prior to Feature Pack 4, and if you want to manage them using the Feature Pack 4 Management Center, migrate the existing promotions using the promotion migration utility. Before migrating, use the information in this topic to plan the migration steps take.

  • Migration limitation for certain order-level promotions

    When you create promotions in WebSphere Commerce Accelerator, you can choose the exclusivity option "Can not be combined with product promotions" in the "Combination with other promotions" field for certain order-level promotion types. This exclusivity option is not supported in the Feature Pack 4 Management Center user interface.

  • Migrate promotions built on default promotion types: complete migration

    For this type of migration, typically, you run the promotion migration utility using the default configuration files and XSL templates; however, in a certain case, create a custom Config Info configuration file to specify an option that is not the default setting.

  • Migrate promotions: partial migration

    For this type of migration, you create a custom version of the Control Info configuration file to specify a partial migration for each promotion type. If you have promotions built on custom promotion types, you create a custom XSL template to transform the promotion to the new data model. Then you run the promotion migration utility using a parameter that calls the custom Control Info configuration file.

  • Migrate promotions built on custom promotion types

    For this type of migration, you create a custom XSL template for each custom promotion type and a custom version of the Control Info configuration file. Then you run the promotion migration utility using a parameter that calls the custom Control Info configuration file. You can choose either a partial or complete migration for each promotion type.

Related concepts

Promotion migration planning
Migration limitation for certain order-level promotions

Related reference