Explore a free version of the import and export solution for Magento 2. Install together with the Export Core and Import Core to see the interface and full scope of data transfer features. This package has the same code and architecture as the original paid Import and Export for Magento 2 extension but includes core functionality only suitable for manual data transfer. See the full scope of automatization features and entities available in the paid version in this demo or book a live demo with the Amasty team to get a consultation in real-time.
The paid version is available in Lite, Pro and Premium packages. Visit our webstore to choose the pricing plan. A free package is the Lite version of the full Import and Export for Magento 2 extension, but without ready-made entities for migration.
Import & Export Core is a universal tool for data migration to or from Magento 2. The solution has a unique architecture and code structure without any intersections with the native import/export functionality developed by Magento. Even though a free package does not include any ready-made entities for migration, you can create compatibility with any entity you need. Import and Export Core is highly flexible and adaptive to any data presented in Magento and 3rd-party resources so that you could build integrations with the most complicated systems.
With the help of this package you can:
To install the package, run the following commands:
composer require amasty/module-import-export-corephp bin/magento setup:upgradephp bin/magento setup:di:compile php bin/magento setup:static-content:deploy (your locale)See more details in the Composer User Guide.
To run data migration, you need to create the required entity or entities (e.g. products, orders, customers) first. Let’s see how it works in the free version of the Magento 2 Order Import and Export module.
Open the Export tab. Here you can choose the entity to export. As an example, we will export order items.
When the required entity is chosen, you can start Magento 2 export configuration.
It is possible to export files from Magento in an XML or CSV format.
If you choose a CSV file, you can also add:
In other words, make your file structure suitable for the platform you are migrating data to.
Provide the title of the file. Keep in mind that you can set a regular expression to fill in the date automatically.
 _(README truncated for .md surface. Full README on https://packagento.com/amasty/module-import-export-core.)_ ## Recent Versions | Version | Released | |---|---| | 1.4.2 | 2025-11-10 | | 1.4.0 | 2025-02-03 | | 1.3.0 | 2024-02-26 | | 1.2.1 | 2023-08-28 | | 1.2.0 | 2023-08-11 | | 1.1.4 | 2022-09-29 | | 1.1.3 | 2022-07-05 | | 1.1.2 | 2022-05-20 | | 1.1.1 | 2022-03-02 | ## Dependencies ### Require | Package | Constraint | |---|---| | php | >=7.3 | ## Quality Latest release (1.4.2) fails the Packagento QA pipeline. Verdicts below are per-cell (Magento line × PHP version) for the matrixed tools, and run-once for the static / security tiers. ### Compatibility Each Magento line is installed on its supported PHP versions, then the module is built (DI compile + static-content deploy). Cells show passed / failed / untested; staircase gaps render as `–`. | Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 | |---|---|---|---|---| | 2.4.7 | Pass | Pass | – | – | | 2.4.8 | – | Pass | Pass | – | | 2.4.9 | – | – | Pass | Pass | ### Code Quality Advisory checks against the module's source. Never affect the Compatibility verdict — a phpcs finding can't make a module incompatible. #### Static Analysis Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module. | Tool | Status | Findings | Summary | |---|---|---|---| | PHPCS | Pass | 0 | | | PHPMD | Warning | 16 | 16 rule violations (MissingImport:12, ExcessiveMethodLength:2, UnusedFormalParameter:1, CountInLoopExpression:1) | | Cpd | Pass | 0 | | | Composer validate | Info | 1 | valid; 1 advisory note (composer validate --strict) | #### PHPStan Type-checks the module against a real Magento install. Re-runs per Magento + PHP version because resolvable symbols differ between releases. | Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 | |---|---|---|---|---| | 2.4.7 | 9 | 9 | – | – | | 2.4.8 | – | 9 | 9 | – | | 2.4.9 | – | – | 9 | 9 | ### Tests Unit and integration suites run per Magento + PHP cell. Test failures speak to the module's behaviour, not its compatibility with a line, so they're reported here separately. #### Unit Tests | Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 | |---|---|---|---|---| | 2.4.7 | N/A | N/A | – | – | | 2.4.8 | – | N/A | N/A | – | | 2.4.9 | – | – | N/A | N/A | #### Integration Tests | Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 | |---|---|---|---|---| | 2.4.7 | N/A | N/A | – | – | | 2.4.8 | – | N/A | N/A | – | | 2.4.9 | – | – | N/A | N/A | ### Security Dependency-advisory audit (composer audit) plus a source malware scan. A malware detection fails the version outright. | Tool | Status | Findings | Summary | |---|---|---|---| | Composer audit | Pass | 0 | | | Malware scan | Pass | 0 | | ## Licence and pricing Free. A licence is still minted on checkout and bound to your project for Composer access — no payment step. Refundable within 14 days of first purchase via https://packagento.com/account/refunds/. ## Install via Claude Code or any MCP client The Packagento MCP server can run the licence + project + Composer steps above in one tool call: ``` purchase_and_install_packages( composer_names=["amasty/module-import-export-core"], project_id="proj_xxx" ) ``` This handles cart, checkout, licence minting, project activation, and writes auth.json credentials. Connect a client with `claude mcp add packagento https://mcp.packagento.com`. Full setup at https://packagento.com/docs/mcp-setup. ## Vendor amasty is a Magento 2 vendor on Packagento. See https://packagento.com/amasty.md for their full catalogue.