A bulk import doesn’t always succeed on the first try — a missing column, a typo in a header, or a few bad rows can hold it up. Cornerspot checks your CSV before importing anything and tells you exactly what to fix. This guide shows you how to read those errors and get your import through.
How import validation works
When you upload a CSV from Bulk Import (at /dashboard/settings/imports), Cornerspot validates it first — nothing is created until the checks pass. Problems fall into two kinds:
- File-level problems block the whole import — for example an unrecognized column or a malformed file. You fix the file and re-upload.
- Row-level problems are reported per row on the review step, so the valid rows can still go through while you fix the rest.
1. Start a new import and upload your CSV
From the Imports page, click New import, then drop your CSV onto the upload area (or click browse to pick it). You can build your file from the Download example CSV link if you don’t have one yet.
2. Let Cornerspot validate the file
Cornerspot reads the file and runs a quick validation (“Validating your CSV — this normally takes a few seconds.”). It’s checking the columns and every row before anything is imported.
3. Read a file-level problem
If the file itself can’t be processed, the wizard shows a File-level problem with an error code and a plain-language message — here, an unrecognized column. A blocked file can’t continue until you fix it, so the whole import stops.
4. Fix your CSV and try again
Correct the issue described in the message — for example, rename the column to a recognized field, or use the “<Entity> - <field>” header form from the example CSV. Then click Try a different file to upload the corrected version.
Reviewing row-level errors
Once the file passes, you reach the review step. Alongside the plan summary, an error table lists every row that needs attention. Use the two dropdowns to focus on what matters:
- By status: Invalid (preflight) for rows that failed validation, Failed (commit) for rows that errored while saving, Valid for rows ready to go, or All.
- By object type: narrow the table to Accounts, Contacts, Deals, Products, Line items, or Activities.
Each row shows its number, type, status, and first error, so you know exactly which line of your CSV to correct.
Partial imports and past runs
- Partial status: if you commit a file where some rows succeed and others fail, the import finishes with a Partial status — the good rows are created and the failed ones are listed for you to fix and re-import.
- Open a past import: from the Imports list, open any run to see its detail page — the row counts, file size, who requested it, the duration, and a Rows tab with the remaining errors and a File errors tab for file-level problems.
- Retry cleanly: fix the rows flagged on a Partial or failed run, then start a fresh import with just the corrected rows.
Tips for getting an import through
- Start from the Download example CSV so your headers already match Cornerspot’s expected fields.
- Read the error code and message first — they name the exact column or field to fix.
- Fix file-level problems before worrying about rows; a blocked file never reaches the row checks.
- Keep imports small while you’re sorting out errors — it’s quicker to validate and easier to spot what went wrong.