Where is it going?
How to export from Magento
- In the Magento Admin, go to System, then Data Transfer, then Export.
- Set Entity Type to Products and Export File Format to CSV, then click Continue at the bottom of the page.
- Magento builds the file in the background through its message queue (cron must be running) and shows a message when it is done. The file is saved in the var/export folder of your Magento install.
- Only Magento 2 exports are read. A Magento 1 export (columns such as _store and _type) is refused with a message.
- Note your store's weight unit (Stores, Configuration, General, Locale Options). The file does not include it, so this page asks you before you download.
What to know about Magento files
- Simple, virtual and configurable products are converted. Virtual products become products without shipping. Bundle, grouped, downloadable and gift card products are not converted; they are named and counted.
- A configurable product becomes one product with its child products as variants, linked by sku through configurable_variations, wherever the child rows sit in the file. Option names come from configurable_variation_labels, or from the attribute code (color becomes Color) when there is no label.
- Rows with a store_view_code repeat a product for one store view (translations, store prices). They never become extra products: each product is converted once from its default row, and the skipped rows are counted.
- A special price lower than the price becomes the sale price, with the price as the compare-at price. If special_price_from_date or special_price_to_date put today outside the sale window, the regular price is used and you are told. The import file has no end date, so a running sale with an end date is listed so you can end it. Magento writes dates in the admin's language, so the day and month order is decided once for the whole file from dates that can only be read one way (such as 23/06/26 or 6/23/26). If the file has no such date, or has both kinds, a sale whose dates depend on the order is left out, the regular price is used, and a warning names those products so you can set the sale in the new store.
- Magento exports image paths relative to its media folder (such as /m/b/photo.jpg), not web links. The new store cannot download them, so images are left out and the products are listed. Full web links in the file are kept.
- Stock: qty becomes the stock count when stock is managed. A product marked out of stock (is_in_stock 0) is written as tracked with stock 0, even when qty is blank, so it cannot be bought; a fraction is rounded toward zero. Both are listed.
- Disabled products (product_online 2) and products that are Not Visible Individually and not part of a configurable product become drafts. A disabled child of a configurable product is left out of it and named; if every child is disabled, the product is kept as a draft. A child that is also sold on its own moves only as a variant; its own page and URL do not move.
- Categories: the first level of each path is the root category (such as Default Category) and is dropped, so Default Category/Gear/Bags becomes Gear > Bags.
- Not carried over, and listed when present: custom options, related, up-sell and cross-sell links, extra attributes in additional_attributes, short descriptions and meta keywords. Tier prices are in a separate Magento export, not in the Products export, and stock per source (multi-source inventory) is not in this file, so they do not move.
- Weights have no unit in the file, so the page asks for your Magento weight unit and does not offer the download until you choose one. Until then, weights are read as pounds, which is what Magento uses by default.
- Built from Magento's export and import source code, its sample file and real exports published on GitHub. It was not tested by importing into a live store.
Only products move. Customers, orders, reviews, gift card balances, blog posts, pages and URL redirects are not in a product export, so CatalogHop does not convert them.