Migrate from Zoho CRM Plus to Pipedrive

Zoho Leads map to Pipedrive People records created in Lead mode. Lead_Status, lead source, and any lead scoring fields migrate as custom fields on the Person. If the customer uses Zoho's Lead conversion feature, the converted Leads (now Contacts) are deduplicated against any existing Zoho Contact records that also migrate. The migration dedupe key is email address, case-insensitive.

Zoho Accounts map directly to Pipedrive Organizations. Industry, website, address, billing address, and phone fields migrate 1:1. The Zoho Account Name becomes the Pipedrive Organization name. Account is the parent object, so we import all Organizations first before any Person or Deal records to satisfy the Organization lookup at insert time.

Zoho Contacts map to Pipedrive People records linked to their parent Organization by Organization ID. Ownership, custom fields, and Contact Role on related Deals migrate as custom Person fields. Tags attached to Zoho Contacts migrate as tag strings on the Pipedrive Person. Email and phone are the dedupe keys.

Zoho Deals map to Pipedrive Deals. Stage name, amount, closing date, probability, and pipeline assignment migrate. Pipedrive's single-deal-per-Contact model means we require a Deal to have at least one linked Organization or Person; Deals with no linkage are flagged in scoping. Pipedrive's probability field is a percentage integer, matching Zoho's convention.

Zoho's multiple pipelines per module with custom stage names and probabilities map to Pipedrive Pipeline stages. We ask the customer to confirm the destination pipeline stage map during scoping. If Zoho has more than one pipeline, we configure multiple Pipedrive Pipelines (available from the Advanced tier upward) and map stage probabilities per pipeline. The Essential tier supports one pipeline; the Advanced tier and above support multiple pipelines.

Zoho Tasks and Events map to Pipedrive Activities. Tasks map to the Pipedrive Task activity type; Events (including Call Logs) map to the Pipedrive Event activity type. The related-to record (Contact, Account, Deal) links via Pipedrive's deal_id or person_id on the Activity. Due date, status, and owner preserve. We resolve the owner by email match against the Pipedrive User table during import.

Pipedrive has no native Campaign object equivalent to Zoho's Campaigns module. Campaign membership on Contacts migrates as a custom multi-select picklist field on the Person (listing campaign names), or as tag strings on each Person record. The customer chooses the strategy during scoping. Campaign metadata (type, status, start/end dates, budget) is documented in a written inventory for the customer's admin to rebuild in a marketing tool if needed.

Zoho Desk Cases have no direct Pipedrive equivalent. Pipedrive does not include a native helpdesk module. Cases migrate as Person notes or as a custom Case object (Pipedrive Advanced tier) with status, priority, and assignee fields. Conversation history migrates as note text on the Person or Case record. The customer's admin rebuilds the support workflow in a dedicated helpdesk tool post-migration.

Zoho Products map to Pipedrive Products, preserving product code, unit price, tax, and description. Product bundles in Zoho decompose into individual line items in Pipedrive. We import Products before Deals so that Deal-Product linking resolves at import time.

Pipedrive's deal-centric model does not include standalone Quote, Sales Order, or Invoice objects at the Essential and Advanced tiers. Quote data (line items, totals, status) migrates as custom Deal fields or as PDF-linked attachments stored in cloud storage with reference links in the Deal record. The customer's admin rebuilds the quoting workflow in Pipedrive using a dedicated add-on or external quoting tool if quoting is a core process.

Zoho custom modules migrate to Pipedrive custom objects if the destination account is on the Advanced tier or above, which supports custom objects. On lower tiers, custom module fields attach to the closest standard object (Person, Organization, Deal) as custom fields. We inspect the Zoho custom module schema via API before migration and map field types (lookup, picklist, currency, date) to Pipedrive equivalents during the schema design phase.

Zoho custom fields on every standard module map to Pipedrive custom fields on the equivalent object. Picklist values in Zoho map to Pipedrive picklist options. Currency fields map to Pipedrive decimal fields. Date fields map 1:1. Autonumber and Formula fields in Zoho cannot be created during migration and are documented in the scope with a rebuild recommendation.