Upgrade Magento: Migrating M1 to M2
Upgrade Magento, migrating from Magento M1 to M2 (eg from 1.9.x to 2.x), to take advantage of speed boosts, latest developments – and future security support. But upgrade of an established M1 store to a new M2 installation, particularly where code has been extended and customised, can offer some challenges to the Magento store owner.
Magento M2 is a welcome upgrade to the enterprise strength e-commerce system. It has been conceived from the ground up to improve site performance, provide better integration with business goals, and support differentiated omnichannel e-commerce experiences. M2 is now the target for all active Magento development.
There was a fear that security patch support for M1 would cease last year (2018). This would have meant that M1 sites would not receive any further security updates and so would be liable to “hacking”.
But Magento has now clarified that M1 patch support will continue for the foreseeable future, with a statement by Jason Woosley, Senior Vice-President of Product & Technology at Magento:
“Magento stands behind our customers and will never leave a customer behind – you can rest assured that we have your back at every turn. Magento 1 has been and will continue to be supported for the foreseeable future. We have no intention of denying access to our world-class software and know your business relies on Magento to drive growth and differentiation for your brand.”
This has removed a little of the panic being felt by Magento M1 website owners who have invested considerable sums in customising code and extensions, as support is going to continue. Now it looks as though end of life will be 2020.
Steps to Upgrading Magento M1 to M2
- Survey M1 Extensions
- Survey M1 Custom Code
- Rebuild/Redesign Interfaces
- Manage M1 Data
Many Magento M1 extensions have been rebuilt as M2 extensions so can be upgraded. Also the path for migrating data from M1 to M2 is now well established. The user interface needs to be completely rebuilt – it is possible to work to replicate the same interface in M2. But most M1 store owners take the opportunity to update their interfaces to match the expectations of mobile-friendly customers.
It is the “custom code” component that requires a careful and “unique” approach on a site by site basis. Code and extensions need to be examined and audited to determine how best to replicate in M2. The logic in the M1 custom code can provide a “leg-up” in developing code for M2. But it may be that new techniques and possibilities are more appropriate and the starting point should be a new functional spec.