Migrate from Plumb5 to Pipedrive

Plumb5 Customer Profiles (name, email, phone, metadata) map to Pipedrive Person records. Standard fields migrate directly. Any behavioral score stored on the profile migrates to a custom numeric field pipedrive_score__c. Lifecycle stage from Plumb5 migrates to a custom picklist field plumb5_lifecycle__c for post-migration review. Dedupe key is email address.

Plumb5 profiles may carry company affiliation data. We create a Pipedrive Organization record by parsing the company_name property or domain from email where available, then link the Person to the Organization via the org_id field. If no company data exists on the profile, no Organization is created and the Person remains unlinked, which the customer's admin reviews post-migration.

Plumb5 behavioral events (web visits, email opens, form submissions, offline interactions) have no direct Pipedrive equivalent since Pipedrive tracks Activities at the Person or Deal level, not across anonymous touchpoints. We split events into two: high-value intent signals (demo requests, pricing page visits, form submissions) migrate as Pipedrive Activities with a custom event_type__c field; anonymous session data is mapped to a custom long-text field on the Person record as a comma-separated last_activity_context__c string. Full event history is preserved in an archive CSV delivered alongside the migration.

Plumb5 tags each profile with a source channel (organic search, paid, social, email, direct, offline). Channel attribution migrates to a Pipedrive Person custom field named channel_source__c as a single-select picklist, preserving the last-known attributed channel. If multiple channels are recorded, the most recent becomes the mapped value and prior channels are appended to channel_history__c.

Plumb5 Campaigns (with associated audience lists, goals, and performance metrics) map to Pipedrive Deals. The campaign name becomes the Deal title, campaign start and end dates map to expected_close_date and a custom campaign_start__c field, and campaign membership is preserved by linking the Deal to the associated Person records. Pipedrive supports multiple Deal pipelines, so multi-campaign structures can map to separate pipelines via custom field campaign_id__c.

Plumb5 campaign membership (which profiles were added to which campaign) maps to Pipedrive as Deal-Person activity associations. Each Person linked to a campaign receives a Deal record, and the Deal-Person relationship is created via the Pipedrive Deal-Person association API. If a Person belongs to multiple campaigns, they receive multiple Deal records.

Plumb5 auto-segmentation models generate dynamic segment memberships. Since Pipedrive handles dynamic segments differently (using filters and smart lists), we migrate segment membership as static Person lists in Pipedrive. We export the last-known segment membership snapshot, create a Pipedrive Person custom field segment__c with the segment name as the value, and document the segment definition so the customer's Pipedrive admin can recreate the dynamic logic as a filter or list.

Plumb5 behavioral scoring values (conversion propensity, engagement score, profitability index) migrate to Pipedrive Person custom fields (e.g., plumb5_engagement_score__c, plumb5_profitability_index__c) as read-only numeric fields. The scoring algorithm logic does not transfer; we document the Plumb5 score definitions during discovery and deliver a scoring model reference sheet for the admin to implement using Pipedrive Workflow Automation if applicable.

Plumb5 user-defined custom fields extending the profile schema map to Pipedrive custom fields on the Person object. We discover all custom properties during the schema audit phase, map their data types (text, number, date, picklist) to equivalent Pipedrive field types, create the fields in Pipedrive before migration, and apply field-level mapping during import. Custom fields with no Pipedrive equivalent are flagged for the admin to configure post-migration.

Plumb5 aggregated KPIs per customer (recency, frequency, monetary value, sentiment scores) migrate to Pipedrive Person custom fields as read-only numeric properties (rfm_recency__c, rfm_frequency__c, rfm_monetary__c, sentiment_score__c). These are derived values preserved as reference data; Pipedrive does not have native RFM or sentiment scoring so these remain informational fields on the Person record.

Plumb5 lifecycle stages (anonymous visitor through brand advocate) have no direct Pipedrive equivalent. We map the last-known lifecycle stage to a Pipedrive Person custom field plumb5_lifecycle_stage__c as a picklist, and where lifecycle aligns with a sales milestone, we also create a corresponding Deal stage in the target pipeline. Stages with no sales-process equivalent (e.g., evangelist) are flagged in the lifecycle mapping reference delivered post-migration.

Plumb5 web and mobile session records (device, geography, referrer, duration) are not a native Pipedrive concept. We archive session data as a JSON blob in a Person custom field session_archive__c and deliver the full session dataset as a supplementary CSV. If the customer requires session data in a queryable format, we recommend a separate analytics integration (e.g., Segment, Amplitude) post-migration.