magento / magento/data-migration-tool
Merge of EAV Structure of Magento 1 with Magento 2 > Product Information lost caused by missing merge.
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 339
- Forks
- 195
- PR merge metrics
- No merged PRs in 30d
Description
### Preconditions
1. Magento 1.9.0.1, Magento 2.3.5-p1
2. PHP 7.2.32
3. DTM 2.3.5
### Steps to reproduce
1. Migrate settings and data from M1 to M2
### Expected result
1. Custom attributes from M1 attribute set 'Default' attribute groups 'General' and 'Prices' are merged into M2 attribute set 'Default' groups 'General' and 'Prices'.
### Actual result
1. Custom attributes are migrated but not merged into attribute groups 'General' and 'Prices'
### Additional notes
This is shop breaking behavior since all product information regarding the not merged attributes is lost.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Reproduce the migration from Magento 1.9.0.1 to Magento 2.3.5-p1 with the described custom attributes, then trace the product attribute-set and group migration path. Done means the custom attributes appear in the Magento 2 Default set's General and Prices groups without losing product information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100