How fast can I update the Magento 2 system to its latest version? How long will it take? Is it a complicated process? These are the questions addressed to Sii experts by many companies. I invite you to read this case study, in which I will answer them all based on the example of cooperation with Urbanista.
Urbanista brand, owned by Stax Limited, was created in 2010 in Stockholm. The company’s offer includes active-noise-canceling audio products and accessories, designed ‘out of a love of music’ with life in motion in mind.
Sii e-commerce team proposed Urbanista to update the system to 2.4.2 Magento version. Such an update and migration introduce numerous improvements – both in terms of business (e.g. security improvement, better data protection) and technical aspects (e.g. module infrastructure improvements). Morevoer, Magento 2.4.2 increases the stability of the e-commerce website, and improves system performance. The new version of the platform includes also brand new modules, allowing store owners to assist customers with the purchases.
What was the task of Sii developers?
- 75 virtual stores for 1 Magento instance
- maintaining mulit-language support with shipping to dozens of countries
- customizing URLredirects
- update and migration to Magento 2.4.2
- Quick update and performance improvement: 2 weeks (including tests and final release)
The goal of Sii e-commerce team was to update and migrate the system to the latest Magento 2.4.2 version at the same time focusing on functionality and UX in the purchasing process.
Urbanista’s e-commerce platform based on Adobe/Magento includes 75 stores. Business continuity and adaptation to changes not only in the Magento 2.4.2 architecture had to be taken into consideration while preparing the update process.
The challenge was to improve the working and reindexing of URLs with which the current default solution did not cope well. Sii experts met it by using the Sii Url_rewrite module, which removes duplicates and makes products work correctly when created in the back office. When it comes to the frontend, it was necessary to adapt to UX changes in the new checkout templates which were changed – and in the case of custom solutions, this is always a rather complex process.
Szymon Nagórski, Frontend Developer at Sii: ‘A real challenge was to adapt asynchronous queries and block with CORS (Cross-Origin Resource Sharing) – a solution based on external queries (Sii solution)’.
Development work included the creation of a 1:1 local copy of the system with access to external integration (ERP), where migration and most of the work took place.
Daniel Lenkiewicz, Software Engineer at Sii: ‘We went through the prepared step-by-step REST query path, checking individual endpoints for integration, e.g. Navision’.
The update to the 2.4.2 version itself was also a complex issue. During our work, internal Magento errors occurred, e.g. errors related to the MC-40700 database”. The next step included work in the test environment: UAT tests, backup and functional tests. Here, we also made minor improvements before the final release.
As always, an important aspect (besides the update itself and migration) is performance – for the system to work efficiently and be tailored to the needs of the end-users and back-office users. About how performance can be audited we have already talked during the E-commerce Trends conference Our keynote was based on the example of Black Friday.
During the migration we analyzed the modules in the latest Magento 2.4.2 version and disabled 147 of them (including Magento Inventory) – due to their lack of usefulness in the project and greately eased the load on the system.
Below you can see the before and after time comparsions after updating to Magento 2.4.2:
- during the tests of adding new products, users and attributes performed on the existing product database (based on Magento Performance Toolkit):
As the chart presents, after updating to Magento 2.4.2, the reindexing time got greatly shortened.
- The comparsion of reindexing operation time:
The increase of performance was almost doubled when fully reindexed.
After conducting tests in the test environment, the proper implementation went into production with a prepared backup (to be used if there was a need to recreate the system).
When updating Magento to 2.4.2 version, it was also necessary to update Elasticsearch to the latest version, update PHP 7.3.x and to analyze the external modules used (e.g. CMS).
What helped Sii developers to complete the task?
- experience with the Magento platform
- knowledge of optimal cloud hosting solutions
- Sii modules for dedicated solutions improving the performance of Magento
Urbanista is satisfied with the results of the activities of Sii experts and the implementation they performed. The client noticed that after the introduction of changes there was a significant difference in the operation of the system:
Urbanista: ‘Thanks to migration, the back office started to work more efficiently, which is noticeable while daily operations are performed’.
Another effect of migrating to Magento 2.4.2. was the reindexation of products and general stabilization of the system along with security updates (280 core fix, 35 security pateches).
The whole project of migration to Magento 2.4.2 carried out by Sii developers (including preparation of the plan, development and tests) lasted 2 weeks, i.e. 1 sprint. The implementation was completed at the end of March 2021.
Do you have any additional questions about the implementation? Perhaps you are interested in a specific aspect of the changes made? Share your opinion in the comments section – I will gladly answer all your questions.