Migrate from Zoho CRM to Pipedrive

Zoho Leads map to Pipedrive Person records. We use the Person's name, email, phone, and any lead-specific fields (Lead_Source, Lead_Status) as custom fields on the Pipedrive Person. Pipedrive does not have a separate Lead module at Essential; Leads and Contacts live in the same People object. We set a custom field zoho_lead_source__c to preserve the original Zoho lead attribution data, and a status field to track whether the record was a Zoho Lead or Contact.

Zoho Contacts map to Pipedrive Persons. The Contact-to-Account link in Zoho (lookup relationship) maps to a Person-Organization link in Pipedrive. We preserve email, phone, address, title, and any custom fields. If the Contact has no linked Account in Zoho, the Person is imported without an Organization link and flagged for manual linking.

Zoho Accounts map to Pipedrive Organizations. The Account name becomes the Organization name; website, industry, employee count, and billing address map to corresponding Pipedrive Organization fields. Account is imported first, before any Person import, so that the Person-Organization link is satisfied at insert time. Zoho Account IDs are preserved in a custom field zoho_account_id__c for reconciliation.

Zoho Deals map to Pipedrive Deals with stage name remapping. Each Zoho pipeline maps to a Pipedrive Pipeline. Zoho's deal stage names (e.g., Proposal Sent, Negotiation) are remapped to Pipedrive stage names, and we preserve the original Zoho stage name in a custom field. Deal value, expected close date, and owner (mapped via email) migrate directly. Multi-pipeline Zoho configurations require us to create multiple Pipedrive Pipelines during migration.

Zoho Products map to Pipedrive Products. Product_Code, Unit_Price, and Unit map directly. We import Products before Deals to ensure that the product reference is valid when Deal-Product associations are created. Pipedrive Products do not support multi-currency price books natively; we flag any Zoho multi-currency price book configuration for manual rebuild.

Zoho Quotes store line items as subform related records, not inline fields. We extract the Quote parent record and each subform line item separately via Zoho's related-records API endpoint, then reconstruct them in Pipedrive as a Deal with multiple Product entries. The Quote's total and terms migrate as Deal fields. If the Zoho plan lacks API access, subform data cannot be extracted automatically and we flag the records for manual re-entry.

Same treatment as Quotes. Zoho Sales Orders use subform records for line items. We extract parent and subform children separately, reconstruct as Pipedrive Deals with Products, and flag any Zoho-specific fields (e.g., terms, shipping address) as custom fields on the Deal.

Zoho activity modules (Tasks, Events, Calls) map to Pipedrive Activities. We preserve the activity type, subject, due date, completion status, and linked record association (Person, Organization, Deal). Zoho Call records with disposition and duration migrate to Pipedrive Activities of type Call with custom fields for disposition and duration in seconds.

Zoho attachments are stored as separate file records linked to parent modules via lookup IDs. We extract attachment metadata (filename, MIME type, URL) via the Attachments API endpoint and download each file. For Pipedrive, we upload files to the linked Person, Organization, or Deal using Pipedrive's File API. Pipedrive's attachment handling is less structured than Zoho's; we create File records and link them via the related_object_type and related_object_id fields.

Zoho custom modules are discovered via GET /settings/fields during scoping. If the destination Pipedrive is on Essential-Professional, we map custom module records to custom fields on Person, Organization, or Deal. If the destination is Enterprise ($99/mo), we create Pipedrive custom objects via the API with equivalent field schemas. We flag any custom module that has lookups to other custom modules, as these require a multi-phase import sequence to satisfy the dependency chain.

Zoho User records carry email, name, role, and status. We extract all active and inactive users during discovery and build an email-to-Zoho-user-ID mapping table. At import time, we match Zoho owner IDs on Contacts, Accounts, and Deals to Pipedrive Users by email. Any Zoho Owner without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Zoho tags are cross-module labels that export with the parent record. We extract tag arrays per record, then decide with the customer whether to migrate them as a multi-select custom field (pipedrive_label_ids) or as a plain-text custom field. Pipedrive's native label feature is plan-gated (Advanced and above for custom labels); we note this constraint during scoping.