Fix a CSV import problem
Resolve file, mapping, and row validation errors.
If the file is rejected
- Export as comma-separated UTF-8 CSV, not an Excel workbook, tab-separated file, or semicolon-separated file.
- Keep the file within 2 MB and 500 data rows. Use distinct, nonempty headers and the same column count on every row.
- Check quotes around text containing commas or line breaks. Close every quoted value and double any quote inside it.
- Shorten exceptionally large cells or rows. Warly rejects an individual row above its 48 KB import limit.
If rows are invalid or skipped
- Map Name, and Phone number for customers. Do not map two columns to the same Warly field.
- For local phone numbers, use a recognized two-letter Country code or set the workspace country. An international number including its country code is less ambiguous.
- Check email spelling and format. Set product duration to a whole number from 1 to 120.
- Duplicate means Warly found an existing record or duplicate row. It is skipped without changing the saved record.
If confirmation fails
A changed file, mapping, or workspace default requires Preview and validate again. If the connection stopped during import, check the saved list and preview again before retrying. Earlier valid rows may already have imported; they are not rolled back.
If Import CSV is unavailable, ask an Owner or Admin. For persistent failures, contact Warly with the exact error and a small synthetic example of the affected columns, not a file containing real customer data.