Magento 2 migration
We are Magento 2 migration expert
Italkeramik – A Magento 2 migration for an existing Magento e-commerce website
Italkeramik needed a Magento upgrade for their existing Magento website
Italkeramik, a Switzerland based E-Commerce Store specializing in designer tiles, approached Romtec – a technology company in Switzerland for upgrading their old website which was built on Magento 1.95 to Magento 2.1.
Since SoftSolutions4U had a wide customer base in Switzerland, and was well aware of quality standards expected, Romtec decided to collaborate with SoftSolutions4U for Magento 2 migration project.
Italkeramik – The technical challenges and solutions
1. New Magento 2 shop had to look exactly like the old shop
Though apparently the task seemed easy, it had many underlying complexities.
First, Magento 2.0 folder structure is very different from Magento 1.9.
Magento 1.9.x contains three folders that are the default themes and are based on the implementation of new themes. Each of these sections contains the following structure:
default/ |-- etc/ |-- layout/ |-- template/
Also note, each theme corresponds to the skin directory, a directory with the same name of the theme, the content of each one within the skin directory is:
default/ |-- css |-- images |-- js |-- libIn Magento 2.x the structure is different
app/design/frontend/ |-- Magento/ |-- luma/ |-- etc/ |-- i18n/ |-- media/ |-- web/ |-- css/ |-- fonts/ |-- images/ |-- js/
To modify the styles of a specific section, we had to add the following:
luma/ |-- Magento_SectionName/ |-- layout/ |-- templates/ |-- web/ |-- css/ |-- fonts/ |-- images/ |-- js/ |-- template/ Therefore, though Magento 2.x theme structure is simpler than Magento 1.9.x, it does not exactly mean that it is easier to extendor modify a theme. Though we could use the old CSS, we had to constantly change and adjust to adapt to Magento 2.x
2. Payment Process had issues which needed to be rectified
The existing payment process – Post Finance has few bugs. These issues needed to be addressed in the Magento 2.x version.
The Checkout process had bugs and we had to test the work in Sandbox.
After a deep dive into the Checkout Process we could resolve all the technical glitches in the checkout process.
3. Updating Content Pages, Products and Images
All the 10 Content pages along with 404 error pages had to be updated with the bench mark site.
Moreover there were Numerous Main Categories and Sub categories with images.
The Products, description, Cost and images were updated through Database running Sql statements.
Our efficient QA team then verified the data and quality of the website.
A successful Magento 2 migration and life long happy customer.
Even more SS4U brought excellent improvements and the project was completed on time.”