magento / magento/data-migration-tool

Customer address problems after migration from Magento 1.9.2.3 to Magento 2.3.3

Open
#874 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
339
Forks
195
PR merge metrics
No merged PRs in 30d

Description

I have checked the eav_attribute_set and I do not have any attribute set with entity id 2,

I checked many solutions but has no luck till now, Please help me to out from this problem,
![Capture](https://user-images.githubusercontent.com/46959928/120061552-6d2b5980-c07b-11eb-8fa3-19bab86bf1bf.PNG)
![Capture_1](https://user-images.githubusercontent.com/46959928/120061555-6ef51d00-c07b-11eb-94f6-bfd27d98edbe.PNG)
![eav_attribute](https://user-images.githubusercontent.com/46959928/120061556-6f8db380-c07b-11eb-969b-aaa8088a5ef7.PNG)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names Magento 1.9.2.3 and 2.3.3 and points to the eav_attribute_set and eav_attribute tables, but it identifies no source file or test. Start by reproducing the customer-address migration and comparing the reported entity ID data; done would require a confirmed cause and a validated migration fix, neither of which is specified here.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.