2025 is already here! And this means that the support of Magento 1 went to end in November 2018 as announced. How can this affect your biz? No more security patches, and this can be very influential for some kinds of businesses. On the other hand, Magento 2 becomes more and more stable and trimmed. There is no need to explain dozens of reasons that are speaking in favor of migration. The only question left is how to migrate to Magento 2. So let’s get straight to the point.
💡We have prepared for you:
- 5 steps that are going to guide you through the process;
- SSH commands to simplify your Magento migration;
- code samples;
- qualified pieces of advice from experienced programmers.
No hurry-scurry, just 5 simple steps 🧑💻
1. Preparation for migration
The first stage of work is related to the old website. To rule out of the possibility of any unforeseen consequences, you have to:
- Check the themes, extensions and other custom solutions you use on your Magento 1 for compatibility with Magento 2.
Some of them can be moved, others will have to be recreated on the new system during the Magento 1 to 2 migration. If you need help with customizing the new version of your store, contact our support!
- Make a clone of a Magento 1 store. Use it for the migration process, don’t go on with a live website!
This step implies a sufficiently capacious process. We will definitely shed light on this in one of our next articles!
- Having a duplicate to work with, carry out analysis of it.
The system update is a good opportunity for getting rid of dead loads, such as unnecessary extensions and plugins. Leave the systems you think are useful and kill the rest.
2. Create new Magento 2 store
Install your new Magento 2 store on a staging server. Create it under the same domain name (if it is possible within the constraints of the current architecture). Set it up with similar to your old store topology. Run tests to make sure everything works correctly.
3. Data migration tool installation
Once you have gone through first two steps, the time has come to install a special tool that was developed to make the Magento migration process easier. Pay attention that you have to be logged in to your site server as a user with permissions to edit files.
- Enter the Magento main directory and type this command to make an update of the composer.json file:
composer config repositories.magento composer https://repo.magento.com - To get the required version of the tool, enter the following:
composer require magento/data-migration-tool:2.x.x
where 2.x.x is your current Magento version. Do not forget to substitute the required value!
- To install migration tool itself, enter the following:
composer config repositories.data-migration-tool git https://github.com/magento/data-migration-tool-cecomposer require magento/data-migration-tool:dev-master - After typing these commands, you’ll have to enter the authentication keys.Public key is your username and the private one is your password. See Magento dev docs for more info on these keys.
4. Magento Migration
Once the tool is prepared, let’s get straight to transferring itself. The process is really ponderous, that is why you should minimize the risks that something will go wrong. So, before you start, please check the following:
- Migration tool should have access to both databases, the one to copy from and the one to take data to.
- Magento 1 cron jobs must be stopped.
- Pay attention that any activity in the admin panel has to be excluded until the migration is complete.
- Working with code during the process is also under the ban.
Data migration tool allows transferring default Magento data and settings. Still, if you have some custom extensions with their own databases, you`ll have to use special mapping files that are provided together with this tool. Yet, some kinds of data are to be moved manually. This applies to all media, front-end part (the way your store looks like) and to access control lists.
When Magento data migration process is over, you should reindex your Magento 2 website. Finally, run tests.
5. Launching your Magento 2
When everything is checked and tested (better to do that more than once), it is time to launch your updated store!
- Stop your Magento 1, putting it into maintenance mode.
- Stop migration tool.
- Start cron jobs on your new Magento 2 store.
- DNS load balancers are to be pointed to the new production hardware.
Despite we have tried to compartmentalize the process of Magento 1 to 2 migration, you still can find yourself a little confused. If you are not confident in yourself, or if your Magento store bristles with different difficulties, like numerous third-party extensions, you may be concerned in our https://skynix.co/services/migration-structuring.
Contact us now🚀
