Migration diagram

The following diagram provides a visual representation of your overall migration path when you migrate from Feature Pack 6+ (version 7.0) or WebSphere Commerce Version 8 to version 9.0, including the 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 WebSphere Commerce Developer Version 9.0, and set up your version 9.0 production environment, including our CI/CD pipeline and production containers.

The numbers on the diagram correspond to main steps in each of the following migration flows:

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

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

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

When you migrate your live production database, we can continue to serve customer traffic throughout the database migration process. While the version 7.0 or version 8.0 database is migrated to version 9.0, you continue to serve traffic through your version 7.0 or version 8.0 environments. You switch traffic to your version 9.0 environment after the database is migrated to version 9.0.


Related reference
Overview of a migration project
Creating a migration plan