Use this matrix when planning a Zoho move or connecting an existing CRM. Historical file migration, read-only extraction, ongoing per-record sync and portable archive restore have different contracts. A successful connection is not proof that every source module can move or synchronize.
Watch the lesson
Choose the appropriate path
| Path | What it does | Required review |
|---|---|---|
| Source files or backup package | Stages supported historical records | Fields, relationships, duplicates, exceptions and capacity |
| Read-only Zoho migration source | Reads selected supported source data for staging | Organization, selected modules, extraction outcomes and import preview |
| Zoho CRM record integration | Exchanges supported Contact fields under its selected policy | Direction, source IDs, conflicts and per-record receipts |
| Zoho Desk integration | Exchanges its supported ticket projection | Desk organization, mapping, direction and ticket outcomes |
| Nviti CSV or portable archive | Supports native portability and supported recovery | Workspace identity, record support, files and archive-only exclusions |
Coverage by feature
| Feature | Current migration support | What requires separate handling |
|---|---|---|
| Contacts, leads, organizations and deals | Supported source modules with explicit source IDs and destination mappings | Reconcile duplicates, converted-lead relationships, owners and stages |
| Tasks, calls, events/meetings and notes | Supported historical record modules | Do not infer original worker state, provider delivery or every source recurrence rule |
| Pipelines and stages | Deal rows can target explicitly mapped Nviti stages | Source pipeline definitions and complete stage histories are not reconstructed by the module importer |
| Custom fields | Supported mapped values; unmapped data can produce restricted source-archive exceptions | Definitions, type semantics and permissions need explicit destination setup |
| Optional Zoho module/field metadata | Explicit mappings into existing authorized native definitions for supported lookups | Does not create native definitions or grants; unsupported types/targets have excluded or rejected dispositions |
| Qualification and AI | Native CSV has an Nviti qualification column | Generic imported contacts default to unqualified; source AI evidence or suggestions do not become reviewed Nviti output |
| Reports and forecasts | Build native definitions and snapshots using the authorized imported records | Zoho reports, categories, adjustments, periods and snapshots have no current module-import adapter |
| Quotes | Limited normalized quote and line-item file import | Explicit currency is required; unsupported line tax and fixed-amount discount semantics are rejected |
| Approvals, sequences, onboarding and renewals | Review and configure native workflows separately | Source definitions and execution histories are not imported as executable automation |
Ongoing Zoho CRM synchronization currently covers Contact name, email and phone. Wider file-import support does not extend that sync to deals, organizations, custom fields, AI, quotes, forecasts, reports or automation. Zoho Desk has its own bounded contract; see Zoho Desk. Manual transfer and record-event sync are independently controlled.
Native portable archives
A portable archive can contain permitted advanced records such as quotes, reports, approvals, sequences, onboarding templates and forecasts. Exported does not mean executable restore support.
Supported restoration covers contacts, organizations, pipelines, stages, fields, modules/custom records, deals, activities and notes under current access and capacity checks. Other exported objects may remain archive-only with exceptions. Credentials, operational enrollment state, campaign bindings and worker execution are not reconstructed. Full workspace restoration is unavailable.
Run a migration pilot
- Keep the original source export and choose a stable source organization or migration identity. Reuse it for later reimports.
- Prepare a small sample containing related contacts, organizations, deals, activities, a duplicate, a changed record and a deliberately unsupported item.
- Review field types, stage/owner mappings, timezone, currencies and explicit duplicate targets.
- Compare source-row, valid-row and exception counts with proposed operations and net-new capacity. Valid rows are not necessarily new records.
- Download and review complete row/file outcomes. Do not approve from a bounded sample alone.
- Approve the current preview, then reconcile created, updated, held, skipped and rejected results and relationships.
- Check retained export and guarded rollback while source evidence is still unexpired. Later-edited records require manual reconciliation.
Imports enforce current release scope, purchased capabilities, staff permissions and tenant-wide limits. Importing a subscription flag, consent-looking value or automation label never creates authority to send. Unknown or withdrawn marketing consent remains a separate decision.
See Migration and recovery, CRM API boundaries, Zoho record updates and Files and storage.