Use the Zoho CRM card on Integrations for the selected company. It opens the connection controls and supported manual record exchange. Bulk migration and ongoing record updates are separate operations.
Watch the lesson
Connect your organization
- Select the company whose data you intend to connect.
- Open the Zoho CRM integration and choose the correct Zoho data center. An account at
accounts.zoho.comuses the US data center. - Authorize the requested access in Zoho and return to Nviti.
- Verify the organization and environment shown before reading or sending data.
- Use the additional write or event-authorization action only for the operation you intend to enable.
The Nviti operator configures the OAuth application and registered callbacks. Ordinary customers do not need to copy redirect URLs into a developer console. An invalid redirect error requires an operator to match the exact registered callback and running configuration. Never put client secrets, access tokens or refresh tokens into tickets, notes or screenshots.
Zoho CRM and Zoho Desk have independent authorizations even when the operator uses one server application's client credentials. Tokens are encrypted in the shared connection store; reversible encryption allows provider refresh. They cannot be stored as one-way password hashes and still be used for OAuth calls.
Exchange a Contact
The current record-sync slice exchanges name, email and Phone for Zoho CRM Contacts. It does not mirror Deals, Accounts, Mobile, owners, marketing enrollment, attachments, custom fields or deletions.
- Pull reads the selected remote record into Nviti under current mapping and capacity rules.
- Push sends permitted selected local values to Zoho with the required export/write authority.
- Review current local and remote values before linking an imported mapping or resolving a conflict.
- A known source ID identifies the same provider record. Similar email or phone values require review; they are not permission to merge people automatically.
Two-sided edits can produce a conflict rather than silently overwriting values. A failed or uncertain remote create is held for reconciliation. Review the exact remote record and use the reconciliation action instead of creating again. Receipts record operations; a connected badge alone proves neither a completed import nor synchronization.
Choose ongoing behavior
Record updates uses provider notifications and local record events. Directions require explicit setup; connection alone does not start a full historical download or default bulk sync. Broader migration from Zoho exports is covered in Migration.
Disconnect removes the working grant and stops new authorized calls while retaining imported records, identity links and duplicate-prevention history. Reconnect to the intended organization and review the mapping again. See Access for purchased capabilities, staff roles and current API/storage allowances.