Migrate from Plumb5 to Zoho CRM

Plumb5's unified Customer Profile maps to Zoho CRM Contact and Account. The primary contact fields (name, email, phone, address) split across Contact; company-level data (company name, domain, industry, employee count) populates Account. Plumb5's contact_id becomes a custom field p5_contact_id__c for deduplication and future sync. If the customer has many anonymous visitor profiles with no email, we preserve them as Contacts with a flag indicating no email and store any available behavioral data as custom fields.

Plumb5 timestamped behavioral events (page views, email clicks, form submissions, app interactions) map to Zoho CRM Activity records. We map web and email events to Tasks with a custom activity type field, preserving the Plumb5 event name, timestamp, and URL. High-frequency session events may be consolidated into daily rollup records to avoid exceeding Zoho CRM's bulk import row limits per batch.

Web and mobile session data (device type, geography, referrer, session duration, utm_source) from Plumb5 maps to custom fields on the Contact record (p5_last_device__c, p5_last_location__c, p5_utm_source__c). Zoho CRM does not natively store raw session data, so we preserve the most recent session context as read-only properties rather than attempting to create a session history module.

Plumb5 tags each interaction with a source channel (organic search, paid search, social, email, direct, referral). We preserve this as both a Zoho CRM Tag on the Contact record and as a custom picklist field p5_channel_source__c. The customer's admin configures the picklist values during schema setup based on the discovered Plumb5 channel taxonomy.

Plumb5 Campaign records (with associated audiences, goals, and performance metrics) map to Zoho CRM Campaign records. Campaign Name, Type, Status, Start Date, and End Date migrate directly. Historical performance metrics (opens, clicks, conversions) store in custom numeric fields on the Campaign record. Campaign membership (which contacts were in which campaign) migrates as Campaign Member records linking Contact to Campaign.

Plumb5 auto-segmentation generates dynamic segment memberships based on behavioral scoring. Zoho CRM handles segmentation via Filters (dynamic, recalculated on access) and Groups (static lists). We migrate segment membership as Zoho Static Groups at migration time, with the segment definition documented for the customer's Zoho admin to rebuild as Filters using Zoho CRM's filter builder. Dynamic segment recreation is out of migration scope.

Plumb5 numeric score values stored per profile migrate to a custom numeric field p5_behavioral_score__c on the Contact. The Plumb5 scoring algorithm itself (weighted rules, thresholds, recalculation logic) does not transfer as executable code. We document each Plumb5 score definition and threshold during discovery and deliver a written scoring model reference so the customer's Zoho admin can rebuild equivalent scoring using Zoho CRM Formula Fields, Validation Rules, or Zia (if Enterprise or above) in a separate configuration engagement.

Plumb5 user-defined fields extending the standard profile schema map to Zoho CRM custom fields. We discover all custom properties during the schema audit phase, determine the equivalent Zoho field type (text, picklist, numeric, date, checkbox), and create the corresponding custom field in the Zoho CRM module before migration. Custom field API names follow Zoho's naming conventions with underscores. Custom field dependencies on Plumb5-specific picklist values are resolved by creating matching picklist options in Zoho during schema setup.

Plumb5 aggregates RFM (Recency, Frequency, Monetary) metrics and sentiment scores per customer. These derived values migrate as read-only custom numeric fields (p5_recency__c, p5_frequency__c, p5_monetary_value__c, p5_sentiment_score__c) on the Contact. Zoho CRM does not natively recalculate RFM; the customer's admin can rebuild RFM logic in Zoho Analytics or via scheduled Deluge scripts post-migration if ongoing recalculation is required.

Plumb5 defines a proprietary lifecycle from anonymous visitor through brand advocate. We map Plumb5 lifecycle values to the closest Zoho CRM equivalent. For organizations that use Zoho Leads for unqualified prospects, lifecycle stages map to Lead Status values (New, Contacted, Qualified, Unqualified). For organizations using only Contacts, we create a custom picklist field p5_lifecycle_stage__c with Plumb5's values and document any lifecycle stages that have no Zoho equivalent for the customer's admin to rename post-migration.