At a glance
- 1. Start from a clean sheetPut every product in one spreadsheet, one row per variant, with the same columns throughout: handle or parent SKU, title, description, price, SKU, barcode, option names and values, weight, stock and image URLs.
- 2. Map to the platform's formatShopify imports a CSV with one row per variant sharing a Handle, and extra rows for more images.
- 3. Test with a small batchImport ten products, including the hardest ones: many variants, several images, long descriptions.
- 4. Run the full import and check itImport the rest in batches and compare counts with the source file.
- 5. Keep it in syncFor supplier files that change every week, a scheduled job can read the file, update prices and stock by SKU and flag new or discontinued products, using the Shopify Admin API or the WooCommerce REST API instead of a man
- Moving from another platformWhen moving from Magento, BigCommerce, Wix or another store, export products, customers and orders separately, and plan redirects from the old URLs so search traffic follows the products.
1. Start from a clean sheet
Put every product in one spreadsheet, one row per variant, with the same columns throughout: handle or parent SKU, title, description, price, SKU, barcode, option names and values, weight, stock and image URLs.
- Every SKU unique, every variant tied to its parent
- Prices and weights as plain numbers, in one currency and unit
- Image URLs that open in a browser without a login
2. Map to the platform's format
Shopify imports a CSV with one row per variant sharing a Handle, and extra rows for more images. WooCommerce's importer uses a parent row for each variable product and a row for each variation, linked by the parent SKU. Map your columns to theirs once and keep the mapping.
3. Test with a small batch
Import ten products, including the hardest ones: many variants, several images, long descriptions. Check them on the storefront, in search and in your feeds before running the rest.
4. Run the full import and check it
Import the rest in batches and compare counts with the source file. Look for missing images, variants that became separate products and prices that lost decimals. Keep the file, so a second run updates products instead of duplicating them.
5. Keep it in sync
For supplier files that change every week, a scheduled job can read the file, update prices and stock by SKU and flag new or discontinued products, using the Shopify Admin API or the WooCommerce REST API instead of a manual CSV.
Moving from another platform
When moving from Magento, BigCommerce, Wix or another store, export products, customers and orders separately, and plan redirects from the old URLs so search traffic follows the products.
Updated 2026-10-26. General guidance, not advice for your situation; we scope each project in writing before any work starts.
Questions people ask first
How many products can I import at once?
Both platforms handle large files, but big imports are safer in batches of a few thousand rows, checked as you go.
Will it overwrite products that are already live?
Only if you choose to. Shopify can overwrite products with the same handle, and WooCommerce can update existing products by SKU or ID.
Can it bring the product photos across?
Yes, if the image URLs are public. The platform downloads each image during the import.
Can the import fill in missing descriptions or attributes?
Yes, as a step before import. Gaps are filled from the supplier file or written in, then reviewed before they go live.
Tell us what you need built.
Tell us the process and the tools involved, or call. We reply with questions or a written scope.
hello@pushbuild.com