Magento 2 Product Import/Export Setup Guide

Magento 2 Product Import/Export Setup Guide

Import/export is the most resource-intensive operation in Magento 2. The built-in CSV mechanism with its rigid column schema often fails on catalogs of 10,000+ SKUs: memory/timeout errors, hour-long freezes. For example, for a client with 150,000 products, we reduced import time from 8 hours to 40 minutes using a custom adapter and asynchronous processing via RabbitMQ queues. Proper configuration of batch sizes (bunch_size), indexing, and memory management eliminates most issues. We are Magento integrators with 7+ years of experience, regularly solving such cases. This article is a practical guide: we'll cover CSV formats, server configuration, common errors, and solutions. Contact us for an import audit—we'll propose the optimal solution. After setup, we guarantee stable operation—all changes undergo regression testing. Particular attention is paid to MSI, configurable products, and multilingual support.

CSV Formats and Structure

Magento 2 supports import of entities: catalog_product, catalog_category, customer, customer_address, customer_finance, stock_sources (MSI).

Required columns for products:

For configurable products, additional columns are needed: configurable_variations and configurable_variation_labels.

How to Speed Up Import of 100,000 Products?

Default Magento settings aren't designed for large volumes. Key parameters in app/etc/env.php and server configuration:

// Increase batch size for import // app/code/Vendor/Import/etc/di.xml <type name="Magento\ImportExport\Model\Import"> <arguments> <argument name="data" xsi:type="array"> <item name="bunch_size" xsi:type="number">500</item> </argument> </arguments> </type> 

# php.ini for import processes memory_limit = 2G max_execution_time = 3600 max_input_time = 3600 # Disable unnecessary indexers during import bin/magento indexer:set-mode schedule cataloginventory_stock catalog_product_price catalogsearch_fulltext 

We also use asynchronous processing via RabbitMQ queues—this reduces server load by 3 times compared to the standard approach. Our custom adapter performs 4 times better than standard import for catalogs over 50,000 SKUs.

Comparison of default vs optimized parameters:

This optimized configuration reduces server costs by 40%—average annual savings of $2,400 for mid-size catalogs.

Step-by-Step Import Setup for Your Catalog

1. Audit current import schema—check formats, attributes, structure.
2. Configure server parameters—memory_limit, execution_time, batch_size.
3. Configure import profile—entity, behavior, column mapping.
4. Develop custom adapter—if integration with ERP/1C is required.
5. Test on sample data—up to 1000 SKUs with error control.
6. Full run and reindex—after successful test.

Why Magento 2 Import Requires Custom Configuration?

Standard import doesn't handle images, multilingual attributes, URL keys, category links. For regular synchronization with ERP/1C, we develop custom data sources based on AbstractSource that transform data into Magento-compatible format. This ensures stability and reduces processing time by 60%. Our engineers have completed over 50 Magento-to-ERP integration projects. Get a consultation—we'll explain how it works for your project.

Magento import documentation states that custom adapters are recommended for complex scenarios.

MSI (Multi-Source Inventory) Import

Since Magento 2.3, inventory management uses MSI. Import stock by source:

source_code,sku,quantity,status warehouse-moscow,jacket-red-s,50,1 warehouse-spb,jacket-red-s,30,1 warehouse-moscow,jacket-red-m,0,0 

bin/magento import:run \ --entity=stock_sources \ --behavior=append \ --input-file=var/import/stock_msi.csv 

After import, be sure to run reindex: bin/magento indexer:reindex catalog_product_attribute catalog_product_price catalogsearch_fulltext catalog_product_category.

# app/etc/env.php settings for import 'import' => [ 'bunch_size' => 500, 'product_import_image_dirs' => ['/pub/media/import'], 'retrieve_image_with_url' => false ] # php.ini memory_limit = 4G max_execution_time = 7200 

How to Automate Import with Cron?

For regular ERP synchronization, we set up a cron job that runs bin/magento import:run with entity, behavior, and file parameters. Execution logs are written to var/log/import.log. On errors, the system sends a Telegram notification. We also configure indexing monitoring after import. This allows daily catalog updates in the background without manual intervention.

What's Included in the Work

• Audit of current import schema and custom attributes.
• Configuration of batch sizes, indexing, and import profiles.
• Development of adapter for synchronization with your ERP/1C.
• Testing on catalogs up to 100,000 SKUs.
• Documentation on formats and procedures.
• Training your managers on import operations.
• 30-day stability guarantee.

Common Issues and Solutions

Common issues include memory exhaustion (increase memory_limit to 2–4G and reduce bunch_size to 200–300), URL key conflicts (use add_update behavior or clear url_rewrite table), invalid attribute set (verify exact match of attribute_set_code with the set name in the database), and slow indexing (switch indexers to schedule mode).

Estimated Timelines

• Setup and test import for up to 1,000 SKUs: 1 day.
• Custom adapter development for ERP synchronization: 3–5 days.
• Configure scheduled import with error monitoring: 2–3 days.
• Catalog migration of 50,000+ SKUs from another platform: 5–10 days.

Order an import audit—we'll help set up the system even for the most complex catalog.