Magento 1 to 2 migration plan
This entry was posted on Thursday May 30, 2019Scope planning (determining what elements of your store will transfer to Magento 2)
Consider your timing: plan a start date and milestones for other parts of the plan.
Write down what UX features will be migrated or added, like mobile compatibility.
Revise the requirements for the data that will be converted: content, customers, products, etc.
Document every customization that is involved in customer experience.
Note down every extension used in the store.
Note down all necessary integrations for payments, taxes, logistics, etc.
Define the current numbers and KPIs of the store: conversion rate, site traffic etc.
Budget planning (noting every obligatory and possible expense)
Platform setup/implementation.
Custom development/integration, like customer experience improvements and extension installation.
Quality Assurance.
Licensing and hosting costs.
Further ongoing support.
Deployment planning (preparing the development team and the project)
Create a timeline for implementation, based off of the points of scope planning.
Have a communication plan ready, for both customers and the team, regarding the migration: who, when and how.
Have a plan B, in case a migration goes wrong and there is a need to reestablish the store.
Post-deployment planning (getting the store back on track)
Revise the key metrics: conversion rate, orders, traffic, etc.
Turn to the official upgrade checklist before applying any changes
Make sure that the file system owner group is granted the write access to the directories and files.
Verify that your cron jobs are working correctly and check all related system messages. Three cron jobs need to be running under the Magento file system owner.
Make sure you have specific file permissions set according to security requirements.
For Magento versions 2.2 and higher the checklist recommends to setting a specific data for DATA_CONVERTER_BATCH_SIZE.