"[intro_start]Most Magento users will soon need to consider migrating to Magento 2 – the new version of the e-commerce platform. But how do you approach such a migration?[intro_end] Since the launch of Magento 2 at the end of 2015, there has been considerable criticism of the new platform. In particular, the instability of the platform and the fact that certain features and extensions were missing caused concern among businesses. This still leads them to switch to alternatives like Shopware. And although much has improved since then, and businesses are gradually making the switch, many still postpone the migration. However, this cannot go on indefinitely: by the end of 2018, Magento is expected to stop support for the first version. Theoretically, it is possible to continue using Magento 1 after this point. But no support also means no security updates. The exact moment when support stops is not yet completely fixed, but there are all reasons to prepare in advance. The expectation is that many developers of extensions, for example, will follow Magento's example. Every change or extension for the platform is therefore at one's own risk and likely wasted money if a decision is made later to switch after all.
Inventory
According to experts, companies planning a migration would do well to first carefully examine the current installation. Contrary to what is sometimes thought, Magento 2 is not an upgrade of the first version. Although the two versions have plenty of similarities, Magento has chosen to rebuild the platform from the ground up. The code, structures, and data architecture are different and also more complex. ‘The first step in the transition process is to assess the current installation. Look at your own operation and highlight the components that are unique (custom extensions, integrations, and workflows) and where the Magento platform asks for improvement,’ says consultant Paul Rogers, for example. He advises then to create an inventory of all the extensions used. The first question is whether these extensions are still needed in a new environment and, if so, whether a Magento 2 version has been made available. Not all extensions are available in that version, which means custom work may be needed (with the associated labor and costs).
Data Migration
For a project team, data migration will be the most significant hurdle. For that, Magento has developed a migration tool that converts the essential data into the Magento 2 model. The tool comes with three key functions: first of all, the settings are migrated from one online store to another. Even more complex is the transfer of the actual store data – step two. Finally, the migration tool has a delta function that bridges the time between the last import and the actual go-live. All data added shortly before launch – think of customer data and recent orders – are transferred during this phase. An important caveat with this tool is that the data generated by third-party extensions is not automatically migrated. A solution for this can be found in Magento’s documentation. Experts recommend seizing the migration to Magento 2 to also revise the catalog and all related data: data, attributes, and media that are no longer used can for example be removed. It is likely that a first, second, and third import will produce numerous error messages: the tables and columns do not match, and the data need to be reformatted. That this is a somewhat complex process is evident. It is about correcting error after error and starting the import again. The tool is viewed as useful and relatively fast – for example, three hundred thousand products can be moved within an hour."
