Open JamesTheHacker opened 4 years ago
Hi @JamesTheHacker
Thank you for reporting this issue. cataloginventory_stock_item might have two products when cataloginventory_stock has more then one record. Usually it has only stock_id = 1 with stock_name = Default. But some extensions might add more if your webstore works with several stocks. If your store does not need more then one stork you can alter \Migration\Step\Inventory\Model\SourceItem::prepareSelect() to fetch only one record from cataloginventory_stock table and you should not have products duplicated in Magento 2 cataloginventory_stock_item table
I think I understand. I don't need anything from the M1 database except for the products and categories. Is it possible to leave out any data from 3rd party plugins during the transfer? I'm not sure the best way to solve this.
I think I understand. I don't need anything from the M1 database except for the products and categories. Is it possible to leave out any data from 3rd party plugins during the transfer? I'm not sure the best way to solve this.
You can disable entire steps for each phase in your config.xml - inventory step is both in the data phase and the delta phase iirc
I'm migrating the data from 1.9.3.7 to 2.3.3. The migration is successful. But, when I run:
bin/magento index:reindex
I get the following error:If I check the database with the following query:
SELECT * FROM cataloginventory_stock_item WHERE item_id = 2;
... there is indeed 2 products with the same ID. Infact, there are duplicate products for every product in the database.If I run the same query on the 1.9.3.7 database there is only 1 product. So, somewhere during the migration it's duplicated the products. Any idea what is happening here?
My config file for migration is below:
And I run like so:
sudo -H -u "${user}" bash -c "${webroot}/bin/magento migrate:data ${migration_dir}/config.xml"
... which runs and completes successfully.