Skip to content
Victor Rad edited this page May 13, 2020 · 13 revisions

The Data Migration Tool project enables merchants to upgrade their Magento 1 store to the latest version of Magento 2 by transferring database data. Read Data Migration Guide for more information.

Reporting issue rules

  • Reported issues in this project are supported mainly by Magento community. Please submit a support ticket here https://magento.com/contact-us if you migrate to Magento 2 Commerce
  • Before reporting new issue try to find a similar among existing
  • Use template which appears while creating new issue for better description

How to contribute

  • If you found a bug during migration and fixed it, then create PR into 2.3-develop branch with explanation about the issue and create new GitHub issue with link to the PR
  • Feature improvements to develop and known issues can be found in the Community Board. To take on some of them you need to request to join either Community Contributors or Migration Tool Contributors to be able to drag from "To Do" column to "In progress". It would be best to discuss details of implementation beforehand in community Slack channel #data-migration-tool
  • New ideas for improvements can be outlined in new issue and discussed in community Slack channel #data-migration-tool
  • Pull requests (PRs) must be accompanied by a meaningful description of their purpose. Comprehensive descriptions increase the chances of a pull request being merged quickly and without additional clarification requests
  • Commits must be accompanied by meaningful commit messages
  • Contributions must adhere to the Magento coding standards

Issues Board

  • Community Board encompass founded issues to fix and improvements to develop which can be pick up by anyone who want to contribute to the project. Any of them can be discussed in comments to the issue or community Slack channel #data-migration-tool

Issue Labels

  • acknowledged + bug means an issue is reproducible with clear steps and caused by the tool
  • improvement enhancement of existing feature
  • feature request new feature to develop
  • up for grabs new feature or enhancement to develop by community
  • question means question
  • needs update issue misses important information from reporter for reproducing on it

Repository

There are the following branches in the repository:

  • 2.3-develop - current development branch for the bug-fixes and improvements which are going to be released in next patch version
  • master - stable branch with the latest release