A "missing header rows" style error, or a message such as "Column headers cannot be empty" or "None of the rows can be imported," almost always comes down to how your spreadsheet's first row is structured, rather than a fault with Zoho CRM itself.
The Structure Zoho Expects
- Row 1 must be column headers. Remove any extra rows above this, such as titles, logos, or blank spacer rows, since Zoho reads whatever sits in row 1 as your field names.
- Row 2 onwards must be your actual data. If your data doesn't start immediately below the header row, the import can fail or behave unpredictably.
- Row 1 cannot be empty. An empty first row specifically produces the "Column headers cannot be empty" error. Delete the blank row and try again.
Header Name Matching
Zoho matches your CSV columns to CRM fields by header name. If your spreadsheet says "First Name" but the underlying field's API name is First_Name, the mapping can fail silently and the field shows as missing, even though the data is technically present in your file. Your column headers don't need to exactly match Zoho's field names for the import to work, since you'll be given the chance to map each column manually, but starting with headers close to Zoho's own naming makes that step far smoother.
The fastest fix for header mismatches: Go to Setup, then Import, and download the official sample file for your specific module and layout. This template already reflects the correct field names, including any mandatory custom fields for that layout, so building your import file around it avoids most header-related failures entirely.
Required Fields Must Be Present and Populated
Make sure a column exists for every required field, and that it's actually populated for every row. Any record missing a required field's value is skipped during import rather than causing the whole import to fail, but it's easy to mistake a large batch of silently skipped records for a broader import failure.
Note: Which fields are mandatory depends on the specific layout you select at import time, not just the module's default schema. A custom field required on one layout may be optional on another, so always check requirements against the layout you're actually importing into.
Checking What Actually Went Wrong
If some or all records were skipped, go to Settings, then Data Administration, then Import, then Import History, and click the Skipped link on the relevant import to see the specific reason each record didn't come through.
Need help? 1 Cloud Consultants can help you prepare a clean import file and troubleshoot recurring header or field mapping errors.
Book a discovery call with 1 Cloud Consultants.