SOURCE-BASED ANALYSIS · NO HANDS-ON RATING
Choose update identity before editing the file
Zoho CRM can match imported rows by a module Record ID or by another supported field such as an email or record name. For a controlled export-edit-import cycle, the CRM-generated Record ID is the stable link back to the original record. Preserve it as data and do not regenerate, format or concatenate it in a spreadsheet.
Build a representative pilot
Export the exact records you intend to update. Keep an untouched copy, then create a pilot containing an unchanged row, a valid update, an empty source cell, a row with a deliberately invalid value and one row that should not match. Write the expected outcome for each row before importing.
| Row | Expected result | Control |
|---|---|---|
| Existing ID, changed phone | One record updated | Record count unchanged |
| Existing ID, empty industry | Existing value retained when skip-empty is selected | Compare before and after |
| Unknown ID | Handled according to selected import mode | Inspect import result |
This is a hypothetical acceptance fixture, not a measured Zoho CRM test.
Map fields deliberately
Select the update-only or add-and-update mode that matches the approved change. Map the Record ID explicitly and review every field mapping. Zoho documents an option to skip updating empty values; use it only when an empty cell means no change, not when emptiness is an intentional deletion.
- Export and archive the source records.
- Preserve Record IDs and source column names.
- Prepare the pilot and expected outcomes.
- Review mapping, empty-value policy and automation settings.
- Run the pilot and inspect the import result.
- Re-export affected records and reconcile IDs, values and counts.
Keep evidence of the import
Record the module, export time, source file checksum, selected import mode, matching field, mappings, operator and reconciliation result. Do not assume that a completed import means every downstream automation has also finished.
Sources and verification
Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.