Migrate from Zoho Marketing Plus to Pipedrive

Zoho Marketing Plus Contacts map to Pipedrive Person records with direct field mapping for first name, last name, email, phone, and address properties. Custom Contact fields created via the Marketing Automation API migrate as Pipedrive custom fields scoped to Person. We resolve Organisation membership using Zoho's contact-company linkage by matching domain names to Pipedrive Organisation records, creating the Organisation first if it does not exist. Multi-brand scoping from Zoho is preserved as a custom picklist field brand_segment__c on Person.

Zoho Campaigns have no native Pipedrive equivalent because Pipedrive is a sales CRM without a campaign management module. We export Zoho Campaign metadata (name, type, channel, start/end dates, audience size, performance metrics) as structured JSON and create a Pipedrive Activity record of type Note attached to each relevant Person and Organisation, with the campaign description preserved in the note body. Campaign audience lists become filtered Pipedrive views. The customer rebuilds campaign execution tracking in their chosen email marketing tool post-migration.

Zoho Deals map directly to Pipedrive Deals with Deal Title, Value, Stage, Expected Close Date, Owner, and custom fields preserved. Pipeline and stage mapping is computed at migration time using Zoho's pipeline and stage identifiers. Pipedrive's visual deal stages (draggable kanban columns) replace Zoho's pipeline view; we configure the equivalent stage labels in Pipedrive before migration so deal history is meaningful immediately on cutover.

Zoho Organisations (from the CRM module if used alongside Marketing Plus) map to Pipedrive Organisations. Company Name maps to Organisation Name, industry, employee count, website, and address fields migrate directly. Organisation is created before any Contact or Deal import so that the Organisation-Person-Deal relationship hierarchy is intact from the first insert.

Zoho email engagements migrate to Pipedrive Activity records of type email. Subject, body (HTML preserved), timestamp, sender, and recipient fields migrate. The activity is linked to the resolved Person (WhoId) and the related Organisation or Deal (WhatId). Email engagement metrics such as open and click tracking are stored as custom activity fields since Pipedrive does not natively track email opens and clicks without a connected inbox integration.

Zoho call engagements migrate to Pipedrive Activity records with subtype set to Call. Call duration, disposition, recording URL (if available), and timestamp migrate as custom fields on the activity. Activity ordering in the timeline is preserved by setting the Pipedrive Activity date to the original Zoho timestamp. Owner assignment migrates by resolving the Zoho marketer ID to the Pipedrive User email match.

Zoho meeting engagements migrate to Pipedrive Activity records of type Meeting. Title, start time, end time, location, attendees, and notes migrate directly. Attendee email addresses are cross-referenced against the migrated Person records to link meeting participants to Pipedrive Person activities. Meeting notes migrate as the activity description field.

Zoho task engagements migrate to Pipedrive Activity records of type Task. Subject, due date, priority, status (done/not done), and assigned owner migrate directly. Completed status from Zoho maps to Pipedrive Done=true. Task notes migrate as the activity description field. The task is linked to the resolved Person or Organisation as the activity target.

Zoho Journeys have no direct Pipedrive equivalent. Pipedrive's Workflow Automation (Growth plan and above) supports 3 if/else branching steps per workflow, which is a subset of Zoho's multi-step visual journey builder. We do not migrate Journeys as code. We export Journey configurations as JSON metadata including triggers, conditions, delays, and actions, and deliver a written handoff document mapping each Zoho Journey step to a recommended Pipedrive Workflow configuration. The customer's admin or a Pipedrive partner rebuilds the automation post-migration.

Zoho Event records (registrations, session data, speaker info, attendee lists) and Webinar attendee records have no Pipedrive equivalent. We export event and webinar attendee data as structured CSV and JSON including registration status, session attendance, and session-level engagement data. Event metadata (event name, date, venue, ticket type) is preserved as Pipedrive Activity Note records for each attendee Person. The customer rebuilds event management in a dedicated tool (Eventbrite, Luma, or similar) post-migration.

Custom fields created via the Zoho Marketing Automation API v1 map to Pipedrive Person custom fields with equivalent data types: text fields to text, picklists to drop-down, multiselect to multiselect, checkboxes to boolean, date fields to date. Pipedrive's custom field limit varies by plan (Growth and above recommended for migrations exceeding 20 custom fields). We validate the customer's Pipedrive plan against the total custom field count before migration begins.