Choose the right Shopify CSV import workflow
Start by identifying the resource: products, blog posts or another type of store data. Next, decide whether you are creating new records, updating existing records or exporting content for review. A file prepared for one workflow should not be treated as a universal store migration file.
| Workflow | What to check |
|---|---|
| Shopify native product CSV | Use Shopify’s current format. Its overwrite option matches existing product handles; blank included fields can replace existing values. Shopify documentation [1] |
| Nimvexa CSV Importer | Use the app’s supported product or blog fields. Its listing describes column mapping, a preview, product updates by SKU and import result reports. Published app features [4] |
If your product file already fits Shopify’s native workflow, that may cover your task. Consider the app when its supported mapping, reporting or blog workflow meets a specific need. Check the current sample and preview rather than assuming every field in an existing export will be accepted.
Prepare a CSV that is easy to inspect
Keep an untouched copy of the source file. Work on a second copy with a meaningful name, such as spring-catalog-review.csv. Add a short note outside the CSV describing the intended change, the records affected and who will check the result.
- Choose the correct template. Download the sample or make an export from the exact tool you will use. Avoid mixing a product template with an article template.
- Protect identifiers. Treat SKUs and other codes as text in your spreadsheet. Check that leading zeros, punctuation and long identifiers survive saving and reopening.
- Keep each field consistent. Check repeated columns for mixed formats, accidental spaces and unexpected empty cells.
- Save as UTF-8 CSV. Reopen the saved file and inspect accented characters, commas, quotes and multiline content. Shopify’s CSV editing guide explains file preparation. [2]
An empty value might mean “clear this field”, “leave it unchanged” or “invalid input”, depending on the importer and field. Verify the behavior using a disposable test record before updating existing content.
A practical checklist for importing products from CSV
Use a small, representative test before a large import. Include an ordinary new record, an intended update and a row containing the formatting that is most likely to cause trouble. Keep test data separate from customer-facing content wherever possible.
- Export the existing records you intend to change. Keep this reference separately from your edited file. Note which fields the export contains.
- Open the product workflow. For Shopify’s native importer, start in Products → Import. For Nimvexa CSV Importer, open the installed app and choose Products.
- Upload the correct file and inspect the mapping. Confirm that a source column represents the intended destination field. Similar names do not guarantee the same meaning.
- Read the preview as a reviewer. Check identifiers, titles, empty values and proposed changes. Do not judge the file only by its first row.
- Run the small test. Open the resulting records in Shopify and compare them against your source. Check both edited and deliberately unchanged content.
- Review results, then expand. In the app, inspect History and the available row-level report. Resolve errors before proceeding with more rows.
For Shopify’s native product import, follow the current instructions in the Shopify Help Center. Do not apply Shopify-native template rules to the app unless the app’s current mapping and preview confirm them.
Updating existing products by SKU: check the match first
Nimvexa CSV Importer’s published feature list includes updating existing items by SKU. Before using that workflow, compare the codes in the file with the intended items in Shopify. Review duplicate or missing SKUs rather than guessing which record should be updated.
Illustrative example: a spreadsheet contains TSHIRT-BLUE-M, but the intended record uses TSHIRT-BLUE-M-2026. A person may recognize the relationship, but the mismatch needs resolving before import. Likewise, a spreadsheet that turns 00123 into 123 can change the identifier you intended to use.
Include both a matching and a nonmatching example in your test. Inspect whether the result is the update you expected; do not assume the importer will infer a relationship or silently repair a code.
Import Shopify blog posts from CSV, then check the storefront
For article work, use the app’s Blog posts workflow and select an existing blog or create a new one. Start from its current sample or a supported export, map the available columns and review the preview before importing. The public feature set includes exporting blog posts as well. [4]
Prepare an editorial check alongside the data check. Open the resulting article in Shopify and on the storefront. Read the title and body, follow important links and inspect headings and formatting. If the source contains embedded media or image references, verify them individually rather than treating successful row processing as proof that every asset has moved.
A blog migration also has decisions outside the CSV: existing URLs, redirects, media ownership and the structure of the destination site. Plan those separately. This guide does not assume that the app automatically transfers every media file, preserves rankings or creates redirects.
Export products and blog posts with a clear purpose
An export is most useful when you know what you want to check next. Write down whether the file is for editing a selected group, reviewing descriptions or preparing a supported transfer. After downloading, inspect its headers and row coverage before relying on it.
For each resource, check which records and fields the selected export includes. If the interface exports a page or selection, account for the other records separately. A downloaded file is not evidence that the entire catalog or every article was included.
Keep separate plans for themes, media, orders, app settings and any other resources that are outside the exported fields. Shopify documents the scope and limitations of store duplication and backups. [3]
Common CSV import problems and what to check
| What you notice | First check | Next step |
|---|---|---|
| Accents or symbols look wrong | Encoding in the saved file | Compare the UTF-8 source, preview and resulting record. |
| Content appears in the wrong field | Column mapping and row alignment | Correct the mapping and retest a small sample. |
| An expected update did not happen | The identifier and matching rule | Check the target SKU for the app, or the handle and overwrite option for native import. |
| Only some rows succeeded | Row-level result report | Identify which records changed before retrying failed rows. |
| The CSV opens as one column | Delimiter in your spreadsheet import settings | Check the saved file against the selected importer’s format. |
| An article looks incomplete | Imported body, formatting and referenced assets | Inspect the source article and the destination page directly. |
Keep the file version and report from each attempt. Repeatedly importing a full file before checking the earlier result makes it harder to understand which change caused a problem.
NIMVEXA CSV IMPORTER
A CSV workflow for products and blog content
Review the app’s published capabilities, current pricing, trial terms and requested permissions on the Shopify App Store before installation.
View CSV Importer on ShopifyThe app is available in English. Check the current template for supported fields.
Frequently asked questions about Shopify CSV import and export
Can I import products into Shopify without an app?
Yes. Shopify includes a native product CSV import and export workflow. Follow its current template and matching rules. Nimvexa CSV Importer is an alternative for supported product and blog workflows with column mapping, previews and import reports.
Can Nimvexa CSV Importer import and export blog posts?
Yes. Its published features include importing articles into an existing or new Shopify blog and exporting blog posts to CSV. Use the app’s current sample or export as your starting point and inspect the resulting articles before importing a larger batch.
Does Shopify match products by SKU or by handle?
The native product CSV workflow uses matching handles when you enable overwriting. Nimvexa CSV Importer advertises updating existing products by SKU. These are different matching rules: verify which importer you are using and test the match before changing existing content.
Can I use the same CSV template for every importer?
Do not assume that you can. Shopify’s native importer and third-party apps can use different headers, supported fields and matching rules. Start with the sample file or export supplied by the tool you will actually use.
Why are accents or descriptions incorrect after import?
Check that the file is saved as UTF-8 and that commas, quotes and line breaks are correctly preserved. Compare one affected source cell with the import preview and the resulting Shopify record before retrying a larger file.
Does a CSV export back up my entire Shopify store?
No. A CSV contains the supported fields included in that export. It is not a complete backup of themes, media files, orders, app settings or every store resource. Review what is included and plan separate backups for anything else you need.
Can I undo an import automatically?
Do not assume there is a one-click undo. Export the relevant existing content first, test a small batch and inspect the reports. If something is wrong, stop and assess which records changed before attempting a correction.
Does installing the app immediately import my data?
Installation gives you access to the app; it is separate from choosing a CSV file, mapping columns, reviewing the preview and starting an import. Review the requested permissions and the current plan terms on Shopify before proceeding.
Sources and further reading
This guide is published by Nimvexa, the maker of CSV Importer. General Shopify behavior and the app’s features are distinguished throughout.