Migrate from Kordeva to Zoho CRM

Kordeva Contacts map to Zoho CRM Contacts if the contact is an active customer or sales-qualified prospect attached to a Company. Contacts that represent early-stage or unqualified prospects map to Zoho Leads. We determine the split using Kordeva's contact status or stage property if present; if no such property exists, all contacts migrate to Zoho Contacts with the customer admin confirming whether Leads should be created for a separate qualification queue.

Kordeva Company records map directly to Zoho CRM Accounts. Company name becomes Account Name, and any domain or website stored in Kordeva becomes the Account's Website field. We use Company name as the dedupe key during Zoho import to prevent duplicate Account creation. Account is created before any Contact import so that the Account-Contact lookup relationship is satisfied at the moment of Contact insert.

Kordeva Deals map to Zoho CRM Deals. The Kordeva pipeline stage names map to Zoho Stage values, which we configure in Zoho before migration. Deal amount, close date, owner, and associated Company all migrate directly. If Kordeva tracks multiple deal pipelines, each pipeline becomes a separate Zoho Deal Layout that we pre-configure during schema setup.

Kordeva activity records (calls, emails, tasks, meetings) logged against Contacts or Deals migrate to Zoho CRM Tasks and Events. We resolve the parent record reference (Contact ID or Deal ID) at migration time and set the WhoId and WhatId on the Zoho Activity record. Activity timestamps are preserved as the original Kordeva creation date for timeline integrity. Task status and priority migrate to Zoho's Status and Priority picklists.

Kordeva custom fields defined via the Custom Fields API are enumerated during discovery and recreated in Zoho CRM as custom fields on the equivalent module. Field type mapping follows Zoho's supported types: Kordeva text and number fields map to Zoho Multi-Line Text or Line Text; Kordeva date fields map to Zoho Date; Kordeva picklist-style fields map to Zoho Picklist. Custom field definitions must exist in Zoho before the corresponding data import phase begins.

Kordeva Users or Owners referenced on Contact, Company, and Deal records map to Zoho CRM Users by email address match. We extract the distinct owner set from Kordeva records during discovery and match each against Zoho's User table. Any Kordeva owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Kordeva's bundled invoicing feature (included at the Regular tier) means some customers may have invoice records and line items tied to Kordeva Accounts. We migrate the Account portion of this data to Zoho CRM Accounts. Invoice records, line items, and payment history require a separate assessment: if the customer uses Kordeva invoicing as their primary billing system, a parallel Zoho Books migration may be needed as a follow-on engagement. We flag this during discovery and scope it as a separate line if invoice data is material.

If Kordeva contains product or service catalog records referenced by Deals, these migrate to Zoho CRM Products. Product name, SKU, unit price, and description map to Zoho Product fields. Price book entries are created during the Product import phase so that Deal line items can reference them.

Kordeva file attachments on Contacts, Companies, and Deals require a separate export step since attachments are stored separately from the record data. We export attachments alongside record data, map the attachment reference to Zoho's attachment storage (tied to WorkDrive under Zoho's Q1 2026 update), and link each file to the migrated record via the Zoho CRM Attachments mechanism. Attachments that cannot be directly linked are delivered as a file package with a mapping index for manual re-association.

Kordeva notes attached to CRM records migrate to Zoho CRM Notes. Note body content migrates as plain text. Any rich text formatting is preserved where the source data supports it. Notes are linked to the parent Contact, Account, or Deal via the Zoho Notes module's record association.