Attribute groups are not taken into consideration while migrating

[mszterlingfsite]

When migrating from 1.7.0.2 CE, there are some attribute groups (such as General for Products) - which is called Product Details in M2, as a result some attributes which are required for M2 are not present or are in different tabs where expected.

Migration tool should really convert CE 1.x into EE 2.0 format, not just COPY as it is

[ilol]

@mszterlingfsite Thank you for this suggestion as well. I am setting up th e meeting with developers to discuss your issues.

[victor-v-rad]

It is a good idea to make migrated attributes and their positions in attribute groups more similar to Magento 2 attribute set. Corresponding internal issue was created to investigate this improvement

[ilol]

Registered: MAGETWO-52479

[dfelton]

If my research serves me correct, it is not the difference in attribute group names that is causing this issue, but the lack of a record for these attributes in the source database's eav_entity_attribute table (which is normal Magento 1 behavior) . Please see issue #212 for further information.

[TechNix66]

Thanks a lot @dfelton ! Your feedback was the solution for my problem.

[dfelton]

@TechNix66 your welcome and happy migrating :)

[victor-v-rad]

Hi @dfelton

You might noticed that migrated product attribute sets and attribute groups get "Migration_" prefix and its structure is more like Magento 1 style than Magento 2. At the same time the structure of "Default" attribute set of Magento 2 stays unattached. I wonder if it is an issue for you? Do you manually rearrange migrated layout of attribute sets?

[dfelton]

@victor-v-rad

What you describe is correct, the Magento 1 attribute sets get migrated over to Magento 2 in an identical structure as what they were in the Magento 1 database, with the only difference being an addition of adding the "Migration_" prefix to the values of the eav_attribute_set.attribute_set_name and eav_attribute_group.attribute_group_name.

After migration, yes I do perform a manual rearranging of the layout of the migrated attribute sets. The only re-arranging performed however, is manually moving the system attributes into the attribute set, that were not part of the Magento 1 attribute set. This has only ever included the attributes I mentioned in issue #212.

Any other questions let me know I'd be happy to answer.

[PascalBrouwers]

@victor-v-rad any progress on this?