Changelog for (Magento 2) UB Data Migration Pro extension (version 3.2.5)
Latest update: Oct 20, 2020
- Compatibility testing with Magento CE 2.4.1.
- Allow to migrate Category’s display settings and related CMS Blocks.
- Improve coding and fine-tuning to handle more special cases.
- Compatibility testing with Magento CE 2.4.0
- Support for converting special price, special_price from/to datetime and variation prices setting in a Configurable product.
- Fine-tuning to handle additional special cases and delta migration phase optimization.
- Compatibility testing with Magento 2.3.4, 2.3.5
- Fixed the issue on special bitnami database settings
- Fixed the issue on the label/alt value of product galleries in the multiple stores context
- Compatibility testing with Magento 2.3.3
- Allowed to convert core’s email template paths in the migrated email template’s content
- Allowed to migrate CMS Blocks, CMS Pages data, as noted here.
- Added CLI commands to check and remove migrated data objects in M2 which no longer exist in Magento 1 since the last migration.
- Fine-tuning source code in all steps and adding extra tweak code to handle special cases of bad data.
- Fine-tuning to handle additional special cases of data settings
- Improved server side processing to enhance the access token.
For anyone familiar with Magento 1, it’s quite common that a configurable product is one of the most popular product types and powerful when you sell complex products with multiple attributes.
However, it can be quite daunting migrating configurable products from Magento 1 to Magento 2 since Magento 1 provides fairly extensive pricing options, such as Special Price, Tier Price, and Cost. That’s why we received many questions like “does the migration tool migrate configurable products attached to the correct simple products and attribute sets?”.
In this article, we will try to cover the main differences of Configurable Products in Magento 1 versus Magento 2 and how our UB Data Migration Pro module helps to migrate all Configurable Products from Magento 1 to Magento 2 automatically. Before we dig deeper, let’s talk briefly about what simple products versus configurable products are. Continue reading
We’re pleased to announce the 3.2.2 release of our UB Data Migration Pro module. Here are two important new features we added to the version 3.2.2:
- It’s now possible to migrate CMS content from Magento 1 to Magento 2
- Keeping the migrated data in Magento 2 in sync with the source data that no longer exists in Magento 1
Ability to migrate CMS content to Magento 2
Since version 3.2.2, UB Data Migration Pro module enables you to migrate all CMS blocks and CMS pages from Magento 1 to Magento 2. In order to migrate these CMS contents, you can optionally tick the CMS Pages, CMS Blocks checkboxes in Step 8 -- Migrating Other Data like this screenshot: Continue reading
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
For the past few months, we have gone extra miles in developing and improving our Magento 2 extensions. Some of these extensions also compliment our responsive Magento 2 themes. The goal is to bring improved native features in our extensions and themes and make it easier for you to set up new Magento 2 stores.
Our eight Magento 2 extensions that are becoming must-have items for ecommerce stores trying to stay ahead are: Continue reading
Sept 9, 2020 Update: Adding an additional common URL rewrite problem which you may encounter after data migration and how to fix it.
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.