Migration diagram

The following diagram provides a visual representation of your overall migration path when you migrate from IBM Websphere Commerce Version 7 or IBM Websphere Commerce Version 8 to HCL Commerce Version 9, including your development and runtime environments.

While it is likely that your migration is completed in planned chunks, it’s worthwhile to understand how these chunks fit together in a high-level migration flow.

The following diagram does not include the planning or preparing phases of the migration, such as setting up hardware and documenting custom assets. But it does assume that you installed a Version 9.0+ HCL Commerce development environment, and set up your HCL Commerce Version 9+ production environment, including your CI/CD pipeline and production containers.

Graphical representation of the complete migration flow.

Your development database and custom assets are migrated to HCL Commerce Developer Version 9.0+. Your staging and production databases are migrated through HCL Commerce Version 9.0+.

When you migrate your database, you use the database migration utility.

There is no application migration utility. You manually migrate your custom assets across the HCL Commerce Developer versions. By not using migration utility to migrate your custom assets, you can pick and choose which assets you want to migrate and which assets you want to abandon in favor of new functionality.

When you migrate your live production database, you can continue to serve customer traffic throughout the database migration process. While the IBM Websphere Commerce Version 7 or IBM Websphere Commerce Version 8 database is migrated to HCL Commerce Version 9, you continue to serve traffic through your IBM Websphere Commerce Version 7 or IBM Websphere Commerce Version 8 environments. You switch traffic to your HCL Commerce Version 9 environment after the database is migrated to HCL Commerce Version 9.