Migrate from Symplify Communication to Pipedrive

Symplify Contact records map 1:1 to Pipedrive Person. We export all standard contact fields (email, first_name, last_name, phone, mobile, address) via the Symplify REST API and load them as typed Pipedrive Person fields. The Symplify originalId is stored in a custom field symplify_original_id__c for audit and cross-reference. Email addresses serve as the dedupe key during import. Organization lookup is resolved after Organizations are created from any associated Company records.

Symplify Company records (if present in the customer's data) map to Pipedrive Organization. Company name, domain, address, and phone fields map directly. Organization is created before any associated Person import so that the org_id lookup on Person is satisfied at the moment of insert. If the customer has no Companies in Symplify, Persons are imported as standalone records without an Organization link.

Symplify Lists are static contact groupings with names and optional segment rules. We export list membership and recreate list structures in Pipedrive as either static Person lists (for small lists under 500 members) or as saved filter views (for large lists with dynamic segment logic). The customer chooses the strategy during scoping based on how lists are used in their Pipedrive workflow.

Symplify Campaigns have no direct Pipedrive equivalent because Pipedrive Campaigns (add-on) are a separate feature not present on all tiers. For customers who track campaign performance as deal-equivalent data in DataDocs, we synthesize Deals from DataDoc records with Campaign context. For customers tracking campaign-level metrics only, we export campaign metadata (name, send date, channel) and message-level statistics (sents, opens, clicks) as a written Campaign Performance Summary rather than live Pipedrive records.

DataDocs store relational data (purchase history, events, bookings) linked to contacts by originalId. Document Types must be audited during discovery because they define mandatory fields and any JSON Schema. For DataDocs with flat, single-record structure, we map fields to custom fields on Pipedrive Person. For DataDocs with multi-row or nested structure, we create a Pipedrive custom object with matching field types and a Person lookup relationship. Orphaned DataDocs (those with no valid Document Type) are flagged in the discovery report and excluded from migration unless the customer remediates the schema.

Symplify open events track per-message engagement with timestamps. Pipedrive has no native open-tracking object on Person or Deal. We export open records and surface them as a structured engagement summary (open rate, unique opens, open timestamps) per campaign and per contact, delivered as a written report for the customer's admin to associate with Pipedrive records manually or via custom reporting.

Symplify click events track URL-level engagement per message with timestamps and click URLs. Pipedrive does not store click data natively. We export click records and synthesize them into a per-campaign click-through summary delivered as a written report, with URL-level detail available for the customer's analytics team to ingest into a BI tool if needed.

Symplify sent records track every dispatch per contact per message with delivery timestamps. Pipedrive has no native sent event object. We export the complete send log and synthesize it into a campaign send summary report delivered alongside the migration, with per-contact send history available as a CSV supplement for manual import or enrichment if the customer requires it.

Symplify Hard Bounce records mark permanently undeliverable contacts. We export hard bounce status by contact and set the Pipedrive Person's email_failures field or the opt_out flag to true, protecting deliverability in Pipedrive's email tools. The original Symplify bounce reason code is stored in a custom field symplify_bounce_reason__c for audit purposes.

Symplify Optout records track unsubscribe preferences with timestamps. We export all optout events and set the Pipedrive Person's opt_out field to true. The original optout timestamp is stored in a custom field symplify_unsubscribed_at__c. This ensures compliance with unsubscribe request tracking and prevents Pipedrive from re-sending to suppressed contacts via its native email tools.