Migrate from Plumb5 to Salesforce Sales Cloud

Plumb5 Customer Profiles with lifecycle stage of Anonymous Visitor, Subscriber, or Lead map to Salesforce Lead. Profiles with lifecycle stage of MQL, SQL, Customer, or Advocate map to Salesforce Contact tied to a Salesforce Account. We compute the split using Plumb5's lifecycle stage property and a customer-provided stage-to-status matrix. The original Plumb5 lifecycle stage is preserved in a custom field p5_original_lifecycle__c on both Lead and Contact for audit and reporting continuity.

Plumb5 profiles contain company-level metadata (industry, employee count, annual revenue) that maps to Salesforce Account fields. We extract these as separate Account records created before Contact import, using the profile's company identifier as the Account Name and website/domain as the Account Website. Account is the parent of every Contact import so that the AccountId lookup is satisfied at insert time.

Plumb5 Behavioral Events (web visits, email opens, form submissions, session interactions) migrate as Salesforce Task records with a custom event_type__c picklist preserving the event category. High-volume event migration uses Salesforce Bulk API 2.0 with batch chunking (10,000 records per batch), exponential backoff on API limit responses, and parent-record resolution linking each event to the correct Contact or Lead via WhoId.

Plumb5 Session Data contains device type, geography, referrer URL, session duration, and entry page. Destination Salesforce orgs store session-level data differently depending on edition and add-ons. We map session records to a custom Task with session-specific fields (session_device__c, session_geo__c, session_referrer__c, session_duration_seconds__c) and link via WhoId to the Contact or Lead. Session data exceeding 200 characters in any field is stored as a ContentNote attached via ContentDocumentLink.

Plumb5 tags each profile interaction with a channel source (organic search, paid search, social, email, direct, referral). Channel attribution is stored as a tag array on the profile. We map channel sources to Salesforce Topics using the Topic and TopicAssignment objects for cross-object queries, or to a custom multi-select picklist p5_channel_source__c on Lead/Contact depending on the customer's reporting preference selected during scoping.

Plumb5 Campaigns with associated audience lists migrate to Salesforce Campaign records. Each campaign's associated contact memberships map to Salesforce CampaignMember records linking the Contact or Lead to the Campaign. Plumb5 campaign performance metrics (opens, clicks, conversions) are stored as custom numeric fields on the Salesforce Campaign record rather than as native campaign reporting.

Plumb5 auto-segmentation models generate dynamic segments based on behavioral scoring rules. Since Salesforce does not have a native dynamic segmentation engine, we migrate the current segment membership as static records. Each Plumb5 segment becomes a Salesforce Campaign (for list-based usage) or a custom Segment_Membership__c object with a Contact lookup and segment_name__c field, giving the customer a rebuild target for Flow-based segmentation post-migration.

Plumb5 propensity and engagement scores migrate as read-only custom numeric fields (p5_propensity_score__c, p5_engagement_score__c) on the Contact and Lead objects. The numeric value transfers; the rule engine that computed it does not. We document the score definitions during discovery so the customer's Salesforce team has a reference for rebuilding them as Salesforce Flow formulas, Einstein Score builders, or Marketing Cloud Account Engagement scoring models post-migration.

Plumb5 user-defined fields extending the standard profile schema migrate to Salesforce custom fields with equivalent API names (with __c suffix per Salesforce convention). Field type mapping follows: text to Text(255) or Long Text Area; numeric to Number; date to Date; boolean to Checkbox; list values to Picklist or Multi-Select Picklist. Custom field creation is completed in the destination Salesforce Sandbox before any data import begins.

Plumb5's Recency, Frequency, Monetary (RFM) and sentiment scores are derived aggregate values stored per profile. We map these to custom Number fields (p5_recency_score__c, p5_frequency_score__c, p5_monetary_value__c, p5_sentiment_score__c) on the Contact. These are read-only in Salesforce and serve as reference data for post-migration segmentation and reporting rather than live scoring inputs.

Plumb5's proprietary lifecycle progression (Anonymous Visitor to Brand Advocate) maps to Salesforce Lead Status on Lead records, with a custom picklist p5_lifecycle_stage__c on both Lead and Contact preserving the original Plumb5 value. Any Plumb5 lifecycle stage with no direct Salesforce equivalent is flagged during scoping for the customer to define a post-migration naming convention, ensuring no stage data is silently dropped.

Plumb5 Owner assignments on profiles, campaigns, and events map to Salesforce User records by email match. We extract every distinct owner referenced on migrating records and resolve against the destination org's User table. Any owner without a matching Salesforce User enters a reconciliation queue for the customer's admin to provision before the corresponding records are imported.