R is considered the predominant language for data scientist and statisticians. Learn how to use R for your own data science projects.
The following parts will walk you through the steps involved in getting your store migrated with a mix of manual efforts and automation.
An ideal check on your extensions should include a check on:
– List of extensions used – List of extensions that you don’t need anymore – Specific data from extensions that needs to be migrated
In case you are using third-party extensions, make sure you find their respective Magento 2.x counterparts in the Magento marketplace. Else, you will have to rebuild those from scratch.
– Prepare a hardware system keeping in mind the system requirements and install Magento 2.x.
– Install the Magento Data Migration tool.
– To add exceptions for data which you don’t want to migrate, you should perform custom changes in the Data Migration Tool.
Before getting into the migration part, check whether the network access is available for the Data Migration Tool to connect to Magento 1 and Magento 2 databases.
– Identify the list of custom modules in the current version; check if the customization has an impact on core modules. If yes, those modules should be migrated on priority. Then follow with the migration of the remaining custom modules.
– Stop cron jobs and activities in the Magento 1.x Admin Panel.
(Note: Do not stop the incremental activities like new orders, inventory updates, invoices etc until the new website is completely live)
– Migrate the store settings and website.
– Perform manual copying of media files from Magento 1.x to the 2.x store.
– Make use of the Data Migration Tool to bulk upload the database from Magento 1 to 2.
– To migrate data gathered by extensions, you will have to download the Magento 2.x compatible version of the same extension.
– If there are differences in the structure of the custom modules and extensions in the 1.x and 2.x versions, use the mapping files provided with the Data Migration Tool to set things right.
– Reindex all Magento 2.x indexers.
– There will be issues encountered at every step, so these should be addressed until you get a clean version.
– Do a thorough overall integration test to ensure the application is devoid of any critical issues.
Remember, your incremental data like reviews, comments, orders placed, auto invoices raised are yet to be updated to your new Magento 2.x store.
– Once the store settings and extensions data have been moved, start moving your incremental data.
– Initiate migration of the incremental updates and simultaneously check for issues as well.
(Note: The incremental data should not be moved by copying Magento 1.x store data from live site to a staging server. Instead, it has to be moved from the live Magento 1.x server)
– In the case you find any issues, the incremental data updates can be stopped by pressing ‘Ctrl + C’ to fix those issues and then resume it back.
It is now time to officially call off your Magento 1.x store and dive into your Magento 2.x store.
– Turn the maintenance mode on for your Magento 1 store. (from here the downtime of your Magento 1.x store starts)
– Start the Magento 2 cron job.
– Cache the pages in your Magento 2 site using any caching tool of your own preference.
– Check your Magento 2 store thoroughly.
– Change server settings directing it to Magento 2 ( Magento 1.x downtime )
– And now you are live! Your new Magento 2.x store is ready for you and your users.
You are good to go with your Magento 2.x version of your eCommerce store.
These guidelines will help in the planning of your Magento 2 migration, each implementation has its own specific nature, so you will need to apply these guidelines appropriately.
Author: Mark Richard