Magento – magento migration tool migrate:data errors

magento2magento2-migration-tool

When I run migrate:data I get some errors, any way to fix this?

[2017-03-06 17:00:38][ERROR]: Foreign key (FK_CATALOG_COMPARE_ITEM_CUSTOMER_ID_CUSTOMER_ENTITY_ENTITY_ID) constraint fails. Orphan records id: 0 from `catalog_compare_item`.`customer_id` has no referenced records in `customer_entity`
[2017-03-06 17:00:38][ERROR]: Foreign key (FK_CATALOG_EAV_ATTRIBUTE_ATTRIBUTE_ID_EAV_ATTRIBUTE_ATTRIBUTE_ID) constraint fails. Orphan records id: 903 from `catalog_eav_attribute`.`attribute_id` has no referenced records in `eav_attribute`
[2017-03-06 17:00:38][ERROR]: Foreign key (FK_CAT_PRD_ENTT_INT_ATTR_ID_EAV_ATTR_ATTR_ID) constraint fails. Orphan records id: 903 from `catalog_product_entity_int`.`attribute_id` has no referenced records in `eav_attribute`
[2017-03-06 17:00:38][ERROR]: Foreign key (FK_EAV_ATTRIBUTE_ENTITY_TYPE_ID_EAV_ENTITY_TYPE_ENTITY_TYPE_ID) constraint fails. Orphan records id: 19,21 from `eav_attribute`.`entity_type_id` has no referenced records in `eav_entity_type`
[2017-03-06 17:00:38][ERROR]: Foreign key (FK_EAV_ATTR_SET_ENTT_TYPE_ID_EAV_ENTT_TYPE_ENTT_TYPE_ID) constraint fails. Orphan records id: 19,21 from `eav_attribute_set`.`entity_type_id` has no referenced records in `eav_entity_type`
[2017-03-06 17:00:38][ERROR]: Foreign key (FK_EAV_ENTITY_ATTRIBUTE_ATTRIBUTE_ID_EAV_ATTRIBUTE_ATTRIBUTE_ID) constraint fails. Orphan records id: 202,213,706,732,903,2712 from `eav_entity_attribute`.`attribute_id` has no referenced records in `eav_attribute`

and this is another one

[2017-03-06 17:00:42][ERROR]: Source documents are not mapped: paybox_question_number,strikeiron_tax_rate

Best Answer

First problem: Foreign key (fk_...) constraint fails. Orphan records id: ...

What does it mean?

You have orphan records in your database. This means that a foreign key is referencing another item which doens't exist anymore. Check some SQL-Tutorials or documentation to read more about it.

How to solve it:

Delete all rows with orphan records or correct all missing data. (https://stackoverflow.com/questions/6445966/elegant-way-to-remove-orphan-rows)

Second problem: Source documents are not mapped

What does it mean?

(I'm not complete sure about this, probably correction needed): You have had different tables that are no more the same, but in a way that the migration tool can't recognize it, as they are customized or extended tables. So in that case you have to check manually whether you want or need to migrate that data aswell or exclude it.

How to solve it:

Check the documentation about mapping, if you want to migrate this data. (http://devdocs.magento.com/guides/v2.0/migration/migration-tool-configure.html)
You can exclude these like shown in this case study example: (http://oyenetwork.com/articles/data-migration-to-magento2-case-study/)

Related Solutions

Magento – Errors while using data migration tool from 1.9.0.1 -> 2.1.2

All these table names and fields which are not "standard" need to be either ignored or mapped in your version of the map.xml.dist configuration files.

The first error line Source documents are not mapped: is about tables which exist in your m1 but m2 knows nothing about, created by extensions.

The next set [ERROR]: Source fields are not mapped. Document: sales_flat_creditmemo (etc) are about attributes (fields) which were created in sales_flat_creditmemo, sales_flat_invoice etc. by extensions, which again m2 knows nothing about.

It's a very long list (and it's only the first, linked to orders, there will be more, regarding customers, products etc.) so you might want to think whether you are using all of these extensions and whether you need it all migrated. The more you can ignore the better for you.

Things that you are not yet ready to migrate (eg:module not existing yet), or will not migrate go in '' tags

<document_rules>
    <ignore>
        <document>easybanner_*</document>
    </ignore>
</document_rules>

<field_rules>
    <ignore>
        <field>sales_flat_order_item.xero_rate</field>
    </ignore>
</field_rules>

Things that will migrate also need to be defined in the xml files too, with transformations if needed. Of course for tables and fields linked to an extension, you need to know if the extension has made it to m2 and if it has changed.

This is going to take you a while and trial and error! I suggest you start by ignoring everything then slowly "move" the things you need to migrate

For things like navigation, banners etc. you might decide to just "rebuild" on m2 rather than fight to migrate.

Ready? It all happens in map.xml.dist (applies across the board) and the more "specialised" map-eav.xml map-customer.xml etc. Each has a document_rules and a field_rules section, and yes, every single one of the names in these long error lists will need to be in there either defined or ignored.

<document_rules>
    <ignore>
        <document>easybanner_*</document>
    </ignore>
</document_rules>

<field_rules>
    <ignore>
        <field>sales_flat_order_item.xero_rate</field>
    </ignore>
</field_rules>

Magento – magento 1 to magento 2 data migration issue

First take a backup of your Magento1 database.

Please remove orphans record from your Magento1 database. after you solve Foreign key error.

Remove 121,164 attribut_id row from catalog_eav_attribute.

Remove 121 attribut_id row from catalog_product_entity_int.

Remove 121,163,164 attribut_id row from eav_entity_attribute.

Source fields are not mapped.

Please add code in map.xml.dist source part.

<ignore><field>customer_eav_attribute.is_used_for_customer_segment</field></ignore>

Source documents are not mapped. Please add code in map.xml.dist source part.

<ignore><document>paybox_question_number</document></ignore>
<ignore><document>social_facebook_actions</document></ignore>
<ignore><document>strikeiron_tax_rate</document></ignore>

Follow this step for all of your source/destination issue.

Once you drop your database and execute this process again after complete this step.

I hope this will help you.

Best Answer

Related Solutions

Magento – Errors while using data migration tool from 1.9.0.1 -> 2.1.2

Magento – magento 1 to magento 2 data migration issue

Related Topic