Dear team
We’ve just purchased UB Data Migration Pro (3.2.3) and trying to migrate our Magento 1.9.3.8 to Magento 2.3.4
I wonder if migration tool allows to “Keep original IDs” for categories?
So far, category IDs in M2 does not match the IDs in M1. But products assigned correctly to categories.
Could you give a technical light how it worked out? The tool somehow create a mapping M1 categoryID => M2categoryID?
5 answers
Hi there,
As explained to you in our first reply via the ticket you submitted under your free account, our module does not support the ‘Keep Original IDs’ for Category.
The category’s ID is automatically defined by MySQL depending on the value of ‘AUTO_INCREMENT’ setting in the table ‘catalog_category_entity’, like this screenshot: https://prnt.sc/pmkxyd. It helps avoid IDs conflict (duplicated IDs) when a new data record is added to that table.
PS. Since our team is off at the weekend, we’re sorry for a certain delay in response if you reach out to us during this time.
Regards,
Ubertheme team
‘catalog_product_entity’ also has entity_id as ‘AUTO_INCREMENT’, but somehow you support Keep Original IDs for this entity. Looks like a strange restriction… Is it because ‘catalog_product_entity’ has sku field so you can map the products by sku, which is not available in ‘catalog_category_entity’ ?
Hi there,
Is it because ‘catalog_product_entity’ has sku field so you can map the products by sku, which is not available in ‘catalog_category_entity’ ?
No, our migration tool has a log table to map the entity IDs for migrated products, you can see this table in your M2 database: ub_migrate_map_step_5
‘catalog_product_entity’ also has entity_id as ‘AUTO_INCREMENT’, but somehow you support Keep Original IDs for this entity. Looks like a strange restriction
To migrate Products with the ‘KEEP ORIGINAL IDs’, it’s mandatory that your M2 have to be a fresh instance. In this case the ‘catalog_product_entity’ is an empty table before being migrated with our tool. As a result, we can keep the Product’s ID in M1 when migrating to M2 database.
Regards,
Mall.
In this case the ‘catalog_product_entity’ is an empty table before being migrated
With fresh instance, ‘catalog_category_entity’ table is also supposed to be empty, no?
I just don’t see any difference between products and categories migration in terms of database.
Both entities are EAV data structures with AUTO_INCREMENT entity_id
Hi there,
With fresh instance, ‘catalog_category_entity’ table is also supposed to be empty, no?
No. If you install a new fresh M2 instance, then check the data in the ‘catalog_category_entity’ table in M2 database, you should see that there are two default data records in that table: https://prnt.sc/td3cyj
Regards,
Mall.
