magento / magento/data-migration-tool
Magento 2.4.3-p1 patch breaks data migration
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 339
- Forks
- 195
- PR merge metrics
- No merged PRs in 30d
Description
Magento 2.4.3-p1 patch breaks data migration. Two new fields 'customer_entity.session_cutoff' and 'customer_visitor.created_at' are added in this patch and cause two 'Destination fields not mapped' errors.
The same data migration configuration works in 2.4.3.
I have tried adding ignore field tags in the destination/field_rules section of map.xml, but this has no effect.
Running the data migration with the -auto option allows migration to complete. but customers are not migrated.
Preconditions
- Magento 2.4.3-p1
- Data migration tool 2.4.3
Steps to reproduce
- Prepare migration config
- Run php bin/magento migrate:data app/code/Company/Migration/etc/opensource-to-opensource/1.9.2.1/config.xml
Expected result
- Magento 1 data migrates to Magento 2 successfully
Actual result
- Data migration halts with 'Destination field not mapped' errors for fields 'customer_entity.session_cutoff' and 'customer_visitor.created_at'
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
Start by reviewing the migration command and the referenced config.xml and map.xml files, then reproduce the failure with Magento 2.4.3-p1 and Data Migration Tool 2.4.3. Check how the two reported destination fields are handled and confirm that migration completes without unmapped-field errors and customers are migrated.
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
- 40/100