Migration from Magento 1 to Magento 2 is less of an option and more of a necessity for the store owners. There were a few flaws in the Magento 1.0 which is now improved in the new Magento 2.0 version. Magento 2 migration can take a great deal of time and you can also face some issues since this procedure is extremely unpredictable and incorporate several customizations.

Here, in this blog, I am listing down the issues that I have faced during the Magento 2 migration.

1. Adding Grouped type product to cart

We faced this issue after we successfully completed the data migration to Magento 2.  During the testing phase, we tried adding Grouped type product to the cart and we found that it was only getting added to the shopping cart but the product details were absent.

The solution which we found for this issue was that we developed a custom module that basically used to override the shopping cart action and displayed the added product in the cart.

2. The checkout button in Minicart was not working after data migration

The checkout in Magento 2 is now driven with JavaScript and KnockoutJS. As a result,  you see significant improvement in Magento 2 checkout. The Magento 2 checkout has improved general flow now and is visually more appealing for the visitors too.

The issue which I faced here was that after data migration, the checkout button in Minicart was not working. I was not able to click on the checkout button and as a result, I was not able to proceed to checkout. Although, I was able to click the checkout button on the shopping cart page.

The solution to fix this issue was by creating a custom module that will override the cart action to make the checkout button clickable.

3. Unable to edit products from Admin after data migration

Admin can add/delete products updated by the sellers. When we migrated to Magento 2, we found that we were unable to edit products from Admin.

The solution for this was that we developed a custom module to override the configurable price.

4. Category URLs were not SEO friendly

The URLs you assign to products and categories play a major role in search engine optimization. Magento’s rewrite functionality creates URLs for categories while saving them. This has caused me countless issues over the last few years, primarily from an SEO perspective.

In order to resolve this issue, we:

• Rewrite entry against the previous URL
• Developed a custom script to generate SEO friendly URLs.

You may also be interested in: Top Rated Magento 2 Extensions for all Ecommerce Businesses

5. Admin unable to create the invoice for Orders

You need to create the invoice for the order as a record of the receipt of the payment. Invoice is somewhat a completed order page created when a temporary sales order is confirmed or when canceled. Admin generally generates an invoice with a packing slip and shipping labels. Multiple invoices can be made for a solitary request, and each can incorporate the same number of or as few of the obtained items that you indicate. The problem which I faced was that Admin was unable to create an invoice for orders.

After doing lots of research, I found that the tables responsible for Invoice creation is creating this issue. After adding the appropriate column to the table, I was able to create an invoice for orders from the admin panel.

6. Unable to edit/update categories

The category can be edited/updated or moved to another position from the catalog. In the case of live inventory, you ought to consider how the change may affect any current links to items in the category.

After migrating to Magento 2, we found that editing any category from Admin was showing error. On exploring, I found that the values of custom category attributes are missing that is why it was throwing an exception.

This issue was fixed by creating a custom module to override the ReadHandler.php Model class

7. Unable to edit/update catalog products

We were receiving the following error when we tried to add new products in the catalog after migrating to Magento 2.

‘Class Magento\Catalog\Model\Product\Attribute\Backend\Media does not exist’

The above error was coming because the Product Attribute media_gallary back-end resource model class is missing in Magento 2.

To make it work we developed a script that fixes the media_gallary attribute’s back-end resource type.

8. Unable to place an order from sub stores

Since the time we migrated to Magento 2, the system was not able to generate order increment id to create the orders due to which we were unable to place an order from sub-stores and create order invoices and shipments from the backend.

To solve this issue we wrote a script to update the Magento 2 database and create new sequence tables for sub-stores, which is a new concept to generate sales order sequence Idin Magento 2.

Author Bio:

Ronak is a serial entrepreneur who has worked with companies of all sizes. He is having 8+ Years of expertise and has been closely working with eCommerce ventures since 2009. Ronak Meghani, the Co-Founder of Magneto IT Solutions, a Magento Development service provider in the USA, UK, UAE, and India. He's enthusiastic about fitness, start-ups, entrepreneurship, and all things related to marketing.