Magento 2 is quite advanced and has a lot of new and advanced features which encourages the users to migrate their Magento 1 store to Magento 2. Many users and store owners are migrating their Magento 1 store to Magento 2 because Magento will stop supporting Magento 1 after June 2020. This is also one of the major reasons for Magento 1 to Magento 2 migration.
We would like to share the experiences some of the users face after Magento 1 to Magento 2 migration. These are some of the common issues you might come across during or after Magento 1 to Magento 2 migration. Let us discuss them in this blog.
1. Magento 2 Performance Issues
Magento 2 has its own share of quirks and unclear mechanics. Performance issues are common after Magento 1 to Magento 2 migration. Some of the popular issues you experience after migration are…
- Low store performance
- Slow speed in Magento 2 admin areas
- Slow page loading speed
- Unoptimized cache configuration
- Low store reliability
To overcome this issue, setup Redis and Varnish cache, optimize and tweak your JS code, work on your media delivery which will improve the performance of the store.
2. Volume Check Warning
When you successfully migrated your Magento 1 store to Magento 2, you have to capture the data updates that have been added to your Magento store and transfer them to your new Magento 2 website.
During this time, volume check warning may appear while testing Magento 2 website while running the migration process. This might happen because Magento 2 creates entities that do not exist in Magento 1. So it is encouraged to test your site that you catch any issue at the earliest.
3. Magento 2 Security Issues
Magento 2 is great and all but well face the truth, it doesn’t offer the best level of security. You have to configure the security in order to get the best out of your brand new Magento 2 store. Poor store protection means…
- Customer and order details leaks
- Malicious redirects
- CC and payment account details leaks
- Store defacing
In order to overcome this issue, make sure your store is protected from hackers, DDoS and XSS attacks and other threats.
4. Category URLs are Not SEO Friendly
Magento categories are a useful way to arrange and organize the products. Usually, after migration, we face a unique issue with category URLs. As Magento creates URL for categories, these URLs are not SEO friendly.
To overcome this issue, you can develop a custom script to generate SEO friendly URLs for categories in site.
5. Editing Products After Migration
After data migration from Magento 1 to Magento 2, many store owners have tried to edit or add a new product at the backend and received an error. We found afterward that the error is coming because of product attribute media_gallery back-end resource model class is missing in Magento 2.
In order to solve this issue, you need developed script which fixes media_gallery attribute’s back-end resource to make it work.
6. Re-indexing the Magento 2 Store
When you are performing your Magento 2 migration, it is really important to know that some of your indexers may be invalid. To re-index your store, you simply need to go to your command-line interface and run the code that will solve this re-indexing issue in Magneto 2 store.
7. Creating Invoices
There have been cases where the developers have come across situations where they were unable to create invoices in their Magento 2 stores after the Magento 1 to Magento 2 migration. This simply means that there was some issue with the table that creates the invoice for the store.
The easiest and convenient way to fix this is to go back into the table and add the required and appropriate columns and it will start working normally.
8. Unable to Place an Order
After data migration from Magento 1 to Magento 2, many found that they were not able to place an order in sub-stores and create order invoices and shipments from the backend. The issue arises because the system is not able to generate order instrument id to create the orders.
In Magento 2, there is a new concept to generate a sales order sequence ID. You can update the Magento 2 database and create new tables and sub-stores.
9. Delta Log Not Installed
When performing a Magento 2 migration, you may come across an error that occurs during the migration of changes to data. The data migration tool usually installs delta log tables during data migration which means that some delta log was not found in Magento 1 database. Such an error may occur because you are trying to migrate a copy of your live Magento store instead of the live store itself. A disadvantage of the copy is that it doesn’t have additional delta log which is needed to complete the migration.
The best way to fix this is to test the migration process from a copy of your Magento 1 database, then find the issues on the copy and try to fix them. Once you fix the issues, you may start the process again from the Magento 1 live store.
Post-migration challenges are not limited to the ones we have mentioned above. There can be many more challenges too. Many people are migrating their Magento 1 store to Magento 2 because of the many new and advanced features it offers. But the after-effects can be sometimes troublesome like we mentioned in this blog. Although these issues can be fixed with the help of some extensions and tools. If you know of other issues faced by the users after migrating their store to Magento 2, please mention them in the comment section below.