Skip to content
Get a quote

How do I associate records between modules when importing into Zoho CRM?

Short answer

Use IDs. In Zoho's Migration Wizard, records link through migration IDs that are unique across all modules. Migrate users first, and keep parents and children in the same migration. In a regular import, map each lookup by Record ID, a unique field, the record name, email or External ID, with one match type per column.

By

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 usedMigration IDs from the source systemRecord ID, a unique field, record name, email or External ID
RuleIDs must be unique across all modules and all recordsAll rows in one lookup column must use the same match type
OrderUsers first; parents and children in the same migrationParents must already exist in Zoho
LimitsUp to 2 GB per file, 25 GB total25 MB per file; rows per file by edition (1,000 Free up to 200,000 Ultimate)
UndoFrom Import HistoryPer 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

  1. 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.
  2. Migrate users.csv first so owner IDs resolve.
  3. 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.
  4. Use linking modules for many-to-many relationships, such as contacts linked to several deals.
  5. Check after loading. Filter children with an empty lookup; those are your broken links.

Steps for a regular import

  1. Import the parent module and keep a field with the source ID, marked unique.
  2. Import the child module and map its lookup column to that unique field (or to External ID).
  3. 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.

Questions, answered

A few useful answers.

Can I link records by name instead of ID?

In a regular import, yes: Zoho can match a lookup by record name. It's risky with duplicate names, such as two accounts called 'Acme', so use Record ID or External ID when you can.

What if the parent record is imported later?

The lookup will be empty. Import parents first, or update the children afterwards with a second import that matches on their ID and sets the lookup.

Do I need the migration IDs after go-live?

Keep them in a field. They're how you'll trace a record back to the old CRM, run a delta or fix a mapping later.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote