Migrate from Zymplify to Pipedrive

Zymplify Contact records with standard fields (name, email, phone, job title, role) map directly to Pipedrive Person records. The CDP Hub's data-cleansing status and enrichment source provenance migrate as custom fields on the Person record (e.g., enrichment_source__c, data_quality_status__c). Any deduplication decisions made in the Zymplify CDP Hub are preserved as a note on the Person record indicating which duplicate was retained.

Zymplify Company records map to Pipedrive Organization. The Company domain, industry, employee count, and revenue fields migrate to their Pipedrive equivalents. Bombora-powered intent scores and G2 Buyer Intent signal metadata (intent_topic, intent_strength, signal_source) migrate as custom fields on the Organization record. The original Zymplify intent data is treated as enrichment provenance rather than native Pipedrive data, and the custom fields carry the raw signal values for admin reference.

Zymplify Deal records map to Pipedrive Deal. The Zymplify pipeline stage assignment maps to a Pipedrive Pipeline and Stage. We preserve Zymplify's custom stage names as-is and configure the corresponding Pipedrive pipeline stages before import. Deal value, close date, owner, and associated Organization and Contact links migrate with full fidelity. Any Zymplify custom deal properties migrate as custom Deal fields in Pipedrive.

Zymplify's pipeline definitions become Pipedrive Pipelines. Each Zymplify pipeline stage maps to a Pipedrive Stage within the corresponding Pipeline. Stage ordering, probabilities, and open/closed/won/loss status are configured in Pipedrive before the Deal import begins. If Zymplify uses multiple pipelines, we create a separate Pipedrive Pipeline for each and assign the relevant Record Type.

Zymplify Sales Cadences are outreach sequences combining email steps, delays, and task actions. No direct equivalent exists in Pipedrive. We export the cadence structure (step order, step type, delay duration, task description) as a structured sequence definition document and create a rebuild plan for Pipedrive's Automation Rules or a third-party sequencing tool such as Mailshake, Lemlist, or Salesloft. The cadence records themselves do not migrate as executable automation; the handoff document gives the admin everything needed to rebuild.

Zymplify Marketing Workflows with triggers, conditions, and actions are Zymplify-native automation constructs with no direct Pipedrive equivalent. Pipedrive's Automation Rules handle basic record-triggered actions but do not replicate Zymplify's full workflow builder. We document each active workflow in a requirements spec including trigger event, condition branches, action list, and recommended Pipedrive Automation Rule or third-party tool equivalent. Workflow definitions do not migrate as code.

Zymplify customer health scores and churn risk indicators are calculated from platform-specific models that cannot be exported as structured objects. We extract the raw health metrics and risk signals as custom fields on the Organization record (e.g., health_score__c, churn_risk_indicator__c, last_health_check__c). The scoring model itself does not carry over; the customer's CS team rebuilds the scoring logic in Pipedrive using the raw signals as input data.

The Zymplify CDP Hub maintains list management and deduplication records including enrichment status, source-of-truth flags, and duplicate suppression decisions. We carry the cleansed contact data as standard Pipedrive Person fields and flag enrichment provenance in a custom field (e.g., enrichment_provenance__c, cdp_cleansed_date__c). Duplicate suppression decisions are preserved as notes on the retained Person record indicating which Zymplify entry was superseded.

Zymplify email engagements (sent, opened, clicked) map to Pipedrive Activity records with type = email. Subject, body, timestamp, and outcome (delivered, opened, bounced) migrate as Activity fields. Each Activity is linked to the corresponding Person and Organization via Pipedrive's activity assignment fields. Email content migrates as a formatted note attached to the Activity.

Zymplify call engagements map to Pipedrive Activity records with type = call. Call duration, disposition, outcome, and any notes from the call are preserved in the Activity record. Call recording URLs from Zymplify are noted in a custom field on the Activity since Pipedrive does not natively host call recordings. Activity timestamp preserves the original call date for timeline accuracy.

Zymplify meeting engagements (including video call and in-person meeting types) map to Pipedrive Activity records with type = meeting. Meeting title, date and time, location or video link, attendees, and outcome migrate as Activity fields. Attendees are linked to the corresponding Person records where email addresses match.

Zymplify Note engagements map to Pipedrive Notes attached to the relevant Person, Organization, or Deal record. Note content, author, and creation timestamp migrate directly. Notes with attachments are handled by migrating the attachment URL or filename as a note comment since Pipedrive Notes support text content with optional file attachments.