I already have an e-shop working on Magento 1 platform. Why should I move to Magento 2?

In summer 2020 the maintenance of Magento 1 would be stopped and there would be a need to move to the second version of this excellent platform for e-commerce within the shortest possible time.


What does it mean?

Cease of development and maintenance of the first platform version, launch of new releases, development of functions and modules. Support of documentation. Cease of security patches supply. Probably sooner or later you will not have any assistance in fixing vulnerabilities on your website.  You may say that not everybody will be able or choose to move to the second version of Magento and a community of the first version supporters may be created. Surely, you are right, but it has not happened till now and nobody knows how much time it will take to create this community.

magento 2

Magento 1 to Magento 2 Migration Process

Migrating Modules

Magento 1 modules are not compatible with Magento 2. Therefore, the first thing that should be done is to make a list of modules that can be bought for example on Magento Markeplace and modules that should be newly created. This is also necessary to export data from the tables of the current modules into the new e-shop.  A table should be made with the information on what will be exported.

Common Questions:

Is it possible to send a claim to the module developer, if their module does not function in my theme?

Yes, it is possible, however the answer will always be as follows: You should install this module in Luma theme and it will start functioning.In other words, module functioning is not guaranteed, if you use a different theme. You should pay additional costs for the module integration. 

How much time does it take to make additional changes and integrate the module?

Generally, it takes not so much time, as it may seem. It entirely depends on the number of modules and their functions. Possible time range is from 2 hours to 22 hours.
If we should implement a totally new theme, Front-end works will be carried out separately after the migration process. The same relates to the development of the new modules.

mobile phone
Look: theme of the upcoming e-shop

Theme files also are not compatible with Magento 2.Therefore there are two variants as follows: to buy the ready theme and customize it or create a theme based on the template or the current e-shop.


Common Questions:

Theme setting/implementation

If the theme is typical and can be bought, you should just install it and fix errors during theme testing.  In general, it means the correction of modules performance. Usually, modules are developed for the Magento default theme, now it is Luma. However, if you have a different theme installed, some modules can function or display improperly.

Is it possible to export styles sheets from the old website to the new one?

Yes, sure, if the current theme was developed with the use of LESS/SASS. However SASS requires more time for integration, as Magento 2 supports only LESS in the basic version.  Availability of necessary files allows saving 30-40% of time.

Data export

Export of settings, data: products, categories, customers, orders. Installation of modules that should be rapidly replaced, they can be bought on the Internet.  Export of data from the old tables into the new ones.

data export
  • How much time does migration take?

  • Data export from Magento 1 to Magento 2 takes from 3 to 5 hours
  • More complicated variant, that is data migration scripting for modules, takes from 16 to 40 hours depending on the modules quantity and data format.
  • Development and implementation of the new theme in Magento 2 takes from 75 to 280 hours, depending on the theme itself and the requirements
  • Testing takes from 8 to 24 hours

Have a project?

Drop us a line and select your budget, we will handle with everything else.

  • Your budget