Two tools, two ways of linking
Zoho has two ways to load data, and they link records differently.
| Migration Wizard (from another CRM) | Import (one module at a time) | |
|---|---|---|
| Key used | Migration IDs from the source system | Record ID, a unique field, record name, email or External ID |
| Rule | IDs must be unique across all modules and all records | All rows in one lookup column must use the same match type |
| Order | Users first; parents and children in the same migration | Parents must already exist in Zoho |
| Limits | Up to 2 GB per file, 25 GB total | 25 MB per file; rows per file by edition (1,000 Free up to 200,000 Ultimate) |
| Undo | From Import History | Per import |
Zoho’s FAQ says linking in a migration “purely works based on the ID’s”, and those migration IDs are also used for record owners. That’s why users have to come first.
Steps for a migration
- Give every source record a unique ID. If two source tables both use numbers starting at 1, add a prefix (
ACC-1,CON-1) so the IDs are unique across modules, as Zoho requires. - Migrate users.csv first so owner IDs resolve.
- Put the parent and child files in the same migration. For example, Accounts, Contacts and Deals together, with each child row holding its parent’s ID.
- Use linking modules for many-to-many relationships, such as contacts linked to several deals.
- Check after loading. Filter children with an empty lookup; those are your broken links.
Steps for a regular import
- Import the parent module and keep a field with the source ID, marked unique.
- Import the child module and map its lookup column to that unique field (or to External ID).
- Use one match type for the whole column.
What the native tool does / where it stops
Zoho links by ID reliably, but it doesn’t create the IDs or fix them. When an export has no ID per row, you have to build one. Duplicate names make name matching unsafe, and source systems often reuse IDs across tables. Prefixing IDs per module is the step most first attempts miss.
Where FlitStack AI fits
FlitStack AI keeps source IDs on every record, resolves the lookups in order and checks that associations survived during the sample run. See Zoho CRM migrations.