Migrate > Plan to migrate WebSphere Commerce > Create a migration plan


Plan and sizing sample template

This template can be used as a basis for creating the own project planning and sizing. Modify the template to reflect the level of customization, site topology,

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 new features and changes in WebSphere Commerce version 7.          
Gather new requirements          
Review deprecated and removed APIs and determine how you are going to address each one.          
Review all custom scripts used for tasks such as build, deployment, or data load.        
If you have previously performed customization of the Management Center, review any changes that affect the customizations and determine how you are going to address each one.          
If you have connections to external systems, ensure that there are test stubs / test connections available for the migration team to use.          
Review traffic statistics for the 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 we will want to include this in the project plan.          
Technical staff education Education on new development languages. For example, if you are a version 5.6.1 customer who wants to learn to customize the Management Center using OpenLaszlo.        
Education on new features. For example, allotting time to review the Information Center documentation on how to load data.          
Development environment migration On an existing WebSphere 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 you have met all prerequisites.          
Install and configure WebSphere Commerce Developer.          
Migrate the development database.          
Migrate the custom assets (make a new row for each custom asset, or create a new document to track all custom assets). For example, the three most time consuming tasks tend to be:

         
Test the migrated application in the development environment.          
Complete all post migration tasks          
Test environment migration Ensure you have met all the prerequisites.        
Install and configure WebSphere Commerce on the test environment.          
Clean the test database.          
Migrate the test database.          
Migrate the test environment application.          
Complete all post migration tasks          
Complete any additional migration steps.          
Migrate one of the performance test environments, or set up a new performance test environment.          
Run a performance test on the WebSphere Commerce version 7 site.          
Production server migration Ensure you have met all the prerequisites.        
Install and configure WebSphere Commerce on the production environment.          
Clean the production database.          
Migrate the production database.          
Migrate the production application.          
Configure the application and Web server.          
Complete all post-instance and database migration tasks.          
Complete any additional migration steps.          
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:          


+

Search Tips   |   Advanced Search