Magento CSV Import/Export: Products, Customers, and Advanced Pricing

Magento’s Catalog Language Is CSV

Adobe Commerce / Magento 2 merchants in the US, UK, Australia, Canada, and Europe still lean on CSV import/export for catalog updates, customer loads, and advanced pricing. The importer is powerful and unforgiving: wrong sku, store_view_code, or additional_attributes encoding creates partial imports and haunted storefronts.

Which Magento CSV Entity?

Use the entity type Magento expects.

Step-by-Step: Product Import

Safest bulk path.

• In Admin: System → Import (wording varies by version) → Products.
• Download the sample CSV for your Magento version.
• Export existing products if you are updating — better than inventing rows.
• Edit in Online CSV Editor; keep sku as text.
• Set attribute_set_code, product_type, and website/store columns correctly.
• Save UTF-8 CSV (BOM quirks: follow Magento’s guidance for your version).
• Run Check Data before Import.
• Review the import log; fix failed SKUs only; reindex/cache as required.

sku,attribute_set_code,product_type,name,price,status,visibility,qty
MUG-BLU-01,Default,simple,Blue Stoneware Mug,28.00,1,4,40

Store Views, Websites, and Locales

Multi-store EU/UK/US catalogs break here.

• store_view_code rows update locale-specific attributes (name/description).
• Do not assume a UK store view shares US attribute values automatically.
• website_id / product_websites columns control where products appear.
• Currency display is store config — CSV prices still need correct scope.
• UTF-8 for DE/FR descriptions with umlauts and accents.

Configurable Products and Variants

Complex types need extra rows/relationships.

• Simple children usually need their own SKUs and attribute values.
• Configurable parents reference children via Magento’s documented columns.
• Import children before (or as documented with) parents depending on version guidance.
• Never collapse variants into a single Shopify-style row and hope.

Customers CSV

Email is the key.

• Deduplicate emails before import.
• Addresses may be separate rows/entities depending on template.
• Customer group codes must exist.
• Passwords: follow Magento’s import rules — often hashed or invite-based flows are safer than raw password columns.
• Phones/postcodes as text.

Excel Landmines

Magento admins lose days here.

• SKU leading zeros stripped.
• Long IDs in scientific notation.
• Semicolon CSV from European Excel — convert to Magento’s expected delimiter.
• Broken quoting on description HTML.
• Saving as wrong encoding so additional_attributes parse fails.

Magento vs Shopify / BigCommerce CSV

Do not cross-upload.

• Maintain a PIM/master sheet; generate Magento-specific CSV.
• attribute_set and store view concepts are Magento-specific.
• See Shopify, BigCommerce, and WooCommerce guides for other channel formats.

Common Mistakes

Catalog incidents.

• Skipping Check Data.
• Updating the wrong store view and overwriting default locale copy.
• Mixing add and update behaviors without reading import behavior settings.
• Importing images paths that do not exist on the server.
• Re-importing entire catalog after 12 SKU errors.

Best Practices

Treat imports like deployments.

• Staging first.
• Pilot a handful of SKUs.
• Version every import file + log.
• Change one concern per file when possible (price XOR qty XOR copy).
• Edit CSV outside Excel when SKUs keep breaking.

Why Use Convert CSV Online?

Convert CSV Online is free, browser-based, and requires no account for everyday conversions. Protect Magento SKUs in the Online CSV Editor, fix EU delimiters, and convert to Excel for merchandising reviews across US, UK, AU, CA, and EU stores.

Conclusion

Magento CSV imports succeed with sample-accurate headers, correct store/website scope, and UTF-8 discipline. Export, edit carefully, Check Data, pilot, then scale — especially on multi-store international catalogs.