How to import products in bulk when moving an ecommerce store

The difficult part of a bulk ecommerce product import is not uploading the file. It is making sure that the source platform fields still mean the same thing in the new store. A title and main image can look correct while a broken SKU, variant combination, weight, or stock value waits until an ad launches or the first order arrives.

Start with a test batch of 10 to 20 products. Include a single-variant product, a product with several options, variants that share an image, an unavailable SKU, a barcode, and one product with a long description. Run this batch through export, preview, import, product page review, and a test order before moving the full catalog. A small batch makes the source of a mapping error visible.

Define what the import will and will not move

A product migration usually includes core product information, variants and SKUs, prices, stock, and images. Orders, customers, reviews, collection membership, URLs, market translations, and redirects are separate data sets. A successful product import does not establish that any of those records moved. Write down the source, destination, and owner for every part of the migration.

Shopify's CSV import guide positions CSV import for switching platforms or changing many products. It recommends a small test for large migrations and tells merchants to back up product data. Shoplazza's Shopify import guide provides a dedicated Shopify CSV path and explains publication and overwrite choices on that platform. SHOPLINE's bulk product guide asks merchants to prepare names, variants, prices, barcodes, and SKUs in its template. Their fields and overwrite behavior differ, so a file should not move between systems without a mapping review.

Keep the original export unchanged. Clean a copy. Sorting, deleting columns, or changing encoding in the only backup makes it harder to tell whether an image or variant problem began during export, spreadsheet editing, or import.

Know the current ShopingX import boundary

ShopingX currently accepts Shopify product CSV files and Amazon Listings TSV or TXT files. The import form asks for the source and destination store, with an optional product category. One file can be up to 10 MB and can contain at most 200 products and 800 SKUs or variants. Split a larger migration by complete products so that the rows for one product do not land in different batches.

For Shopify CSV, the importer groups rows by Handle or title. It reads the title, body, tags, product type, up to three option groups, SKU, barcode, price, compare-at price, cost, stock, weight, and image URLs. For Amazon Listings, the current parser treats each row as one single-variant product and reads basic fields such as item name, Seller SKU or ASIN, description, main image, price, quantity, and barcode. It does not infer a complex option structure from several Amazon rows.

The import creates new products. It is not an overwrite workflow. ShopingX checks duplicate SKUs and product numbers within the file and against the merchant's existing catalog. Successful products are created as drafts and remain off sale. Current behavior does not establish migration of orders, customers, reviews, collections, old URL redirects, market translations, or a Merchant Center feed.

Clean six field groups before uploading

Start with product identity. Keep every SKU stable and unique, and make sure that the rows for one product share the intended Handle. A source product without a SKU can reach the preview, but it becomes difficult to reconcile with a warehouse, an advertising feed, or a later stock update. Assign a durable identifier before migration when possible.

Review names, main image URLs, prices, stock, options, and option values. A valid product needs a name and main image. Price and stock cannot be negative. Images must use publicly reachable HTTP or HTTPS URLs. A private network address, a signed link that expires, or a URL that requires a login is not a dependable migration source. ShopingX downloads the images during commit, so do not close the source image host before the batch finishes.

Normalize weights. The Shopify mapping converts grams, kilograms, pounds, and ounces into kilograms, but sample the result, especially for small parcels. Treat price as a numeric source value, not as a finished market price. Taxes, currency presentation, and destination-market pricing still need a separate review.

Descriptions may contain HTML. Check links, embedded images, tables, and inline styles. Remove links to an old admin area, expired campaign pages, and assets you no longer have permission to use. Rebuild navigation using the product categories and collections guide instead of treating every source tag as a storefront category.

Use preview as a release gate

Open the import tool from the ShopingX product list. Choose the source, store, and file, then run Parse Preview. The preview reports product and variant counts, valid products, invalid products, and products with warnings. Each row shows the name, source key, SKU count, price, stock, and its first error or warning.

Missing names, missing or invalid main image URLs, negative prices or stock, duplicate identifiers inside the file, and conflicts with existing SKUs or product numbers produce errors. The current admin does not enable commit while any preview row is invalid. Correct the source file and preview it again. Adding a date suffix to a conflicting SKU only to pass validation creates a second identity that the warehouse and ad feed must somehow understand.

Warnings also need review. If a source product has no SKU, the importer tries to use a source identifier. Gallery images beyond 20 are skipped. During commit, a failed main image download fails that product. Failed gallery or variant image downloads are recorded as warnings. Keep the cleaned source file and import job ID so that each result can be traced to a row.

Review drafts before publishing anything

After commit, inspect the first product, the last product, and the product with the most variants. Compare the title, main and gallery image order, price, compare-at price, total stock, option combinations, SKUs, barcodes, weights, and description. Use the ecommerce product page checklist for the storefront review. If the same mapping is wrong across several products, fix the source and repeat a small batch instead of manually editing dozens of records.

Imported products remain drafts and off sale. Use that state to add translations, storefront categories, collections, shipping templates, SEO titles, and descriptions. Publish two test products first. Open each production product page, select every option, add the item to the cart, and confirm that its price and stock continue into checkout.

Google Merchant Center's product data specification requires submitted price and availability to match the landing page, checkout, and structured data. This is a useful acceptance rule even when Shopping ads are not part of the launch. One SKU should not have four different states across the admin, product page, structured data, and checkout.

Pass one batch before scheduling the next

Keep the original export and cleaned file. Record the product count, SKU count, errors, warnings, created products, and failures. Then verify that multi-variant products stayed intact, images have durable sources, price and stock agree, important old product URLs have a redirect plan, and every test product is reachable from the new store navigation.

The batch passes when errors stop at preview, successful products enter the right store as drafts, every SKU can be checked on the product page and at checkout, the old catalog remains available for comparison, and every data set outside the product import has an owner. Review the ShopingX quick start guide, then create a merchant account for the test batch. After the catalog passes, use the store launch test to validate the complete purchase path.