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:
Scope of CMS content supported in Pro ver 3.2.2:
By default, our Pro ver3.2.2 only migrates CMS content from the following Magento 1’s tables:
- cms_page (see a few exceptions noted below)
For the cms_page content, we focus on two key fields of the Design tab only: Layout and Custom Layout. Our migration tool automatically migrates and converts core layouts in accordance with Magento 2’s new layout definitions as follows:
$mapping = array( //M1 -> M2 'one_column' => '1column', 'two_columns_left' => '2columns-left', 'two_columns_right' => '2columns-right', 'three_columns' => '3columns' );
That means your M1 page layouts will be converted and mapped to the new M2 page layouts respectively, including:
- 1 column
- 2 columns with left bar
- 2 columns with right bar
- 3 columns
The following example shows how you might migrate Customer Service page from Magento 1 to Magento 2:
CMS content that needs to be migrated manually
Before you begin proceeding with CMS content migration, it is important to notice about the data set that our migration tool does not cover:
- Widget shortcodes added by core Magento and 3rd parties products: Even though all widget shortcodes are transferred to Magento 2 on as-is basis and visible in Magento 2 backend view after migration, however you have to manually configure the said widget shortcodes to make them ready for use in Magento 2.
- Excluded fields on CMS Page | Design tab: Except for the two fields (Layout and Custom Layout), other fields in CMS Page | Design tab are not migrated to Magento 2 (Due to the huge difference between XML definition in M1 vs. M2).
So, all kinds of data mentioned above needs to be migrated manually at your end.
Deleting migrated data in M2 which no longer exists in M1
There’s a high chance that you might delete some data objects on the source side (Magento 1) after those data objects have already been migrated to Magento 2. How to delete destination records (migrated data objects in Magento 2) based on the absence of the corresponding source records (original data objects in Magento 1)?
With UB Data Migration Pro v3.2.2, it provides a mechanism to remove migrated data objects from Magento 2, where the source record of the said data no longer exists in Magento 1. To do so, you simply use the CLI commands below to delete any specific migrated data objects in Magento 2 depending on which one you need:
- For Websites, Stores, Store views and associated data objects migrated in Step 2:
php -f bin/ubdatamigration rmdeleted --step=2
- For Attributes and associated data objects migrated in Step 3:
php -f bin/ubdatamigration rmdeleted --step=3
(NOTE: This will cover both attribute sets and attribute groups)
- For Categories and associated data objects migrated in Step 4:
php -f bin/ubdatamigration rmdeleted --step=4
- For Products and associated data objects migrated in Step 5:
php -f bin/ubdatamigration rmdeleted --step=5
- For Customers and associated data objects migrated in Step 6:
php -f bin/ubdatamigration rmdeleted --step=6
- Active quotes and associated data objects migrated in Step 7:
php -f bin/ubdatamigration rmdeleted --step=7
(NOTE: Can only delete the active quotes migrated to M2 which no longer exists in Magento 1. This means the original sales active quotes have already been converted to sales orders in Magento 1)
- Other data and associated data objects migrated in Step 8:
php -f bin/ubdatamigration rmdeleted --step=8
The CLI commands give you the ability to start and rerun the command lines anytime which is handy in case of big data migration. If you’re new to our migration tool, you can refer to this blog post to learn more about each migration step above.
The following are examples of the log messages for the CLI command php -f bin/ubdatamigration rmdeleted --step=3:
Since deleting any specific migrated data objects in Magento 2 (which no longer exist in Magento 1) is executed in the CLI mode only, you’ll see the ‘cleaning’ status in the migration tool’s GUI while running as follows:
Updating to UB Data Migration Pro v3.2.2
As usual, updating to the latest Pro v3.2.2 is pretty easy and straightforward following our Readme manual. You can also check out the updated manual with all the latest features and more information on how to use them in your own projects.
Should you need any assistance from our team with the upgrade, please get in touch with here.