Common Import Issues
The most common CSV upload errors and how to fix them.
How to read this page
Each issue below follows the same format: what the error says, why it happens, and how to fix it. If you're looking for a specific error message, scan the bold headings.
"Date format not recognized"
Why it happens: The date was entered in a format Nabu doesn't recognize — for example, 1/15/24, 15-01-2024, or January 15, 2024.
How to fix it: Change all dates in the affected column to YYYY-MM-DD format (for example, 2024-01-15). In Excel or Google Sheets, you can format the entire column as text and manually ensure dates match this pattern. Some spreadsheet apps auto-convert dates to a localized format when you open a CSV — always check the date column before uploading.
"Provider not found"
Why it happens: The provider_email (or provider identifier) in your CSV doesn't match any provider set up in People & Payroll. This is usually a typo, an email address that hasn't been entered in setup yet, or a provider who was entered with a slightly different email.
How to fix it: Go to Setup → People & Payroll and check the email address on file for the provider. Update the CSV to match exactly, or add the provider to setup first and then re-upload.
"Required field is empty"
Why it happens: A column that Nabu requires — such as service name or price — was left blank in one or more rows.
How to fix it: Open your CSV and fill in the missing value. Check the template's example row or notes column to confirm which fields are required vs. optional. Required fields are usually marked in the template.
"Duplicate record"
Why it happens: A row in your CSV has the same name or identifier as a record that already exists in Nabu. By default, Nabu won't overwrite existing records to prevent accidental data loss.
How to fix it: If you're trying to update an existing record, edit it manually in the setup section rather than re-importing it. If the record in your CSV is genuinely new (not a duplicate), check for naming inconsistencies — for example, "HydraFacial" vs. "Hydrafacial" vs. "Hydra Facial" would all be treated as separate records.
"Amount contains currency symbol"
Why it happens: A dollar amount was entered as $150 or $1,500.00 instead of a plain number.
How to fix it: Remove the $ sign and any commas from all amount fields. Enter 150 or 1500.00 — just the number. You can use Find & Replace in your spreadsheet to remove $ characters from an entire column at once.
"File is not a valid CSV"
Why it happens: The file was saved in the wrong format. Common causes: the file was saved as .xlsx (Excel format) instead of .csv, or the spreadsheet has merged cells, which CSV format can't represent.
How to fix it: Go back to your spreadsheet, unmerge any merged cells, and save as CSV. In Excel: File → Save As → select "CSV (Comma delimited)." In Google Sheets: File → Download → Comma Separated Values. Do not upload .xlsx, .xls, or .numbers files directly.
"Column header mismatch"
Why it happens: One or more column headers in your file don't match what Nabu expects. This happens when a header was accidentally renamed, a column was deleted, or you built the file from scratch instead of using the template.
How to fix it: Download the template again and compare your column headers to the template headers side by side. Headers must match exactly, including capitalization and spacing. Copy the header row from the template directly into your file to ensure an exact match. Do not translate, abbreviate, or reorder headers.
General questions
How do I know which rows had errors? The validation preview highlights error rows in red. Each error cell shows a tooltip explaining what's wrong. You can also download the error report from the validation screen — it's a copy of your CSV with an added column describing the issue for each row.
Can I import partial data — just the valid rows? Yes. If you confirm an import that has a mix of valid and error rows, Nabu imports all valid rows and skips the error rows. The preview tells you exactly how many rows will be imported before you confirm. Fix the error rows in your CSV and re-upload them separately when ready.