magento / magento/data-migration-tool
Story: auto-resolving of issues and help during migration
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 339
- Forks
- 195
- PR merge metrics
- No merged PRs in 30d
Description
The main goal of this story is to help our customers on the way of migration and decrease the overall time spent to have Magento 2 store ready for launch.
The usual behavior of Data Migration Tool is to stop process in case of some error. For example: Integrity check inconsistency, orphan records in DB, not existing class on EAV step and so on. This by design behavior was developed because there are many ways to resolve it and which one serves best for a client is simply unknown. But having **auto-resolve mode** and **interactive mode** will help to decrease the overall time for migration if the client wants one-button solution.
Also making the tool more informative in case of errors will help our customers resolve it more efficiently. Namely transfer parts of [Migration Guide](http://devdocs.magento.com/guides/v2.2/migration/bk-migration-guide.html) into DMT code.
Acceptance Criteria:
- interactive mode is set by default (-i, --interaction). As soon as an error appears migration paused and auto-resolving of the issue is proposed with detailed information how it is going to be fixed. Also customer can stop migration and fix it by himself
- auto-resolve mode can be set in CLI as an option (-a, --auto). In case of an error happens the tool throw warning about it with details how exactly it was resolved and proceed further
- parts of [Migration Guide](http://devdocs.magento.com/guides/v2.2/migration/bk-migration-guide.html) are transferred into the tool. Hints are proposed to the customer if something went wrong
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 reading the acceptance criteria and the linked Migration Guide, then trace how the Data Migration Tool currently reports migration errors and exposes CLI options. Define the scope for interactive and auto-resolve modes, including error details, warnings, hints, and migration continuation. Done means the requested options and behaviors are implemented across the relevant migration failures and documented guidance is available in the tool.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100