Migrate from Plumb5 to Freshsales

Plumb5 Customer Profiles map directly to Freshsales Contacts. Standard fields including name, email, phone, and address migrate as typed Freshsales fields. Plumb5 behavioral score values migrate as a read-only numeric custom field plumb5_score__c. The customer's Plumb5 lifecycle stage migrates to the Freshsales Lifecycle Stage field with closest-match value mapping, with any Plumb5-only stage values stored as a secondary custom field plumb5_lifecycle__c for the admin to reassign post-migration.

Plumb5 stores business-level data as part of the unified Customer Profile rather than as a separate entity. We extract company-related properties (company name, industry, employee count, annual revenue) from each Customer Profile and create corresponding Freshsales Account records. The Account is created before the Contact so that the Account Lookup relationship is satisfied at the moment of Contact insert. Dedupe is performed on Account Name.

Plumb5 behavioral events (web visits, email opens, campaign clicks, offline interactions) migrate as Freshsales Task records attached to the corresponding Contact. Each Task receives a type label (web_visit, email_engagement, campaign_click, offline_interaction) via a custom field plumb5_event_type__c, preserving the event category. Timestamps migrate as ActivityDate and the original event timestamp stored in a custom field plumb5_event_time__c for chronological ordering. High-volume event migrations require batch chunking against Freshsales API limits.

Plumb5 tags each profile with a source channel (organic search, paid search, social, email, direct, referral). Channel attribution migrates as a Freshsales Lead Source value if the destination uses the standard field, or to a custom picklist field plumb5_channel__c if the customer's existing Freshsales Lead Source values are already in use. The admin chooses the target field during scoping. Multi-touch attribution data from Plumb5 (which may store first-touch and last-touch channel) migrates as separate custom fields.

Plumb5 Campaigns with associated audiences, goals, and performance metrics migrate to Freshsales Campaigns. Campaign membership (which Contacts were part of which Campaign) migrates as Campaign Member records linked to the Contact and Campaign. Campaign status and type fields map from Plumb5 values to Freshsales Campaign Type picklist. Note that Plumb5 campaign automation rules tied to these campaigns require separate rebuild documentation and do not migrate as active workflows.

Plumb5 auto-segmentation scores are derived from a rules engine specific to the platform and cannot transfer as executable logic. We extract the last-recorded numeric score for each Customer Profile and store it as a Freshsales custom field plumb5_score__c marked read-only post-migration. The customer's Freshsales team rebuilds equivalent scoring using Freddy AI rules after migration. We document the original Plumb5 score definitions during discovery so the rebuild team has a reference.

Plumb5 dynamic segments generated by auto-segmentation are evaluated continuously on the source platform and cannot transfer as live segment definitions. We export each Contact's segment membership as of the migration snapshot date and store segment names in a custom multi-select picklist field plumb5_segments__c or as Contact List memberships in Freshsales, depending on the customer's usage pattern. Post-migration, Freshsales Static Lists replace the static memberships and Freddy AI Rules rebuild the dynamic classification.

Plumb5 user-defined fields extending the standard Customer Profile schema migrate to Freshsales custom fields created during the schema design phase. We discover all Plumb5 custom properties during the schema audit, map each to an equivalent Freshsales field type (text, number, date, picklist, multi-select picklist, checkbox, phone, url), provision the fields in Freshsales before migration, and then import data into them. Any Plumb5 custom field without a Freshsales native equivalent maps to a text custom field and is flagged in the migration inventory.