We have just released a maintenance release for UB Data Migration Pro which focused on further improving the delta migration performance. The goal is automatically finding any data changes that occur on your current production instance between the last migration and the delta migration, and migrate only the differences. In most cases, the new delta migration from version 3.2.0 will complete much faster than the prior versions.
Apart from that, several incremental enhancements are also included in this release. Read on to learn more about the update. Continue reading
Delta migration is worth noting when you plan to migrate data from Magento 1 to Magento 2.
This article informs you which delta migration options UB Data Migration Pro provides and how you should use them. All of the important steps that have to be carried out for the delta migration are covered in this article. Additionally, frequently asked questions are also described in detail to give you a fundamental understanding of the delta migration feature. Continue reading
In 2018, there has been an increase in the number of e-commerce stores that carry out Magento migration. We believe this number would continue to rise in 2019 due to upcoming Magento 1’s end of support. It’s no longer the question of ‘Should you migrate your Magento 1.x to Magento?’. It’s more about how you should do it and which migration tool you should use.
This Magento data migration FAQs Part III takes you through the frequently asked questions specific to our UB Data Migration Pro extension which were not covered in our Magento data migration FAQ Part 1 and Part 2.
This FAQs is aimed at helping you identify which is causing the errors that you might see at some point and the appropriate resolution.
|Q1. Today we are taking a look on rules migration, we cannot edit any migrated rule. It shows this error: Unable to unserialize value. It works properly with new rules, not the migrated one.
|This circumstance occurred with a user who attempted to use our old UB Data Migration Pro v3.1.4 with the latest Magento 2.3.0 (Disclaimer: Upgrading to UB Data Migration Pro v3.1.7 is needed for compatibility with Magento 2.3.0).
After completing the first migration, the migrated sales rules were stored in serialized strings in accordance with Magento 2.2.x. Then the user upgraded his migrated instance to the latest Magento 2.3.0. However, due to the incomplete upgrade, those migrated sales rules were not converted to the new JSON format required by Magento 2.3.0. This was the reason of getting the error message above ‘Unable to unseriazlie value’.
Resolving the problem:
Upgrade to the latest UB Data Migration Pro v3.1.7 for compatibility with Magento 2.3.0, then run the delta migration with the CLI mode —update in Step 8 -- Migration Settings > Others.
Data migration is a critical element when Magento 2 is adopted and the risk involved is high. However, choosing the right data migration tool will increase the likelihood of achieving a smooth transition of data to Magento 2.
We have conducted an interactive interview session with Fayyaz Khattak, Magento Community Manager at Cloudways, to know his recipe for a successful Magento 2 data migration project. We explored the common hurdles that could potentially derail a data migration project and how UB Data Migration Pro helped him ease up the migration process.
Fayyaz, thanks for taking out some time for this interview and sharing your insights and what you’ve learned along the way. Continue reading
As you are probably aware of, Magento has officially announced the end of support date for Magento 1. The software support for Magento Open Source 1 (formally known as Community Edition) and Magento Commerce (formally known as Enterprise Edition) will be extended through June 2020.
The dates have been rumored for quite some time. And now we’re all clear about the specifics of Magento 1’s end of life and there is no need to worry about Magento 1 End-of-life in 2018. Continue reading
You might be familiar with the option to add URL Rewrites in both Magento 1 and Magento 2, which is also referred to Search Engine Friendly URLs. Sometimes URL Rewrite issues arise when migrating data from Magento 1 to Magento 2. This guide will help you in troubleshooting when you encounter such issues.
What is URL Rewrite?
URL rewrites make it possible to make your existing Magento store URLs more ‘search engine friendly” and also easier for visitors to read.
Within Magento, the system URL looks similar:
- For a Product URL: /catalog/product/view/id/10
- For a Category URL: /catalog/category/view/id/11
The ‘catalog’ segment refers to the Catalog module of the Magento core, followed by other segments indicate that a product with ID 10 or a category ID 11 should be displayed on the page. No matter how often the URL changes, these ID remains the same.
Customer data is one of the most important elements -- especially when migrating from Magento 1 to Magento 2. What if the transfer doesn’t go smoothly? In eCommerce one of the worst scenarios is that the migrated customers may be unable to log in to the new Magento 2 instance.
Getting started with the customer data migration can be intimidating, but with a right migration tool, the process isn’t as hard as it seems. Fortunately, our UB Data Migration tool makes this very simple.
If you’re considering our migration tool, we have done the hard work for you and figured out how to automatically migrate customer logins and passwords to Magento 2 with ease. In this article, I’ll briefly go through the important change in the way Magento 2 store passwords, how to migrate only customer logins and passwords using UB Data Migration tool, and possible post-migration login issues as well. Continue reading
In case you missed, check out:
- Magento 2 Data Migration FAQs -- Part I
- Magento 2 Data Migration FAQs -- Part III
A couple of months ago, we shared our first Magento 2 Data Migration FAQs. It highlights 10 key questions about Magento data migration, information about migration tool and best practices for using it to migrate your data.
Today, I’m sharing 15 of the specific problems our users faced in their actual Magento migration projects, and how to deal with them. These typical issues might occur because some behaviour and logic of Magento 1 has been implemented differently in Magento 2.
I hope they’re as valuable for you as they’ve been for us. And you will have a solid preparation and make a smooth transition to Magento 2.
|Q. Couldn’t connect to Magento 1 database
|If your Magento 1’s database is on a separate MySQL server from your Magento 2 instance, it is required to set up remote connection from your Magento 2’s server to your Magento 1’s MySQL. Learn how to set up remote connection from your Magento web note here.
In the meantime, you need to make sure your database credentials (host, port, username, password) are correct.
Today, I am honored to have Roel van Leuken, the Founder and CTO of Kwaaijongens B.V. Roel is a helpful and down-to-earth person. He has been working with Magento when it was brand new in the early days.
In the interview, Roel has shared his views in details about how his team at Kwaaijongens.nl took advantage of Data Migration Pro extension to overcome the biggest challenge -- Magento data migration. So let’s read along and find out more about his journey with Magento.
The latest version of Magento 2, Magento 2.2 has been released in Sept that brings significant new functionality to the market. It’s not a surprise that B2B segment of ecommerce is a huge focus in Magento 2.2, and this focus on B2B features makes sense when you consider the rapid growth of the B2B market, which should generate $6,7 trillion across the global by 2020, as reported in a research by Frost & Sullivan.
For now Magento 2 is in the phase of active improvement. In this context the most important question is how to migrate from Magento 1 and the latest Magento 2.2.
This blog will serve as a quick guide for those who need to know about what’s new in Magento 2.2 and all changes that will affect your Magento data migration projects. Continue reading