An Excel list built over many years contains more than rows and columns. It also carries inconsistent writing habits, empty cells, and business decisions that changed over time. A clean move into Zoho CRM therefore begins before you select a file. You first need to understand the list, decide where each piece of information belongs, and define a recovery path before starting the import.
The practical method is to make the file consistent, then test the same mapping with a small group. A larger import can follow when the results make sense. This is not a promise of perfection. It is a way to expose skipped rows, separate updates that cannot be reversed, and keep decisions under control while they can still be changed inside the source file.
Why a long-standing Excel file cannot move unchanged
A long-running list grows through small responses to daily needs rather than through a shared data model. A phone column may gradually become a notes field, while one status appears under several spellings. That history does not make the file wrong. However, if every destination column needs one clear meaning, those older habits must first be separated and normalized.
The office coordinator opens the list and finds phone numbers and notes inside the same column. Two people have maintained the file for years using different habits. The first task is not to move those rows immediately. Separating phones from notes, interpreting blanks, and aligning different terms for the same concept makes later import decisions easier to review and explain.
Clean the source file before starting the import
Zoho accepts XLS, XLSX, CSV, and vCard imports. Excel controls such as combined filters or embedded images can produce unexpected errors, so prepare a plain working file. VCF files are limited to 5 MB in every edition. CSV limits are 5 MB in Free, 10 MB in Standard and Professional, and 25 MB in Enterprise and Ultimate.
XLS, XLSX, and VCF imports accept no more than 5,000 records in one batch. For larger work, use CSV and divide the file. Row limits are 10,000 in Standard, 20,000 in Professional, 30,000 in Enterprise, and 50,000 in Ultimate. More than ten consecutive blank rows may mark the file's end, and data after them is ignored. Separate multi-select values with semicolons and tags with commas, and review new picklist values before importing. Every picklist value in the file must exist in the matching CRM field. When one does not, correct the source file or ask an administrator to add the value, because a record imported while the value is missing cannot be returned to it later.
Mandatory fields and decisions that cannot be reversed later
A row with an empty mandatory field is skipped. Last Name is mandatory for Leads and Contacts, while Deal Name and Closing Date are mandatory for Deals. During mapping, Replace Empty Values can fill blank mandatory fields, and selected fields can receive defaults. Description, auto-number, unique, formula, and multi-select lookup fields cannot receive a default through this option.
Seeing fewer records than expected after the import does not mean the missing rows disappeared. They may have been skipped because one mandatory field was empty. Zoho does not run validation or layout rules during imports. A field's data type also cannot be changed after creation; only its name can change. Removing a field from a layout does not release its place within the edition's field limit.
Duplicate checking is limited to three matching keys
You can add records as new, update only existing records, or combine both modes. Duplicate checking uses one of three keys: Record ID, Email, or Record Name. Matching is case-insensitive. It does not perform fuzzy matching that automatically merges similar spellings, so differences inside the chosen key column need to be corrected in the source file before the import begins.
A module ID is not a general duplicate-prevention key. Use it when restoring records that were previously exported; selecting it for another file can create duplicates. When adding and updating together, assess the results for matched and unmatched rows separately. The rule that skips a row with an empty mandatory field remains relevant regardless of the import mode you choose.
Test the complete mapping with a small group first
Before using the full live file, prepare a small group with the same columns and mapping. After the test, read the added, updated, and skipped results in import history. An XLS, XLSX, or VCF test remains subject to the 5,000-record batch limit. The sample reveals how the mapping behaves, but it cannot guarantee that every later row will produce the same result.
Zoho Sandbox is available in Enterprise and Ultimate. Enterprise provides three configurations, while Ultimate provides seven configurations and one full data copy. Lower editions do not have this separate Sandbox option, so testing uses a small batch while accounting for the 30-day undo window. In that situation, an add-only test keeps the reversible scope clearer than a test that updates existing records.
Make an explicit choice about import automation
The option to trigger automation and processes appears on the import screen only for files below 10,000 rows. Date-based workflows run independently of that choice. Turning the option off should therefore not be treated as disabling every automation. Review date fields and their possible effects while preparing the file, and do not assume which other automations will run beyond the documented boundary.
The same screen lets you select an assignment rule and define a follow-up task. Using an assignment rule requires the Assignment Rules profile permission. Before starting the Zoho import, record three decisions separately: the automation option's state, the selected assignment rule, and the follow-up task. This gives you a reliable reference when reviewing which choices were active during processing.
The undo window does not reverse every import change
An import cannot be stopped after it starts. Undo is available within 30 days, but it removes only records that were added; it does not restore updated records to their earlier state. If a Contacts import is undone, Accounts brought in with those contacts are also deleted. Before work containing both additions and updates begins, document which outcomes remain reversible.
Import history remains listed for 60 days. Details for added, updated, and skipped records are visible during the first 7 days; afterward, only totals remain. When fewer than 3,000 records were skipped, you can download a file containing their reasons. Administrators see every import, while other profiles see only their own. Review should happen before the detailed view expires.
Edition thresholds and the checks to make after completion
Read the thresholds together: CSV capacity is 5 MB in Free, 10 MB in Standard and Professional, and 25 MB in Enterprise and Ultimate; VCF remains limited to 5 MB everywhere. Row limits are 10,000 in Standard, 20,000 in Professional, 30,000 in Enterprise, and 50,000 in Ultimate. Sandbox offers three configurations in Enterprise and seven in Ultimate, which also includes one full data copy. Lower editions rely on a small batch and the 30-day undo window.
For the final check, compare added, updated, and skipped totals in Zoho history with your source file. Examine details within the first 7 days and, when available, download the skipped-record file so mandatory blanks can be corrected at the source. If undo is necessary, remember that it removes additions only and may also delete Accounts created with imported Contacts. A clean import ends with an explainable result, not merely a completed progress indicator.
