CSV Import Checklist

By Online CSV Editor · Last updated: 2026-03-23

If you need to import a CSV into Shopify, HubSpot, Mailchimp, Salesforce, or another platform, check six things first: headers, row structure, delimiter, encoding, duplicate logic, and sample import behavior. That checklist catches most practical import failures before they touch live data.

This guide is especially useful for operators working with contact lists, product catalogs, customer records, order exports, or supplier feeds where one bad header or one malformed row can break the whole upload.

The high-value CSV import checklist

Confirm the file is actually the right dataset. Wrong exports and stale files are a common human failure mode.
Match required headers exactly. Destination tools often expect specific column names and order. Start with header cleanup guidance.
Check row structure and quotes. Make sure one record equals one row and quoted commas do not create fake extra columns.
Validate delimiter and encoding. Files that look okay in one tool can still fail in another due to semicolon/comma mismatches or UTF-8 issues.
Review duplicate and identifier logic. Decide whether email, customer ID, SKU, or another field is the true unique key.
Run a test import. Upload a small subset before pushing the full production file.

What to check in the file itself

Headers: remove duplicate header names, fix spelling, and match the destination schema. Example: if Shopify expects Variant SKU, using SKU may not map correctly.

Required values: scan for blank email addresses, missing product handles, empty titles, or other fields the importer treats as mandatory.

Duplicates: remove repeated contacts, customers, or SKUs intentionally. Blind duplicate removal can also delete legitimate variants, so define the rule first.

Text identifiers: preserve ZIP codes, account numbers, and SKUs with leading zeros. If they are coerced into numbers, re-import may silently fail or create mismatches.

What to check in parser settings

Delimiter matches the source file and destination requirements.
UTF-8 text renders correctly without mojibake or replacement characters.
Quoted fields remain intact when cells contain commas, semicolons, or line breaks.
No null bytes or hidden parser warnings remain in the file.

Example: using the checklist for a Shopify product upload

You receive a supplier product CSV with semicolon delimiters, mixed casing in headers, duplicate SKUs, and a few descriptions containing commas and line breaks.

Open the file with the correct semicolon delimiter.
Rename headers to match Shopify’s expected fields.
Check quoted descriptions so they stay in one cell.
Deduplicate SKUs intentionally, keeping valid product variants.
Export a clean UTF-8 version and test with a small import batch.

How the in-app pre-import checklist helps

CSV Editor includes a lightweight pre-import checklist to flag common risks early. It can help surface extension mismatches, empty content, parser-detected delimiter information, replacement characters, null bytes, and parser diagnostics before deeper editing work starts.

Treat it as an early-warning layer, not a guarantee of vendor-specific compatibility. Destination platforms still apply their own schema and validation rules after upload.

Quick tips

Test import 10 to 20 rows before importing thousands.
Keep the original export untouched for rollback.
Document the unique key you used for deduplication.
Check a few rows with special characters and long descriptions before export.

FAQ

Why does my Shopify or CRM import reject only some rows?

That usually points to row-level validation issues such as missing required fields, bad quote handling, invalid values, or duplicates against existing records.

What is the biggest mistake before a CSV import?

Skipping a sample import. A preview can look perfect while the destination tool still rejects the file due to mapping or validation rules.

Should I clean the CSV before or after mapping fields?

Usually before. If headers and values are already clean, field mapping becomes simpler and import errors are easier to diagnose.

Canonical: https://csveditoronline.com/docs/csv-import-checklist-crm-shopify