It’s time to consider Magento 2 as the optimal solution for the development of an e-commerce project that our Vue JS development company can offer.
Many clients we review new projects with today ask us whether to start a new eCommerce project on Magento 2 or be careful and move to Magento 1: our answer is yes, you can start by developing a new eCommerce project on Magento 2 (with some exceptions).
Other clients who have already more than started their e-commerce project ask us if it is necessary to migrate their e-commerce solution to Magento 2 and in what time frame: our answer in this case is none, although in terms of the given time, November 2018 is Magento’s inexorable end to product support and security for Magento 1.
It is good to clarify and express your opinion on in what situation we recommend continuing developing e-commerce on Magento 2, and in what situation to stay on the Magento 1 solution.
The necessary premise is that Magento 2 certainly won’t make you sell more, but it can offer you a more medium-term perspective than Magento 1 to grow your eCommerce project.
We must immediately solve an important problem: refusal to update technology creates risks, inefficiencies and imposes restrictions, therefore, there are situations when migration or development of a project on Magento 2 becomes the only way out.
buy female viagra online noprescriptionrxbuyonline.com/female_viagra.html no prescription
Magento’s e-commerce project from scratch
In this case, unless the project requires a number of extremely specific settings that may not be available on the Magento 2 platform, we strongly recommend that you continue developing your e-commerce platform on Magento 2. The benefits are many. in particular, there is an added value on:
- Representation
- Solution scalability
User experience in the admin panel
If instead you want to continue working with Magento 1, I can give you a piece of advice: try to develop all customizations already focusing on the Magento 2 code structure, so that you can then minimize the gap needed to adapt the customization to Magento 2 when you decide to port the solution.
Existing Magento eCommerce project
This is the most delicate situation, because we may have come across Magento 1 e-commerce solutions that have been active for a long time, which work and generate a significant number of orders and have many settings.
In this case, we believe that the key to the decision is to evaluate whether the development of the project requires immediate strong tuning or not, in the first case it will be possible to evaluate whether these settings are so important, to consider migrating everything at the same time to Magento 2 or otherwise, postpone whether surgery for the next 12 months.
Transferring data from Magento 1 to Magento 2
If you decide to migrate your e-commerce solution from Magento to Magento 2, the first question to answer is how to migrate data such as customers, orders, rules, settings, fortunately there is nothing to invent here, it is possible to use the tool provided in Magento, called Magento Data Migration Tool.
Once this is done, it will be necessary to migrate all the settings from Magento 1 to Magento 2, and here you can help with an interesting guide that you can find at this link.
Conclusions
We have tested the migration tool from Magento 1.9.2.3 to Magento 2.1.3, and we must say that it works really well. It does not allow the transfer of customizations, and on the latter, as already mentioned, it is necessary to develop add-ons.
If you are interested in developing a Magento 2 project or porting Magento 1 eCommerce to Magento 2, please contact our ecommerce web design company to learn more about the project.
