Planning and sizing sample template for a migration

Modify the template to reflect your level of customization, site topology, and business requirements to help plan your version 7.0 or 8.0 migration to version 9.0.

A template that can be used to plan and size your migration project.
Task	Sub Task	Estimated duration	Complexity	Owner(s)	Assumptions, Comments
Site analysis and preparation	Review the current site, and collect: Design documentation Use cases Custom code
	Review the new features and changes made in HCL Commerce 9.0.
	Gather new requirements
	Review deprecated and removed APIs and determine how you are going to address each one.
	Review all custom scripts that are used for tasks such as build, deployment, or data load.
	If you have previously customized Management Center, review any changes that affect your customizations and determine how you are going to address each one.
	If you have connections to external systems, you need to ensure that there are test stubs / test connections available for your migration team to use.
	Review traffic statistics for your site and project statistics for the future. Use this analysis to determine if you are going to need to purchase new hardware. Procuring hardware can take time, and you want to include this in your project plan.
Technical staff education	Education on how to utilize the new CI/CD pipeline.
	Education on how to plan and execute your container infrastructure.
	Education on developing with JPA technology.
Build your container platform and CI/CD pipeline	Determine which software you want to use to build a container platform that can support the HCL Commerce application.
	Create your strategy for frequently deploying new features, updates, or fixes to your production environment.
	Implement your container platform and CI/CD pipeline, including your staging and production environments.
	Configure the HCL Commerce Build (WCB) tool.
Development environment migration	On an existing HCL Commerce Developer installation, perform a regression test of all custom code to ensure that there is no confusion as to what the source of problems are after migration is complete.
	Ensure that you meet all prerequisites.
	Install and configure HCL Commerce Developer.
	Migrate site your security, configurations. Then, migrate the development database.
	Migrate your remaining assets (make a new row for each custom asset, or create a new document to track all custom assets). For example, the most time consuming tasks tend to be: Fixing deprecation and compilation warnings EJB to JPA migration Store migration Search migration
	Test the migrated application in the development environment.
	Build your migrated custom assets by using the WCB tool and deploy your assets to your HCL Commerce application. Then, test your custom assets within your production environment.
Production server migration	Take a backup of your version 7.0 or 8.0 production database, then restore the version 7.0 or 8.0 production database copy on version 9.0 production environment.
	Migrate the restored/offline database.
	Test your migrated customizations at runtime against the offline database while tuning for production site traffic volumes.
	Back up live version 7.0 or 8.0 database.
	Point your version 9.0 environment to the live version 7.0 or 8.0 database.
	Migrate the live database while still serving traffic.
	Switch traffic from version 7.0 or 8.0 environment to version 9.0 environment.
	Update SITE table on live database.
Test the migrated site
Get education for the day to day maintenance
Post launch support
Project management
Contingency (for unknown or unexpected issues)
Total project hours: