cancel
Showing results for 
Search instead for 
Did you mean: 

M1 to M2 Migration Isssue

SOLVED

M1 to M2 Migration Isssue

I am trying to migrate Magento v1.9.5 data to Magento v2.3.5 using the following command:
bin/magento migrate:data --reset --auto /app/code/Vendor/Migration/etc/opensource-to-opensource/1.9.4.5/config.xml


This fails with this error:
[ERROR]: Not mapped id key 138 found for eav_entity_attribute.attribute_id

 

Can anybody give me any pointers in how to resolve this?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: M1 to M2 Migration Isssue

Right - I've sorted this without any apparent loss of data.

 

On the DESTINATION database (NOT the source database):

 

Remove 138 attribut_id row from catalog_eav_attribute

Remove 138 attribut_id row from eav_entity_attribute

catalog_product_entity_int was an empty table so no action required.

 

This generated the following error:

Notice: Undefined offset: 18 in /home/porscheshopco/testnewversion/vendor/m
agento/data-migration-tool/src/Migration/Step/Eav/Data.php on line 492

 

I corrected this by modifying '/vendor/m
agento/data-migration-tool/src/Migration/Step/Eav/Data.php' as per these instructions:

 

https://github.com/magento/data-migration-tool/commit/ea9cc9f21d3634dd3695fd88f9c869d9535cb6a6

 

Hope this may be of use to someone else.

View solution in original post

6 REPLIES 6

Re: M1 to M2 Migration Isssue

Hi @skinnybloke 

 

check for the attribute I’d 396 entry in eav_attribute table Magento 1 database

 

if this attribute is created from 3rd party extension then remove the extension class from attribute entry

if not then share the attribute data here

 

Hope this helps you!

Problem Solved! Click Kudos & Accept as Solution!

Re: M1 to M2 Migration Isssue

Hi Nishu - the attribute id is 138, not 396 as I specified. Details for the eav_attribute table are:

 

attribute_id: 138

entity_type_id: 4 - catalog_product

backend_type: int

frontend_input: select

frontend_label: Item_Selection

source_model: eav/entity_attribute_source_table

is_required: 0

is_user_defined: 1

is_unique: 0

fme_customer_account: 0

fme_email: 0

fme_pdf: 0

 

All other fields are blank

Re: M1 to M2 Migration Isssue

Hi @skinnybloke ,

 

do you have any entry for attribute is 396. I am checking for this id because your error mention this id

ERROR]: Not mapped id key 396 found for eav_entity_attribute.attribute_id

 

if entry exist please share the details.

 

Thanks!

Re: M1 to M2 Migration Isssue

Hi Nishu - as I mentioned in the post above 396 was a typo.

 

The error is:

ERROR]: Not mapped id key 138 found for eav_entity_attribute.attribute_id

 

Re: M1 to M2 Migration Isssue

Well, I tried deleting the following inspired by another thread but I still get the same error message:

 

Remove 138 attribut_id row from catalog_eav_attribute.

Remove 138 attribut_id row from catalog_product_entity_int.

Remove 138 attribut_id row from eav_entity_attribute.

 

 

Re: M1 to M2 Migration Isssue

Right - I've sorted this without any apparent loss of data.

 

On the DESTINATION database (NOT the source database):

 

Remove 138 attribut_id row from catalog_eav_attribute

Remove 138 attribut_id row from eav_entity_attribute

catalog_product_entity_int was an empty table so no action required.

 

This generated the following error:

Notice: Undefined offset: 18 in /home/porscheshopco/testnewversion/vendor/m
agento/data-migration-tool/src/Migration/Step/Eav/Data.php on line 492

 

I corrected this by modifying '/vendor/m
agento/data-migration-tool/src/Migration/Step/Eav/Data.php' as per these instructions:

 

https://github.com/magento/data-migration-tool/commit/ea9cc9f21d3634dd3695fd88f9c869d9535cb6a6

 

Hope this may be of use to someone else.

View solution in original post