Migration From Magento 1 to Magento 2

Migration From Magento 1 to Magento 2


Most of the businesses which still have their e-commerce on the Magento 1 platform think about migration to Magento 2. Officially Magento 1 is supported by Adobe till the end of June 2020.

The question is: How to start the migration process?

From a merchant point of view it’s simple:

“We want to have the same functionalities as we have now”

Maybe it’s also a good time to add new functionalities or change the project’s design?

From the technical side, it’s a more complex process than we think. In my opinion, there are four main stages of preparation:


1) Functionality analysis

In my opinion, in the beginning, we should focus on functionalities that we have on the frontend and on the admin panel.

By the frontend, I mean all functionalities which are available for customers.

By the admin panel, I mean all functionalities which are used by merchants, service desk team.

We should check which functionalities are necessary and used on a daily basis. This analysis should be done by the shop owner and technical staff/agency separately.

After that, conclusions from both analyzes should be combined and discussed. It will give us 80-90% of functionalities which are must-have in the shop.

Missing 10-20% of must-have functionalities will be defined in the first iterations of the project.

After the main analysis, we will see that 60-70% of all shop’s functionalities are must-have functionalities. The rest of them are unused functionalities or functionalities which didn’t bring any value in your shop.


2) Extensions/modules

Then we can connect each extension with particular functionality. We will have a list of modules that should be migrated to Magento 2.

One part of this list contains modules that are available on Magento 1 and also they are available on Magento 2. 

The second part of the list contains custom created modules and modules which haven’t been rewritten to Magento 2. In this case, we have two options:

  1. Leave this functionality and not migrate it to Magento 2
  2. Rewrite custom module to Magento 2



3) Data migration

Magento 1 database structure is similar to Magento 2 database structure. It’s a good idea to migrate Products, Categories, Customers, CMS Pages. This would be easy, but in most cases, shops are customized which comes down to expand M2 existing tables or create new and map data from M1 to M2.

To do this process we can use the official Data Migration Tool from Magento (https://devdocs.magento.com/guides/v2.3/migration/migration-tool.html) or custom extension like Improved Import & Export Tool for Magento (https://firebearstudio.com/the-improved-import.html).


4) Design, theme

The frontend parts in Magento 1 and Magento 2 are different. It’s necessary to rewrite or recreate themes.

If you want to improve the frontend part you should consider using Progressive Web Application (PWA) solution for Magento 2.

Adobe works on the official solution – PWA Studio (https://magento.github.io/pwa-studio/).

We started using ScandiPWA Theme for Magento (https://scandipwa.com/)

Using the PWA solution we will improve customer experience in the shop and it will increase sales.

From my perspective migration from Magento 1 to Magento 2 looks like creating a new project from scratch. We can’t copy files from Magento 1 to Magento 2 – it will not work.

The biggest advantage is a situation that we have all the requirements which work well on Magento 1 platform and we can migrate it to Magento 2. We do not have to reinvent a wheel from the beginning.

If you have any questions about the migration process or you need help in analyzing your current webshop functionalities please don’t hesitate and write to us.