Help article

Troubleshoot CSV import issues

Understand validation errors, skipped rows, duplicate purchases, zero-value purchases, dates, currencies, and file size limits.

Updated 7/19/2026

Troubleshoot CSV import issues#

CSV imports are easiest when you validate first and import second.

Skipped rows#

Skipped rows are not always errors. Joinometry may skip:

  • zero-value purchases,
  • purchases that already exist,
  • rows without enough player or transaction information,
  • rows outside the expected format.

Validation errors#

Validation errors mean Joinometry could not understand a row well enough to import it.

Common causes include:

  • wrong template,
  • changed column headers,
  • invalid dates,
  • missing transaction IDs,
  • unsupported currency values,
  • an amount that is not a paid purchase.

File size#

Keep CSV files under the upload limit shown on the Imports page. If your export is too large, split it by month or by smaller date ranges.

Browser file selection#

Your selected template and field choices can stay after validation, but your browser may require you to choose the local file again before importing.

Best next step#

Fix the first few validation errors, validate again, and only import once the preview matches what you expect.

Was this helpful?

A quick rating tells us which guides need work.

Need more help?

If this article does not answer your question, contact us and include what you were trying to set up.

Contact support