Pipeline-Based Job to Step-Based Job Migration

Use the B2C Commerce Business Manager migration option to migrate legacy pipeline-based custom jobs to step-based jobs.

To take advantage of the benefits of the B2C Commerce new job framework, we recommend that you migrate legacy pipeline-based custom jobs to step-based jobs. A pipeline-based job migrated to a step-based job preserves the job’s business function, and takes advantage of the new job framework. You find the migration option in Business Manager > Administration > Operations > Jobs (Deprecated). You have full control over which job is migrated to the new job framework, and when the migration takes place. If there are no job steps that perform the functions of your legacy job pipeline, you can create custom job steps.

The migration is a manual per-job process. The process automatically performs the following steps:

A new custom job is created with the same details as the legacy job.
The migration process is logged and is accessible from the global jobs log file.
The migrated job is renamed. The string Migrated is added to the ID
Previous executions of the job are accessible from the Job History (Deprecated) module under the new name.
The legacy-migrated job and its data is only visible to administrators.
The legacy-migrated job data can’t be changed, exported, or imported.