magento / magento/data-migration-tool
The website with id 1 that was requested wasn't found. Verify the website and try again
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.3.7 and Magento 2.3.4
2. Data Migration tool 2.3.4
### Steps to reproduce
1. Install and configure data migration tool
2. Run `bin/magento migrate:settings vendor/magento/data-migration-tool/etc/opensource-to-opensource/1.9.3.7/config.xml` and wait to finish
3. Run `bin/magento migrate:data vendor/magento/data-migration-tool/etc/opensource-to-opensource/1.9.3.7/config.xml`
### Expected result
1. Expecting the actual data to migrate after settings and stores are migrated.
### Actual result
1. Error after running migrate:data.
`In WebsiteRepository.php line 110:`
`The website with id 1 that was requested wasn't found. Verify the website and try again. `
### Additional notes
I tried manually fixing it but I don't know where it is going wrong. The settings and stores get transferred in the migrate:settings step. I can see the data in de M2 database. But I cannot see any website or store with id 1. So I don't know why Magento is trying to load it anyway.
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 with the reported migrate:settings and migrate:data commands and the 1.9.3.7 configuration file, then inspect WebsiteRepository.php at line 110. Compare the migrated websites and stores in the Magento 2 database with the data requested during migrate:data. Done means the migration proceeds without the missing-website error and the expected data is migrated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100