Magento Data Migration Tool

Overview

Overview

We're pleased you're considering moving from the world's #1 eCommerce platform—Magento 1.x—to the eCommerce platform for the future, Magento 2. We're also excited to share the details about this process, which we refer to as migration.

Magento 2 migration involves four components: data, extensions and custom code, themes, and customizations.

Data

We've developed the Magento 2 Data Migration Tool to help you efficiently move all of your products, customers, and order data, store configurations, promotions and more to Magento 2. See the Magento Migration Guide for details.

Extensions and custom code

We've been working hard with the development community to help you use your Magento 1 extensions in Magento 2. Now we're proud to present the Magento Marketplace, where you can download or purchase the latest versions of your favourite extensions.

Also, we have developed the Code Migration Toolkit, which will help to port extensions and your custom code to Magento 2, significantly reducing your porting efforts.

More information on developing extensions for Magento 2 is available in the Magento 2 Extension Developer Guide.

Themes and Customizations

Magento 2 uses new approaches and technologies that give merchants an unmatched ability to create innovative shopping experiences and scale to new levels. To take advantage of these advances, developers will need to make changes to their themes and customizations. Documentation is available online for creating Magento 2 themes, layouts, and customizations.

Supported versions

This edition of tool supports the following versions for migration:

  • Magento Open Source version 1.6.x, 1.7.x, 1.8.x, 1.9.x

  • Magento Commerce version 1.11.x, 1.12.x, 1.13.x, 1.14.x

If you migrate from Magento Open Source to Magento Commerce, the following versions are supported:

  • 1.6.x, 1.7.x, 1.8.x, 1.9.x

Supporting issues and Pull Request contributions

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. Contributions like Pull Requests are welcome and we will process/merge it

Prerequisites

Before you start your migration, you must do all of the following:

Set up your system using a topology and design that at least matches your existing Magento 1.x system.
  • Do not start Magento 2 cron jobs.

  • Back up or dump your Magento 2 database as soon after installation as possible.

  • Check that the data migration tool has a network connection to the Magento 1.x and Magento 2 databases.

Open ports in your firewall so the migration tool can communicate with the databases and so the databases can communicate with each other.
  • Migrate Magento 1.x extension and custom code to Magento 2.
Reach out to your extension providers to see if they have been ported yet.

Install the Data Migration Tool

This section discusses how to install the Magento Data Migration Tool. You can install it from either repo.magento.com or from a GitHub repository.

Note: The versions of both the migration tool and the Magento 2 code must be identical (for example, 2.4.0). To find the version of either package, open composer.json and find the value of "version".

Install the tool from GitHub

To install the migration tool from GitHub, use the following steps:

  1. Log in to your Magento 2 server as a user with privileges to write to the Magento 2 file system or switch to the web server user.

  2. Go to Magento 2 root directory.

  3. Enter the following commands:

    composer config repositories.data-migration-tool git https://github.com/magento/data-migration-tool
    composer require magento/data-migration-tool:<version>
    

    where <version> is release version (e.g. 2.4.0)

  4. Wait while dependencies are updated.

Install the tool from repo.magento.com

To install the Data Migration Tool, you must update composer.json in the Magento root installation directory to provide the location of the migration tool package.

To install the migration tool, you must:

  1. Decide the version of magento/data-migration-tool you want as discussed in the preceding section.

  2. Run the composer config and composer require commands to update composer.json.

  3. When prompted, enter your authentication keys. Your public key is your username; your private key is your password.

To update composer.json:

  1. Log in to your Magento server as the web server user or as a user with root privileges.

  2. Change to your Magento installation directory.

  3. Enter the following command to reference Magento packages in composer.json:

    composer config repositories.magento composer https://repo.magento.com
    
  4. Enter the following command to require the current version of the package:

    composer require magento/data-migration-tool:<version>
    

    where <version> is either an exact version or next significant release syntax.

    Exact version example:

    composer require magento/data-migration-tool:2.4.0
    

    Next significant release example:

    composer require magento/data-migration-tool:~2.4
    
  5. Wait while dependencies are installed.

More details

See the Migration Guide for the detailed help with your data migration process.

Comments
  • Delta changes not migrated

    Delta changes not migrated

    We completed the migration successfully. When we try to do the delta changes we get the below warnings. And the delta changes were not at all carried out for the entities (orders, invoices, shipments, returns, credits, customers, transactions, reviews).

    [2017-06-08 10:29:26][INFO][mode: delta][stage: delta delivering][step: Custom Customer Attributes Step]: started [2017-06-08 10:29:26][INFO][mode: delta][stage: volume check][step: Custom Customer Attributes Step]: started [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: magento_customercustomattributes_sales_flat_order [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: magento_customercustomattributes_sales_flat_order_address [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: magento_customercustomattributes_sales_flat_quote [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: magento_customercustomattributes_sales_flat_quote_address [2017-06-08 10:29:26][WARNING]: Volume Check failed [2017-06-08 10:29:26][INFO][mode: delta][stage: delta delivering][step: Customer Attributes Step]: started [2017-06-08 10:29:26][INFO][mode: delta][stage: volume check][step: Customer Attributes Step]: started [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: customer_entity [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: customer_entity_int [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: customer_entity_text [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: customer_entity_varchar [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: customer_address_entity [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: customer_address_entity_int [2017-06-08 10:29:26][WARNING]: Volume Check failed [2017-06-08 10:29:26][INFO][mode: delta][stage: delta delivering][step: Map Step]: started [2017-06-08 10:29:26][INFO][mode: delta][stage: delta delivering][step: Log Step]: started [2017-06-08 10:29:26][INFO][mode: delta][stage: volume check][step: Log Step]: started [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: customer_visitor [2017-06-08 10:29:26][WARNING]: Volume Check failed [2017-06-08 10:29:26][INFO][mode: delta][stage: delta delivering][step: SalesOrder Step]: started [2017-06-08 10:29:26][INFO][mode: delta][stage: volume check][step: SalesOrder Step]: started [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: sales_order [2017-06-08 10:29:26][WARNING]: Volume Check failed [2017-06-08 10:29:26][INFO][mode: delta][stage: delta delivering][step: OrderGrids Step]: started [2017-06-08 10:29:26][INFO][mode: delta][stage: volume check][step: OrderGrids Step]: started [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: sales_order_grid [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: sales_invoice_grid [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: sales_shipment_grid [2017-06-08 10:29:26][WARNING]: Mismatch of entities in the document: sales_creditmemo_grid [2017-06-08 10:29:26][WARNING]: Volume Check failed [2017-06-08 10:29:26][INFO][mode: delta][stage: delta delivering][step: SalesIncrement Step]: started [2017-06-08 10:29:26][INFO][mode: delta][stage: volume check][step: SalesIncrement Step]: started [2017-06-08 10:29:26][WARNING]: Mismatch in last increment id of order entity [2017-06-08 10:29:26][WARNING]: Mismatch in last increment id of invoice entity [2017-06-08 10:29:26][WARNING]: Mismatch in last increment id of creditmemo entity [2017-06-08 10:29:26][WARNING]: Mismatch in last increment id of shipment entity [2017-06-08 10:29:26][WARNING]: Mismatch in last increment id of rma_item entity [2017-06-08 10:29:26][WARNING]: Volume Check failed [2017-06-08 10:29:26][INFO][mode: delta][stage: volume check][step: SalesIncrement Step]: Migration completed successfully [2017-06-08 10:29:26][INFO][mode: delta][stage: volume check][step: SalesIncrement Step]: Automatic restart in 5 sec. Use CTRL-C to abort [2017-06-08 10:29:31][INFO][mode: delta][stage: delta delivering][step: Custom Customer Attributes Step]: started [2017-06-08 10:29:31][INFO][mode: delta][stage: volume check][step: Custom Customer Attributes Step]: started [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: magento_customercustomattributes_sales_flat_order [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: magento_customercustomattributes_sales_flat_order_address [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: magento_customercustomattributes_sales_flat_quote [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: magento_customercustomattributes_sales_flat_quote_address [2017-06-08 10:29:31][WARNING]: Volume Check failed [2017-06-08 10:29:31][INFO][mode: delta][stage: delta delivering][step: Customer Attributes Step]: started [2017-06-08 10:29:31][INFO][mode: delta][stage: volume check][step: Customer Attributes Step]: started [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: customer_entity [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: customer_entity_int [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: customer_entity_text [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: customer_entity_varchar [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: customer_address_entity [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: customer_address_entity_int [2017-06-08 10:29:31][WARNING]: Volume Check failed [2017-06-08 10:29:31][INFO][mode: delta][stage: delta delivering][step: Map Step]: started [2017-06-08 10:29:31][INFO][mode: delta][stage: delta delivering][step: Log Step]: started [2017-06-08 10:29:31][INFO][mode: delta][stage: volume check][step: Log Step]: started [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: customer_visitor [2017-06-08 10:29:31][WARNING]: Volume Check failed [2017-06-08 10:29:31][INFO][mode: delta][stage: delta delivering][step: SalesOrder Step]: started [2017-06-08 10:29:31][INFO][mode: delta][stage: volume check][step: SalesOrder Step]: started [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: sales_order [2017-06-08 10:29:31][WARNING]: Volume Check failed [2017-06-08 10:29:31][INFO][mode: delta][stage: delta delivering][step: OrderGrids Step]: started [2017-06-08 10:29:31][INFO][mode: delta][stage: volume check][step: OrderGrids Step]: started [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: sales_order_grid [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: sales_invoice_grid [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: sales_shipment_grid [2017-06-08 10:29:31][WARNING]: Mismatch of entities in the document: sales_creditmemo_grid [2017-06-08 10:29:31][WARNING]: Volume Check failed [2017-06-08 10:29:31][INFO][mode: delta][stage: delta delivering][step: SalesIncrement Step]: started [2017-06-08 10:29:31][INFO][mode: delta][stage: volume check][step: SalesIncrement Step]: started [2017-06-08 10:29:32][WARNING]: Mismatch in last increment id of order entity [2017-06-08 10:29:32][WARNING]: Mismatch in last increment id of invoice entity [2017-06-08 10:29:32][WARNING]: Mismatch in last increment id of creditmemo entity [2017-06-08 10:29:32][WARNING]: Mismatch in last increment id of shipment entity [2017-06-08 10:29:32][WARNING]: Mismatch in last increment id of rma_item entity [2017-06-08 10:29:32][WARNING]: Volume Check failed [2017-06-08 10:29:32][INFO][mode: delta][stage: volume check][step: SalesIncrement Step]: Migration completed successfully

    Note: we have not changed anything on the M2 DB post data migration other than adding few custom customer attributes. We tried to initiate the delta migration after a week time.

    Please help. We highly rely on this tool.

    question 
    opened by rg-srini 44
  • Attempt to load value of nonexistent EAV attribute

    Attempt to load value of nonexistent EAV attribute

    Preconditions

    1. Magento 1 EE 1.14.3.10
    2. Magento 2 EE 2.2.6
    3. PHP 7.1.22
    4. MySQL 5.7.23

    Steps to reproduce

    1. Migrate data from Magento 1 to 2
    2. View a product page

    Expected result

    1. No error. This error started to occur in Magento EE 2.2.6.

    Actual result

    1. Errors in system.log and support_report.log
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '83' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '169' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '501' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '167' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '215' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '220' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '223' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '395' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '402' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '417' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '451' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '452' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:52] report.WARNING: Attempt to load value of nonexistent EAV attribute '551' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '83' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '438' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '167' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '215' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '220' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '221' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '222' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '223' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '269' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '332' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '395' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '402' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '417' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '451' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '452' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    [2018-10-05 12:40:53] report.WARNING: Attempt to load value of nonexistent EAV attribute '470' 
                            for entity type 'Magento\Catalog\Api\Data\ProductInterface'. [] []
    
    1. But these attributes do in fact exist, for example eav_attribute 83
    SELECT attribute_id, entity_type_id, attribute_code, attribute_model, backend_model, backend_type, backend_table, frontend_model, frontend_input, frontend_label, frontend_class, source_model, is_required, is_user_defined, default_value, is_unique, note
    FROM magento2_prod.eav_attribute
    WHERE attribute_id=83;```
    
    

    attribute_id entity_type_id attribute_code attribute_model backend_model backend_type backend_table frontend_model frontend_input frontend_label frontend_class source_model is_required is_user_defined default_value is_unique note 83 4 color [NULL] [NULL] int [NULL] [NULL] select Color [NULL] [NULL] 0 1 [NULL] 0 [NULL]

    bug acknowledged 
    opened by craigcarnell 41
  • After successful Migration: SQLSTATE[42000]: Syntax error or access violation: 1103 Incorrect table name '',

    After successful Migration: SQLSTATE[42000]: Syntax error or access violation: 1103 Incorrect table name '',

    After successful migration (no errors) we have a problem accessing the products grid in the backend with the following error:


    SQLSTATE[42000]: Syntax error or access violation: 1103 Incorrect table name '', query was: SELECT COUNT(DISTINCT main_table.attribute_id) FROM eav_attribute AS main_table INNER JOIN eav_entity_type AS entity_type ON main_table.entity_type_id = entity_type.entity_type_id INNER JOIN eav_entity_attribute ON main_table.attribute_id = eav_entity_attribute.attribute_id INNER JOIN ``ASadditional_tableON main_table.attribute_id = additional_table.attribute_id WHERE (entity_type_code= 'catalog_product') AND (additional_table.is_used_in_grid = 1)


    All other stuff should be ok and also the products are shown in the frontend.

    opened by andidhouse 40
  • [Migration\Exception] - Integrity Check failed  1.9.2.2 -> CE 2.0.0

    [Migration\Exception] - Integrity Check failed 1.9.2.2 -> CE 2.0.0

    Hi guys,

    I have following the guide to use this tool at http://devdocs.magento.com/guides/v2.0/migration/migration-migrate.html

    I have finished the "Migrate settings" step

    • Command was run:

    php -f /home/qvv/www/_shared/mage2/ce-200-dev/bin/magento migrate:settings -r /home/qvv/www/_shared/mage2/ce-200-dev/vendor/magento/data-migration-tool/etc/ce-to-ce/1.9.2.2/config.xml

    But the tool get errors at "Migrate data" step as the screenshots:

    • Command was run:

    php -f /home/qvv/www/_shared/mage2/ce-200-dev/bin/magento migrate:data /home/qvv/www/_shared/mage2/ce-200-dev/vendor/magento/data-migration-tool/etc/ce-to-ce/1.9.2.2/config.xml

    migrate data error and error more

    Only websites, stores and some configs data was migrated to Magento 2 and no more.

    and i can't finished the data migration on this step

    Any ideas to solve that issues?

    Thanks.

    opened by quynhvv 40
  •   [PDOException]   SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-Migration_Default' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_NAME'

    [PDOException] SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-Migration_Default' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_NAME'

    Hi, I am using this data-migration-tool, getting below error, [PDOException] SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-Migration_Default' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_NAME'

    Note: I am migrating datas from magento1.13.1.0 to magento 2.1.0

    question 
    opened by VignaPranav 38
  • Migration: [ERROR]: Document has ambiguous configuration: sales_flat_quote_payment

    Migration: [ERROR]: Document has ambiguous configuration: sales_flat_quote_payment

    I have got a error like below,

    [ERROR]: Document has ambiguous configuration: sales_flat_quote_payment

    I have ignore the table

    sales_flat_quote_payment

    question 
    opened by Dregolwd 37
  • Migrating from Magento CE 1.9.0.1 to Magento EE 2.1.0 1062 Duplicate entry '1-Migration_Default' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_NAME'

    Migrating from Magento CE 1.9.0.1 to Magento EE 2.1.0 1062 Duplicate entry '1-Migration_Default' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_NAME'

    [PDOException]
    SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-Migration_Default' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_NAME'

    migration

    [Exception]
    Notice: Undefined offset: 1 in vendor/magento/data-migration-tool/src/Migration/Step/Eav/Data.php on line 261 migrate

    opened by kiranmaip 32
  • [Migration\Exception] - Integrity Check failed 1.9.0.1 -> CE 2.0.0

    [Migration\Exception] - Integrity Check failed 1.9.0.1 -> CE 2.0.0

    Hello All,

    I am trying to port existing magento 1.9.0.1 to Magento 2.0. I was able to run ./magento migrate:settings (mode) , but when I executed data mode, there were errors

    [ERROR]: Source documents are missing or not mapped: amazon_log_api,amazon_log_exception

    I have added ignore fields to the file map.xml present in vendor/magento/data-migration-tool/etc/ce-to-ce/1.9.0.1/map.xml

    Below is the example I have added,

    amazon_log_api.log_id amazon_log_api.host

    Even though after making all above mentioned modification, I can see error which says it could not map database I have followed suggestions from this post, but It did not help https://github.com/magento/data-migration-tool-ce/issues/19

    Please let me know how to proceed further by adding, particualy, where to add ignore fields, I have added all fields in each table, it would be nice if there is a option to just mention table and all its column would be automatically ignored.

    Also, if there are any issues, please let me know, As I am a beginner, please explain me in detail as it would really help me to understand, Appreciate your help, I have tried for a week and was frustrated as I could not find more information,

    Looking forward for your response,

    opened by vcpawate 26
  • Duplicate entry

    Duplicate entry "reques path" although different store_id

    I don't now why I can't migrate url_rewrite table with same "request path" value but different store_id. I think this is a bug of this tool. Do you have any idea? screenshot_2

    opened by Vincenkt 25
  • How to fix? element cannot be added as child to sidebar.additional and sidebar.main, because the latter doesn't exist

    How to fix? element cannot be added as child to sidebar.additional and sidebar.main, because the latter doesn't exist

    Hi, I'm receiving these errors about "element cannot be added as child to 'sidebar.additional', because the latter doesn't exist".

    [2018-02-02 12:20:24] main.INFO: Broken reference: the 'catalog.compare.sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] [] [2018-02-02 12:20:24] main.INFO: Broken reference: the 'sale.reorder.sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] [] [2018-02-02 12:20:24] main.INFO: Broken reference: the 'wishlist_sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] [] [2018-02-02 12:20:24] main.INFO: Broken reference: the 'paypal.partner.right.logo' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] [] [2018-02-02 12:20:24] main.INFO: Broken reference: the 'bml.right.logo' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] [] [2018-02-02 12:20:24] main.INFO: Broken reference: the 'umm.sidemenu.catalog_category_view.main' element cannot be added as child to 'sidebar.main', because the latter doesn't exist [] [] [2018-02-02 12:20:24] main.INFO: Broken reference: the 'sidebar_main_top_before_laynav' element cannot be added as child to 'sidebar.main', because the latter doesn't exist [] [] [2018-02-02 12:20:24] main.INFO: Broken reference: the 'umm.sidemenu.catalog_category_view.additional' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] [] [2018-02-02 12:20:24] main.INFO: Broken reference: the 'catalog.leftnav' element cannot be added as child to 'sidebar.main', because the latter doesn't exist [] [] [2018-02-02 12:20:24] main.INFO: Broken reference: the 'umm.sidemenu.catalog_category_view.main' tries to reorder itself towards '', but their parents are different: 'sidebar.main' and '' respectively. [] [] [2018-02-02 12:20:24] main.INFO: Broken reference: the 'sidebar_main_top_before_laynav' tries to reorder itself towards '', but their parents are different: 'sidebar.main' and '' respectively. [] [] [2018-02-02 12:20:24] main.INFO: Broken reference: the 'umm.sidemenu.catalog_category_view.additional' tries to reorder itself towards '', but their parents are different: 'sidebar.additional' and '' respectively. [] [] [2018-02-02 12:20:24] main.INFO: Broken reference: the 'catalog.leftnav' tries to reorder itself towards '', but their parents are different: 'sidebar.main' and '' respectively. [] []

    Someone could guide me to fix the issue with my sidebar.main and sidebar.additional? Thanks in advance.

    ##################### EDIT

    I didn't saw this issue at migration until weeks of the installation, so currently my M2 is under production with this bug. As said @victor-v-rad this errors seems not relevant with the issue.

    I would try to detail the error:

    At BBDD we have all the fields of our megamenu in the categories. You can writte all these fields at database manually, so you are going to see working correctly the "umm" (Universal MegaMenu) at front-end.

    The problem is at backend, when you edit any category all the fields at megamenu are going to be deleted.

    I have tried to uninstall I have installed the extension, and to install other similar megamenu solutions with the same result.

    Without experience at M2 I though that the log file with "umm.sidemenu" was related, but I was wrong.

    question 
    opened by cmcimport 23
  • Want To Migrate Only Product from 1.9.3.2 to 2.2.0

    Want To Migrate Only Product from 1.9.3.2 to 2.2.0

    Hii @victor-v-rad

    After migration my products are deleted by mistake and want to migrate only Products , i have tried data migration with "-a " attribute , but products not migrated , can you tell me from which step Products migrate .

    Thanks Yogesh

    question 
    opened by yogeshsyscraft 23
  • Data Migration stuck at catalog_product_entity_media_gallery_value

    Data Migration stuck at catalog_product_entity_media_gallery_value

    Preconditions

    1. Magento 1.9.3.3 open source
    2. Magento 2.4.3-p1 open source

    Steps to reproduce

    1. migrate:data --auto vendor/magento/data-migration-tool/etc/opensource-to-opensource/1.9.3.3/config.xml

    Expected result

    1. Data should be successfully migrated

    Actual result

    1. Stuck at catalog_product_entity_media_gallery_value with 0%

    Additional notes

    1. I have already done the data migration previously. Do I have to truncate the entire M2 DB to start the migration again?
    opened by guptarakesh2701 1
  • Migration\Handler\SetValue not compatible with PHP 8.1

    Migration\Handler\SetValue not compatible with PHP 8.1

    Preconditions

    1. Magento 1 with tier prices
    2. Migration to Magento 2.4.5 (opensource to opensource)
    3. PHP 8.1

    Steps to reproduce

    1. Migrate Magento 1 to Magento 2

    Expected result

    1. Migration completes successfully

    Actual result

    Error in the OrderGrids Step:

    [2022-12-05T08:22:49.790153+00:00][DEBUG][mode: data][stage: data migration][step: Tier Price Step][table: catalog_product_entity_tier_price]: migrating
    0% [>---------------------------] Remaining Time: < 1 sec
    In ErrorHandler.php line 62:
                                                                                   
      [Exception]                                                                  
      Deprecated Functionality: substr(): Passing null to parameter #1 ($string)   
      of type string is deprecated in /var/www/html/magento/vendor/magento/data-m  
      igration-tool/src/Migration/Handler/SetValue.php on line 35                  
                                                                                   
    
    Exception trace:
      at /var/www/html/magento/vendor/magento/framework/App/ErrorHandler.php:62
     Magento\Framework\App\ErrorHandler->handler() at n/a:n/a
     substr() at /var/www/html/magento/vendor/magento/data-migration-tool/src/Migration/Handler/SetValue.php:35
     Migration\Handler\SetValue->handle() at /var/www/html/magento/vendor/magento/data-migration-tool/src/Migration/RecordTransformer.php:126
     Migration\RecordTransformer->applyHandlers() at /var/www/html/magento/vendor/magento/data-migration-tool/src/Migration/RecordTransformer.php:74
     Migration\RecordTransformer->transform() at /var/www/html/magento/vendor/magento/data-migration-tool/src/Migration/Step/TierPrice/Data.php:139
     Migration\Step\TierPrice\Data->perform() at /var/www/html/magento/vendor/magento/data-migration-tool/src/Migration/Mode/AbstractMode.php:82
     Migration\Mode\AbstractMode->runStage() at /var/www/html/magento/vendor/magento/data-migration-tool/src/Migration/Mode/Data.php:124
     Migration\Mode\Data->runData() at /var/www/html/magento/vendor/magento/data-migration-tool/src/Migration/Mode/Data.php:69
     Migration\Mode\Data->run() at /var/www/html/magento/vendor/magento/data-migration-tool/src/Migration/Console/MigrateDataCommand.php:59
     Migration\Console\MigrateDataCommand->execute() at /var/www/html/magento/vendor/symfony/console/Command/Command.php:255
     Symfony\Component\Console\Command\Command->run() at /var/www/html/magento/vendor/magento/framework/Interception/Interceptor.php:58
     Migration\Console\MigrateDataCommand\Interceptor->___callParent() at /var/www/html/magento/vendor/magento/framework/Interception/Interceptor.php:138
     Migration\Console\MigrateDataCommand\Interceptor->Magento\Framework\Interception\{closure}() at /var/www/html/magento/vendor/magento/framework/Interception/Interceptor.php:153
     Migration\Console\MigrateDataCommand\Interceptor->___callPlugins() at /var/www/html/magento/generated/code/Migration/Console/MigrateDataCommand/Interceptor.php:77
     Migration\Console\MigrateDataCommand\Interceptor->run() at /var/www/html/magento/vendor/symfony/console/Application.php:1021
     Symfony\Component\Console\Application->doRunCommand() at /var/www/html/magento/vendor/symfony/console/Application.php:275
     Symfony\Component\Console\Application->doRun() at /var/www/html/magento/vendor/magento/framework/Console/Cli.php:116
     Magento\Framework\Console\Cli->doRun() at /var/www/html/magento/vendor/symfony/console/Application.php:149
     Symfony\Component\Console\Application->run() at /var/www/html/magento/bin/magento:23
    

    Additional notes

    The problem is triggered by the map-tier-price.xml.dist configuration

                <transform>
                    <field>catalog_product_entity_group_price.value_id</field>
                    <handler class="\Migration\Handler\SetValue">
                        <param name="value" value="NULL" />
                    </handler>
                </transform>
                <transform>
                    <field>catalog_product_entity_tier_price.value_id</field>
                    <handler class="\Migration\Handler\SetValue">
                        <param name="value" value="NULL" />
                    </handler>
                </transform>
    

    because the Migration\Handler\SetValue class throws an error if NULL should be set:

    <?php
    /**
     * Copyright © Magento, Inc. All rights reserved.
     * See COPYING.txt for license details.
     */
    namespace Migration\Handler;
    
    use Migration\ResourceModel\Record;
    
    /**
     * Handler to set constant value to the field
     */
    class SetValue extends AbstractHandler implements HandlerInterface
    {
        /**
         * @var string
         */
        protected $value;
    
        /**
         * @param string $value
         */
        public function __construct($value)
        {
            $this->value = (strtoupper($value) === 'NULL') ? null : $value;
        }
    
        /**
         * @inheritdoc
         */
        public function handle(Record $recordToHandle, Record $oppositeRecord)
        {
            $this->validate($recordToHandle);
            $valueStored = $recordToHandle->getValue($this->field);
            $operator = substr($this->value, 0, 1);
            $value = substr($this->value, 1);
            switch ($operator) {
                case '+':
                    $value = $valueStored + $value;
                    break;
                case '-';
                    $value = $valueStored - $value;
                    break;
                default:
                    $value = $this->value;
            }
            $recordToHandle->setValue($this->field, $value);
        }
    }
    

    The problem are the lines

            $operator = substr($this->value, 0, 1);
            $value = substr($this->value, 1);
    

    if $this->value is null, since null musn't be used anymore in substr.

    As a workaround I changed the lines to

            $operator = substr($this->value ?? '', 0, 1);
            $value = substr($this->value ?? '', 1);
    

    and could finish the migration.

    opened by Barakur 2
  • Update SetValue.php

    Update SetValue.php

    PHP 8.1 compatible. Deprecated usage of function. Giving error in script.

    Description

    Fixed Issues (if relevant)

    1. magento/data-migration-tool#<issue_number>: Issue title
    2. ...

    Manual testing scenarios

    1. ...
    2. ...

    Contribution checklist

    • [ ] Pull request has a meaningful description of its purpose
    • [ ] All commits are accompanied by meaningful commit messages
    • [ ] All new or changed code is covered with unit/integration tests (if applicable)
    • [ ] README.md file is updated and included in the pull request if any README.md predefined sections require an update
    opened by dlabsnl 0
  • Migration getting stuck at post processing leftover

    Migration getting stuck at post processing leftover

    Preconditions

    1. Magento 1.9.4.5
    2. Magento 2.4.5 MySQL 8.0.29, PHP 8.1.10
    3. several modules installed

    Steps to reproduce

    1. install Magento 2.4.5 with data-migration-tool 2.4.5
    2. run bin/magento migrate:settings [...]/magento2/vendor/magento/data-migration-tool/etc/opensource-to-opensource/1.9.4.5/config.xml without errors
    3. run bin/magento migrate:data [...]/magento2/vendor/magento/data-migration-tool/etc/opensource-to-opensource/1.9.4.5/config.xml
    4. At post processing step 80% getting error: 'Argument#1 must be of type array, null given'

    Expected result

    1. Expected succesful migration step post processing after all other steps run without errors

    Actual result

    Stack Trace [2022-09-23T19:57:52.770580+00:00][INFO][mode: data][stage: data migration][step: PostProcessing Step]: started 80% [======================>-----] Remaining Time: < 1 secarray_merge(): Argument #1 must be of type array, null given#0 [...]/magento2/vendor/magento/data-migration-tool/src/Migration/Step/PostProcessing/Data/DeletedRecordsCounter.php(93): array_merge() #1 [...]/magento2/vendor/magento/data-migration-tool/src/Migration/Step/PostProcessing/Data.php(110): Migration\Step\PostProcessing\Data\DeletedRecordsCounter->saveChanged() #2 [...]/magento2/vendor/magento/data-migration-tool/src/Migration/Mode/AbstractMode.php(82): Migration\Step\PostProcessing\Data->perform() #3 [...]/magento2/vendor/magento/data-migration-tool/src/Migration/Mode/Data.php(124): Migration\Mode\AbstractMode->runStage() #4 [...]/magento2/vendor/magento/data-migration-tool/src/Migration/Mode/Data.php(69): Migration\Mode\Data->runData() #5 [...]/magento2/vendor/magento/data-migration-tool/src/Migration/Console/MigrateDataCommand.php(59): Migration\Mode\Data->run() #6 [...]/magento2/vendor/symfony/console/Command/Command.php(255): Migration\Console\MigrateDataCommand->execute() #7 [...]/magento2/vendor/magento/framework/Interception/Interceptor.php(58): Symfony\Component\Console\Command\Command->run() #8 [...]/magento2/vendor/magento/framework/Interception/Interceptor.php(138): Migration\Console\MigrateDataCommand\Interceptor->___callParent() #9 [...]/magento2/vendor/magento/framework/Interception/Interceptor.php(153): Migration\Console\MigrateDataCommand\Interceptor->Magento\Framework\Interception{closure}() #10 [...]/magento2/generated/code/Migration/Console/MigrateDataCommand/Interceptor.php(77): Migration\Console\MigrateDataCommand\Interceptor->___callPlugins() #11 [...]/magento2/vendor/symfony/console/Application.php(1009): Migration\Console\MigrateDataCommand\Interceptor->run() #12 [...]/magento2/vendor/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand() #13 [...]/magento2/vendor/magento/framework/Console/Cli.php(116): Symfony\Component\Console\Application->doRun() #14 [...]/magento2/vendor/symfony/console/Application.php(149): Magento\Framework\Console\Cli->doRun() #15 [...]/magento2/bin/magento(23): Symfony\Component\Console\Application->run() #16 {main}

    Additional notes

    Tried to find information about this error on google without success. Hope, anyone can help me understanding this error and necessary steps to avoid it.

    opened by thomashellmann 2
  • Return value of Migration\ResourceModel\AbstractCollection::key() must be an instance of Migration\ResourceModel\mixed, int returned

    Return value of Migration\ResourceModel\AbstractCollection::key() must be an instance of Migration\ResourceModel\mixed, int returned

    Preconditions

    1. Magento 1.9.3.10 to Magento 2.4.5
    2. PHP 7.4 & MySQL 8.0.30 - Ubuntu 22.04.1
    3. FRESH Magento 2 install

    Steps to reproduce

    1. Run - composer require magento/data-migration-tool:~2.4.5
    2. Create and configure a Migration module in app/code/Vendor/Migration following steps in official docs
    3. Check data integrity and add ignores for tables and fields that are flagged as problematic i.e. 3rd party extensions
    4. Run - php bin/magento migrate:settings --reset app/code/Vendor/Migration/etc/opensource-to-opensource/1.9.3.10/config.xml

    Expected result

    [2022-09-08T11:15:47.605990+00:00][INFO][mode: settings][stage: integrity check][step: Settings Step]: started 100% [============================] Remaining Time: < 1 sec [2022-09-08T11:15:47.632163+00:00][INFO][mode: settings][stage: integrity check][step: Stores Step]: started 100% [============================] Remaining Time: < 1 sec [2022-09-08T11:15:47.652288+00:00][INFO][mode: settings][stage: data migration][step: Settings Step]: started 100% [============================] Remaining Time: < 1 sec [2022-09-08T11:15:49.870886+00:00][INFO][mode: settings][stage: data migration][step: Stores Step]: started 100% [>---------------------------] Remaining Time: < 1 sec

    Actual result

    [2022-09-08T11:15:47.605990+00:00][INFO][mode: settings][stage: integrity check][step: Settings Step]: started 100% [============================] Remaining Time: < 1 sec [2022-09-08T11:15:47.632163+00:00][INFO][mode: settings][stage: integrity check][step: Stores Step]: started 100% [============================] Remaining Time: < 1 sec [2022-09-08T11:15:47.652288+00:00][INFO][mode: settings][stage: data migration][step: Settings Step]: started 100% [============================] Remaining Time: < 1 sec [2022-09-08T11:15:49.870886+00:00][INFO][mode: settings][stage: data migration][step: Stores Step]: started 0% [>---------------------------] Remaining Time: < 1 secReturn value of Migration\ResourceModel\AbstractCollection::key() must be an instance of Migration\ResourceModel\mixed, int returned#0 /var/www/html/magento2/vendor/magento/data-migration-tool/src/Migration/ResourceModel/AbstractCollection.php(69): Migration\ResourceModel\AbstractCollection->key() #1 /var/www/html/magento2/vendor/magento/data-migration-tool/src/Migration/ResourceModel/Destination.php(38): Migration\ResourceModel\AbstractCollection->valid() #2 /var/www/html/magento2/vendor/magento/data-migration-tool/src/Migration/Step/Stores/Data.php(118): Migration\ResourceModel\Destination->saveRecords() #3 /var/www/html/magento2/vendor/magento/data-migration-tool/src/Migration/Mode/AbstractMode.php(82): Migration\Step\Stores\Data->perform() #4 /var/www/html/magento2/vendor/magento/data-migration-tool/src/Migration/Mode/Settings.php(100): Migration\Mode\AbstractMode->runStage() #5 /var/www/html/magento2/vendor/magento/data-migration-tool/src/Migration/Mode/Settings.php(58): Migration\Mode\Settings->runData() #6 /var/www/html/magento2/vendor/magento/data-migration-tool/src/Migration/Console/MigrateSettingsCommand.php(59): Migration\Mode\Settings->run() #7 /var/www/html/magento2/vendor/symfony/console/Command/Command.php(255): Migration\Console\MigrateSettingsCommand->execute() #8 /var/www/html/magento2/vendor/magento/framework/Interception/Interceptor.php(58): Symfony\Component\Console\Command\Command->run() #9 /var/www/html/magento2/vendor/magento/framework/Interception/Interceptor.php(138): Migration\Console\MigrateSettingsCommand\Interceptor->___callParent() #10 /var/www/html/magento2/vendor/magento/framework/Interception/Interceptor.php(153): Migration\Console\MigrateSettingsCommand\Interceptor->Magento\Framework\Interception{closure}() #11 /var/www/html/magento2/generated/code/Migration/Console/MigrateSettingsCommand/Interceptor.php(77): Migration\Console\MigrateSettingsCommand\Interceptor->___callPlugins() #12 /var/www/html/magento2/vendor/symfony/console/Application.php(1009): Migration\Console\MigrateSettingsCommand\Interceptor->run() #13 /var/www/html/magento2/vendor/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand() #14 /var/www/html/magento2/vendor/magento/framework/Console/Cli.php(116): Symfony\Component\Console\Application->doRun() #15 /var/www/html/magento2/vendor/symfony/console/Application.php(149): Magento\Framework\Console\Cli->doRun() #16 /var/www/html/magento2/bin/magento(23): Symfony\Component\Console\Application->run() #17 {main}

    Additional notes

    The error: Return value of Migration\ResourceModel\AbstractCollection::key() must be an instance of Migration\ResourceModel\mixed, int returned

    I have not been able to find anything related to this error. Is there a compatibility issue with 2.4.5?

    Please advise.

    opened by rickg123 7
  • Deprecated Functionality: preg_replace()

    Deprecated Functionality: preg_replace()

    Preconditions

    1. From Magento 1.9.0.1
    2. To Magento 2.4.4
    3. PHP 8.1

    Steps to reproduce

    1. bin/magento migrate:data vendor/magento/data-migration-tool/etc/opensource-to-opensource/1.9.0.1/config.xml.dist -a

    Expected result

    1. Successful migration

    Actual result

    [2022-08-04T08:44:12.308463+00:00][INFO][mode: data][stage: data migration][step: Map Step]: started 0% [>---------------------------] Remaining Time: < 1 sec In ErrorHandler.php line 61:

    Deprecated Functionality: preg_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /var/www/html/vendor/magento/data-migration-tool/src/Migration/Handler/TruncateSuffix.
    php on line 93

    Additional notes

    opened by Andreabont 2
Releases(2.4.5)
Run patches migration style in your Laravel applications.

This package generates patch files in the same fashion Laravel generates migrations. Each file is timestamped with an up and a down method and is asso

Anthony Rappa 44 Sep 9, 2022
PHP 7 Migration Assistant Report (MAR)

Introduction What is PHP 7 Migration Assistant Report(MAR)? PHP 7 MAR, or just "php7mar", is a command line utility to generate reports on existing PH

Alexia E. Smith 790 Dec 8, 2022
NYC Checkbook - Drupal 9 migration

Checkbook NYC Checkbook NYC is an open source financial transparency web application. Checkbook provides transparent access to a city's or other juris

Office of the Comptroller, City of New York 1 Jan 14, 2022
Validate PHP database migration files for compliance with best practices. Ensure db migrations are irreversible.

PHP DB Migration Validator Introduction In modern PHP frameworks such as Symfony and Laravel, migrations usually have up and down methods. In up metho

Anton Komarev 17 Dec 14, 2022
Make Laravel Pivot Tables using the new Laravel 9 closure migration format

This will allow you to create pivot table migration files using the new Laravel 9 closure migration format by simply passing two models.

Jose Jimenez 16 Aug 23, 2022
Collection of the Laravel/Eloquent Model classes that allows you to get data directly from a Magento 2 database.

Laragento LAravel MAgento Micro services Magento 2 has legacy code based on abandoned Zend Framework 1 with really ugly ORM on top of outdated Zend_DB

Egor Shitikov 87 Nov 26, 2022
Convenient tool for speeding up the intern/officer review process.

icpc-app-screen Convenient tool for speeding up the intern/officer applicant review process. Eliminates the pain from reading application responses of

null 1 Oct 30, 2021
Thunder is an advanced Laravel tool to track user consumption using Cashier's Metered Billing for Stripe. ⚡

⚡ Thunder Thunder is an advanced Laravel tool to track user consumption using Cashier's Metered Billing for Stripe. ⚡ ?? Supporting If you are using o

Renoki Co. 10 Nov 21, 2022
A tool to import Nordigen connected banks Firefly III

Firefly III Nordigen importer A tool to import Nordigen connected banks Firefly III Explore the docs » View Firefly III demo · Report Bug · Request Fe

Firefly III 12 Dec 9, 2021
Blacksmith is a code generation tool which automates the creation of common files that you'd typically create for each entity in your application.

Blacksmith is a code generation tool which automates the creation of common files that you'd typically create for each entity in your application.

Indatus 197 Dec 30, 2022
Laracademy Generators - is a tool set that helps speed up the development process of a Laravel application.

Laracademy Generators Laracademy Generators - is a tool set that helps speed up the development process of a Laravel application. Author(s): Laracadem

Laracademy 320 Dec 24, 2022
A code generation tool for Laravel developers.

Blueprint is an open-source tool for rapidly generating multiple Laravel components from a single, human readable definition. Watch a quick demo of Bl

Laravel Shift 2.4k Jan 5, 2023
Tool Berbasis Web Untuk membuat Laporan Praktik Kerja Lapangan Version 1.0

PKL-AUTO Tool Berbasis Web Untuk membuat Laporan Praktik Kerja Lapangan Version 1.0 Features : Online/Offline Mode Laporan langsung aja Tinggal Select

Ivan Dwi Yanto 1 Nov 26, 2021
Tool to convert from composer.yml to composer.json.

composer-yaml This project allows you to convert a composer.yml file into composer.json format. It will use those exact filenames of your current work

Igor 56 Sep 28, 2022
GitScrum is a Project Management Tool, developed to help entrepreneurs, freelancers, managers, and teams Skyrocket their Productivity with the Agile methodology and Gamification.

What is GitScrum? GitScrum is a Project Management Tool, developed to help entrepreneurs, freelancers, managers, and teams Skyrocket their Productivit

GitScrum 2.8k Dec 29, 2022
An issue tracking tool based on laravel+reactjs for small and medium-sized enterprises, open-source and free, similar to Jira.

ActionView English | 中文 An issue tracking tool based on php laravel-framework in back-end and reactjs+redux in front-end, it's similar to Jira. You co

null 1.7k Dec 23, 2022
Nebula is a minimalistic and easy to use administration tool for Laravel applications, made with Laravel, Alpine.js, and Tailwind CSS.

Nebula Nebula is a minimalistic and easy to use administration tool for Laravel applications, made with Laravel, Alpine.js, and Tailwind CSS. Nebula m

Nebula 228 Nov 11, 2022
Email-flooder - A CLI flooder e-mail tool, made in PHP.

E-mail flooder (PHP 8.0.13) You can send emails to any server, however the request must come from Gmail. (Remember to enable less secure apps to be ab

null 2 Dec 17, 2021
Hashtopolis is a multi-platform client-server tool for distributing hashcat tasks to multiple computers.

Hashtopolis is a multi-platform client-server tool for distributing hashcat tasks to multiple computers. The main goals for Hashtopolis's development are portability, robustness, multi-user support, and multiple groups management.

Hashtopolis 1.1k Jan 4, 2023