12/14/2020 - #ecommerce #magento
by: Ceyhun Kaplan

Although the terminology can be confusing, the move to Magento 2 is more a change in technology than a migration to a new version. This transition, which has become essential at a time when Adobe is abandoning maintenance on M1, represents a real technical and organizational challenge for agencies and e-merchants who want to upgrade. Here’s a brief overview of the main pitfalls to avoid.



Extend the migration deadline

Perhaps your site was created years ago, has always been trouble-free, and you’re therefore reluctant to change platforms. This is a legitimate worry: upgrading to version 2.x represents a significant effort. No Magento expert will tell you the transition is easy.

Unfortunately, the answer to this question is always the same: you no longer have a choice. Since June 2020 Magento has ceased the application maintenance of its version 1.x. Security breaches, incompatibility with new technologies, performance issues, scalability ... Maintaining Magento 1 will become more and more risky and expensive, despite community initiatives such as OpenMage LTS.

In addition, any investments you continue to make will be lost when the death knell for Magento 1.x. tolls. All code overloads, installed modules, style integrations, etc. will have to be redone during the migration to M2. You might as well get started as soon as possible!

The inevitable question is: “When should I migrate to Magento 2?”

The simple answer would be “Migrate now!”. The informed answer would be “Start now!”. We’ll explain why in the rest of this article.


Aiming for an isoperimeter MVP: a utopia

So, you’ve taken the plunge and decided to migrate to Magento 2. Yay! A quick glance at Magento 2’s new features will make your mouth water: more modern technology stack, improved performance, numerous marketing & SEO features, new back office interface… And these are just the improvements in the native version of Magento!

Since creating your M1 site, you’ll have fine-tuned and personalized it with community modules, specific developments, optimization of native behaviors and external services.

The goal is to keep this functionality with your migration to M2, but not for the MVP version! Many migration projects to Magento 2 fall behind schedule due to the desire to keep the same functional scope, which took years to be built on Magento 1.


Getting started without specifications: the risk of regression

Aiming for an iso-perimeter version on Magento 2 is a way to reduce the burden of designing and writing specifications. The process is to start from the functional perimeter on Magento 1 and to build that on Magento 2. This methodology nevertheless has a significant constraint: building a backlog from the code of Magento 1 is extremely complex because it will not be exhaustive. Depending on code overloads, community modules installed but no longer used, configurations in the back office and legacy code, it’s sometimes difficult to determine in advance the origin of a behavior. For example, two different modules A and B can override the same native add to cart functionality. Without going into the details of the code of each module, it’s impossible to disentangle what’s native, what relates to module A and what relates to module B. A specification makes it possible to express an expected result, while reading the code will express a potential result.


“Data migration is easy”

Data migration is facilitated by Magento’s Data Migration Tools module. Although it simplifies the match of the table structure between M1 and M2, this module doesn’t do everything! Many cases won’t be taken into account with this tool:

  • Specific development on catalog management, customers and orders

  • Community modules that add tables to the database

  • Types of editorial content (News, Blog, Lookbook, etc.)

This list isn’t exhaustive and depends mainly on the changes experienced by your native Magento. It nevertheless shows the precautions to be taken before centralizing all data migration via Data Migration Tools.


APIs, synchronizations and external services: the eternally forgotten

Although Magento 2 comes with a very complete functional arsenal, complementary services and tools will add to your sales ecosystem. Between tracking tools, tagging plans, open and consumed APIs, catalog imports from a PIM, catalog feeds for marketplaces, exports of orders for ERP, marketing automation services ... for years you’ve built a complex, interdependent and difficult-to-map system.

Going on a migration project without considering all the connections, flows and interfaces can cause unpleasant surprises! If the system was created by different developers and not properly recorded, setbacks will seem inevitable!


Rest assured, all these traps are easy to get around when you are surrounded by good people . Contact our team by emailing hello@bird.eu to discuss your migration project. Just like the bird in our name, we’ll help you migrate with coordination and ease (and in “V” formation ) to the warm lands of Magento 2!

Write your comment

for take-off?

Blackbird is a web agency specialized in the development of eCommerce websites. We are Magento Experts and we offer our services and advice for e-marketing, strategy, branding, deployment and methodology.

+339 50 66 21 38

Legal terms
Agency 30, Avenue du Rhin
67100 Strasbourg