Vladimir Sedlar

This was a migration of a Swiss publishing house webshop from Magento 1 to Magento 2.

The project was built using Docker and Docker Compose. The same technology was used in remote environments like staging and production.

The project included a connection with a legacy ERP system, product import, and order export, as well as a connection with a CRM for managing customer review imports and exports.

After the initial migration was completed, several changes of the shop data needed the plan for further migrations to be changed and only use partial migration for customer and order data.

In addition to this, many changes were implemented to improve the overall shop performance, which was a big issue for the store in the past, before the migration.

The changes included the set up of the Varnish Cache and specific caching of specific parts of the site, such as the category tree and layered navigation.

The product filtering was also customized to enable multi-select filtering. The search quality was a big priority for the site, so a lot of time went into configuring the various search options to achieve excellent quality of results.

The set up of the Jenkins pipeline was also done from my side.

A Magento 2 based project written in PHP. The project was a migration of a multishop system from Magento 1 to Magento. That required preserving all existing functionality such as communication with the ERP system, various third-party API connections, etc. At the same time, new features needed to be added, such as the Google product feed. The project used Docker both for local development and deployments.

Our company took over this project only two months before the release date. We had to turn a barely working project into something that looked like an actual website in a limited amount of time, which involved rewriting a lot of the customized back-end logic implemented there to serve the high volume of products present.

We also had to finish work on the various ERP exports and imports, which was a particular challenge because the system still used XML for this. On the other side, we had third-party connections with systems like Econda, Ekomi(CRM), and Google Analytics.

The database set up was also rather difficult because of the high number of custom tables supporting features like custom pricing, product types, preorders, and company accounts.