Migrate from Plumb5 to Twenty CRM

Plumb5 unified customer profiles map to Twenty CRM People records. The Plumb5 profile contains name, email, phone, and behavioral metadata. For profiles that represent organizations (B2B records with company-level data), we map to Twenty CRM Company records and link the People record via the Main Contact relationship. Email serves as the dedupe key. We preserve Plumb5's profile creation timestamp and last-modified timestamp as Twenty's createdAt and updatedAt fields. Custom properties on the Plumb5 profile migrate to Twenty custom fields on the People or Company object, created during the schema audit phase.

Plumb5 behavioral events (web, mobile, email, and offline touchpoints) migrate as Twenty CRM Task records attached to the corresponding People record. Each event type maps to a Task with a descriptive subject line, the original timestamp as ActivityDate, and the event metadata (channel, source, action) stored in custom Task fields. Session referrer, device type, and geography from Plumb5 migrate as additional custom fields. Because Twenty's Task object supports unlimited custom fields, we preserve event-level detail rather than aggregating into summary metrics.

Plumb5 session records (device, geography, referrer, duration) attach to the behavioral event record as custom fields on the Task. If a Plumb5 profile has session-level data without a corresponding behavioral event, we create a Task with a subject like 'Session Record' and populate the session metadata in custom fields. This ensures that channel attribution and session context are not lost even when a session did not produce a named event.

Plumb5 tags each interaction with a source channel (organic search, paid search, social, email, referral, direct). We map this to a custom picklist field on the People object named Channel_Source__c. For profiles with multiple channel touchpoints, we store the most recent channel as the primary value and document all attributed channels in a text field for the customer to reference during analysis.

Plumb5 marketing campaigns with associated audiences and goals map to Twenty CRM Opportunities if the campaign has a revenue or pipeline context, or to a custom Campaign object if the customer's Plumb5 campaigns track audience membership separately from revenue. Campaign membership (which People were in which Campaign) migrates as a custom multi-select picklist or as linked records via a custom Campaign_Membership__c junction object. Goals and performance metrics from Plumb5 migrate as custom fields on the destination object.

Plumb5 auto-segmentation models generate dynamic segments based on behavioral criteria. Twenty CRM does not have a dynamic segment engine. We migrate segment membership as a static tag stored in a custom picklist field (Segment_Membership__c) on the People record. We document each Plumb5 segment definition (criteria, conditions, scoring thresholds) in the handoff workbook so the customer's admin can recreate segment logic as Twenty CRM Views with filter conditions or as Workflow triggers.

Plumb5's behavioral scoring models produce numeric score values stored per profile. We migrate the last-known score as a custom numeric field named Behavioral_Score__c on the People object. The Plumb5 score definitions (which behaviors contribute which weight) are documented in the migration workbook for the customer to re-implement using Twenty CRM Workflows and custom formula fields. Score history over time does not migrate as a time-series; only the most recent snapshot value transfers.

Plumb5 aggregates engagement KPIs per customer (recency, frequency, monetary value, sentiment scores). These derived values migrate as read-only custom numeric fields on the People record (e.g., Recency_Score__c, Frequency_Score__c, Monetary_Value__c, Sentiment_Score__c). We flag these as derived values so the customer knows they represent a snapshot at migration time and may need refresh through a Twenty-native calculation if the customer implements a parallel metrics engine.

Plumb5 defines a proprietary lifecycle progression from anonymous visitor through brand advocate. Twenty CRM has no native lifecycle stage model. We map each Plumb5 lifecycle value to a custom picklist field named Lifecycle_Stage__c on the People record, using the closest semantic equivalent. Stages that have no direct Twenty analog are preserved verbatim and documented in the handoff workbook so the customer can rename or consolidate them post-migration.

Plumb5 user-defined fields extending the standard profile schema migrate to Twenty CRM custom fields on the corresponding standard or custom object. We discover all Plumb5 custom properties during the schema audit phase, map them to the equivalent Twenty field type (text, number, date, picklist, multi-select, checkbox), and pre-create them in the Twenty workspace before any data import. Fields that cannot map directly (e.g., Plumb5-specific data types without a Twenty equivalent) are documented for the customer to resolve during workspace configuration.