Migrate from Plumb5 to Nutshell

Plumb5 Customer Profiles with name, email, phone, and standard metadata map directly to Nutshell People records. Company affiliation on each profile maps to a Nutshell Company record. We use email as the dedupe key during import and create the Company record first so that the People-Company association is satisfied at insert time. Any Plumb5 profile that lacks a company association becomes a standalone Person in Nutshell. Custom profile fields discovered during the schema audit phase migrate as Nutshell custom fields on the Person or Company object.

Plumb5 Behavioral Events (web sessions, email interactions, campaign touches, offline events) are timestamped interaction records that have no direct Nutshell equivalent because Nutshell does not have a native event stream object. We migrate the most recent meaningful events as Nutshell Task records with a custom event_type field indicating the interaction category (web_session, email_open, campaign_click, offline_touch). Each Task is linked to the corresponding Person or Company. Historical event volume can be significant; we batch import via Nutshell's API with rate-limit handling and flag the event count during scoping so the customer understands the post-migration record volume.

Plumb5 web and mobile session records contain device, geography, referrer, and session duration data. Nutshell does not store session-level records. We map the most recent session attributes (device_type, last_session_referrer, last_session_geo, last_session_duration) to custom fields on the Person record. Earlier session history migrates as Task activity log entries if the customer specifies scope, or is summarized and stored as metadata properties if the event volume is large.

Plumb5 tags every interaction with a source channel (organic search, paid search, social, email, direct, referral). Channel attribution is stored as a property on the Customer Profile. We preserve this as a Nutshell Tag on the Person record or as a single-select custom field depending on whether the customer prefers tag-based segmentation or structured field reporting. The channel value migrates with the profile record and does not require a separate import phase.

Plumb5 Campaigns with associated audiences and performance metrics have no native Nutshell Campaign object. Nutshell is a sales CRM, not a marketing automation platform, and does not include campaign management functionality. We migrate campaign names as Tags on the associated Person records, with campaign membership preserved as a multi-tag list per contact. Campaign goals, budget, and performance metrics (impressions, opens, clicks) have no destination field; we document these values in a separate campaign inventory sheet for the customer's admin to reference if they implement campaign tracking in a separate marketing tool.

Plumb5 auto-segmentation and scoring models generate numeric conversion propensity scores per profile. These score values are static at any given moment and we migrate them as a Nutshell custom numeric field (plumb5_score__c) on the Person record. The scoring logic itself is a rules-engine artifact that cannot be transferred; we document the score definition ranges and threshold values during discovery so the customer's Nutshell admin has a reference for rebuilding scoring in Nutshell's workflow rules or a third-party scoring tool if needed.

Plumb5 auto-segmentation generates dynamic segments based on behavioral criteria. Nutshell has no dynamic segmentation engine. We export segment membership for each profile at migration time and create static Tags in Nutshell representing each Plumb5 segment (e.g., high_intent, repeat_visitor, churned). These tags are read-only post-migration; any new dynamic segmentation logic must be rebuilt in Nutshell using Nutshell's workflow rules or a connected marketing automation tool.

Plumb5 user-defined fields extending the standard Customer Profile schema migrate to Nutshell custom fields on the appropriate object (Person, Company, or Lead). We discover all custom properties during the schema audit phase, map them to the closest Nutshell native field type (text, number, currency, date, checkbox, single-select, multi-select), and pre-create any missing custom fields in Nutshell before the data import begins. Nutshell's Enterprise plan offers unlimited custom fields; the Foundation and Growth plans have limits that we verify during scoping.

Plumb5 defines a proprietary customer lifecycle progression from anonymous visitor to brand advocate. Nutshell does not have a native lifecycle stage field. We map the Plumb5 lifecycle value to a Nutshell custom single-select field (lifecycle_stage__c) on the Person record, using the closest available label from the customer's existing Plumb5 stage definitions. Stages with no clear Nutshell equivalent are flagged in the mapping document for the customer to decide on post-migration naming. The anonymous-to-advocate model does not map to Nutshell's Lead Status because those statuses represent sales qualification, not lifecycle position.