
A Shopify product CSV does not contain the actual associated image files. It records product data and image references. If you plan to close the old store or delete its listings, preserve access to those images until the new store finishes importing them, and keep an appropriate independent media archive.
Key Takeaways
- A CSV export is not a self-contained product-photo package.
- The destination needs reachable source images during import.
- Verify the new media before retiring its old source.
Identify the dependency before closing the store
Shopify's product export guide explicitly says images are not included in the CSV. It instructs merchants moving stores to import while the old store and product listings remain viewable. The destination's image creation depends on public accessibility of those sources.
Downloading the spreadsheet is therefore only one part of migration preparation. A folder containing a CSV but no accessible source media cannot be assumed to restore every image later.
The catalog-versus-originals backup guide describes a similar distinction for photo editing, but its Lightroom backup controls do not operate on Shopify. Here the crucial dependency is the importer's access to image URLs.
Preserve the product-to-image relationship
Keep a dated export and an asset inventory associated with the actual product identifiers. Preserve approved image originals through your authorized backup process, and verify the files can be opened independently. Do not infer that screenshots of product pages replace the source images.
Use the SKU mapping guide to keep similar colors or revisions distinct. An archive of correct images still needs its association with the correct product.
Shopify also warns that sorting a product CSV in a spreadsheet can disassociate variant or image rows and lead to bad overwrites on import. Preserve the original export and understand the row structure before making bulk changes. A neat-looking alphabetical sheet is not automatically a valid migration file.
Migrate in an order that preserves access
For a proposed store move, use this acceptance plan:
- Export the intended product set and retain the unchanged file.
- Inventory expected images and preserve required originals separately.
- Keep the source store and listings accessible during the destination import.
- Inspect the destination's attached media against the inventory.
- Check representative buyer-facing galleries and the variants that need distinct photos.
- Retire the old source only after the required destination media have been verified.
These steps are proposed checks, not a claim that any migration has been completed. A successful product-record import does not establish complete image transfer.
Handle missing sources without guessing
If a source URL no longer works, locate the approved original in authorized storage and arrange the correct destination mapping. Do not invent alternate CDN paths or assume a missing public object can be recovered by changing a string in its address.
If sources remain accessible but some images are absent, inspect the affected rows and actual destination media rather than repeating the entire migration blindly. Keep unresolved products visible in the inventory.
Connect the final exported files and destination records through the approved-version handoff. Accept the media migration when the intended images exist in the destination and display with the correct products. The presence of a CSV on your computer is evidence of an export, not proof of a recoverable image archive.
Related tasks
- Does a Lightroom Classic Catalog Backup Include My Original Photos?
- How Do I Keep AI Product Images Matched to the Correct SKU?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- Shopify: Exporting products: Associated image files are not included in a product CSV. A new store must access publicly available images during import, so the source store and products should remain intact until import finishes. Sorting CSV rows can disassociate variants and image URLs.
Based on the complete official export source captured October 29, 2026. No store, CSV, backup, import or image recovery was tested. The migration sequence is proposed. Public community questions informed the topic but are not factual authorities, and no deleted-asset recovery technique is promised.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.