CSV Import & Export Guide

By Online CSV Editor · Last updated: 2026-04-22

Most CSV import and export problems are not caused by the upload button. They come from messy headers, delimiter mismatches, inconsistent values, encoding drift, duplicate rows, or files that were converted without a clear schema plan. The goal of this hub is simple: make a CSV predictable before it moves.

Use this section when you are preparing a file for a CRM, ecommerce platform, reporting tool, app, or API. If the problem is more about cleanup than conversion, start from the CSV cleaning guide.

The best order for import and export prep

  1. Open the file correctly first. Confirm delimiter, encoding, and header row before changing values.
  2. Fix the schema next. Rename headers, remove junk columns, and preserve key fields or IDs.
  3. Choose the right workflow. Combine rows, merge files, convert formats, or export with a new delimiter based on the actual job.
  4. Validate the output. Spot-check records and run a small sample import or script test before using the full dataset.

What import-ready and export-ready actually mean

  • The file opens into the correct columns with no row drift.
  • Headers map cleanly to the destination fields or code-level keys.
  • Critical IDs, dates, and optional values follow one consistent rule.
  • The conversion path is explicit: combine, merge, delimiter change, CSV to JSON, direct import, or TSV export.
  • A small real-world test confirms the destination accepts the result.

Example: taking a supplier export into an app API

Suppose you receive a supplier CSV with columns like Product Name, SKU, Price, and Updated At. Before converting that file into JSON for an internal app, you would first validate the delimiter, clean the headers, standardize dates and blanks, and confirm SKUs stay text-safe.

  1. Open and validate the CSV structure.
  2. Rename headers for cleaner downstream keys.
  3. Normalize missing values and date formats.
  4. Convert the cleaned CSV to JSON.
  5. If you need to move structured app data back into a flat file, plan the reverse workflow with JSON to CSV conversion.
  6. If a downstream workflow expects tab-delimited output instead of commas, finish with CSV to TSV conversion.
  7. If you receive a tab-delimited export but your destination expects commas, use TSV to CSV conversion.
  8. If you need a universal pre-upload QA pass before any destination, use the CSV import checklist.
  9. If you are preparing a product file for ecommerce upload, use the Shopify CSV format guide.
  10. If you are preparing a contacts file for CRM import, use the HubSpot contacts CSV format guide.
  11. If you are preparing a subscriber list for email marketing, use the Mailchimp CSV import guide.
  12. If you are preparing an address-book handoff, use the Google Contacts CSV import guide.
  13. Test a few objects in the API or app before using the full dataset.

Core import and export guides

Convert CSV to TSV safely

Re-export comma-delimited files as tab-separated output without breaking quoted text, row structure, or destination imports.

Convert TSV to CSV safely

Turn tab-delimited files into standard CSV without breaking headers, quoted text, comma-heavy values, or import structure.

CSV import checklist

Run a universal pre-upload QA pass for headers, delimiter, encoding, quoted fields, IDs, duplicates, and sample-import safety.

Common mistakes teams make

Converting before cleaning: format changes do not fix structural mess. They often freeze it into a new output type.

Skipping header QA: unclear headers break both import mapping and JSON key quality.

Not deciding how to handle blanks: empty cells, placeholders, and null values need one deliberate rule.

No sample test: even a technically correct file can still fail the real destination workflow.

Quick tips

  • Always keep the original export unchanged.
  • Pick one schema reference before combining or merging files.
  • Validate delimiter and encoding before assuming a file is broken.
  • Use a small sample import or API call as the final QA step.

FAQ

What should I check before importing a CSV anywhere?

Check delimiter, encoding, headers, required columns, duplicate risk, and a small sample import before uploading the full file.

What is the difference between combining and merging CSV files?

Combining means stacking rows from files that share the same schema. Merging means joining columns from different files by a shared key such as email, customer ID, or SKU.

When should I convert CSV to JSON instead of keeping CSV?

Convert to JSON when a script, app, or API needs object-based data. Keep CSV when the workflow is still centered on flat tables, spreadsheets, or bulk imports.

When should I convert JSON to CSV?

Convert JSON to CSV when people need a flat table for spreadsheet review, bulk uploads, reporting, or handoff workflows. Decide the column layout first so nested fields and arrays do not create a messy export.

When should I convert CSV to TSV?

Convert CSV to TSV when the destination explicitly supports or prefers tab-delimited files, especially if text-heavy fields contain many commas and tabs produce a cleaner import workflow.

Canonical: https://csveditoronline.com/docs/csv-import-export-guide