Migrate from Plumb5 to HighLevel

Plumb5 Customer Profiles map directly to GoHighLevel Contacts. Standard fields (name, email, phone, address) map to GoHighLevel's standard Contact properties using email as the dedupe key. Plumb5 custom properties discovered during schema audit map to GoHighLevel custom Contact fields with type preservation (text, number, date, dropdown). We resolve the owner reference by email match against GoHighLevel Users and flag any unmapped properties for scoping review.

Plumb5 behavioral events (web sessions, email opens, campaign interactions, offline touchpoints) migrate to GoHighLevel Tasks as a chronological engagement log attached to the Contact. Each event type (page_view, email_open, campaign_signup, etc.) maps to a custom Task subject prefix. We preserve the original timestamp as ActivityDate to maintain the chronological sequence. Events with no Contact match (anonymous visitor records) are held in a staging queue for review during cutover.

Plumb5 tags each interaction with a source channel (organic search, paid search, social, email, referral, direct, etc.). Channel attribution migrates to GoHighLevel Tags as tag strings on the Contact record. Multi-channel touchpoints (a contact who interacted via both email and paid search) result in multiple tags. The customer chooses whether to preserve full channel history as tags or consolidate to the most-recent channel during scoping.

Plumb5 marketing campaigns with associated audiences, goals, and performance metrics migrate to GoHighLevel Campaigns. We preserve campaign name, start and end dates, goal metrics, and contact membership counts. GoHighLevel Campaign membership is tracked via CampaignMember records linking Contacts to Campaigns. Note that campaign automation workflows tied to Plumb5 campaigns do not migrate; we document them separately for the customer's admin rebuild in GoHighLevel's workflow builder.

Plumb5's auto-segmentation and behavioral scoring models rate each profile with a numeric conversion propensity score. The score value at migration time migrates as a static read-only custom numeric field on the GoHighLevel Contact. The scoring rules engine itself does not transfer because it is a Plumb5-specific rules artifact; we document the score definitions (score ranges, thresholds, contributing factors) in a scoring-reference file so the customer's GoHighLevel admin has a rebuild specification for GoHighLevel's workflow-based scoring automation.

Plumb5 defines a proprietary lifecycle progression from anonymous visitor through brand advocate stages. GoHighLevel does not have a native lifecycle stage field. We map Plumb5 lifecycle values to a custom Contact field (text, read-only post-migration) and optionally as a Tag for dynamic segmentation use. Stages with no direct GoHighLevel equivalent are preserved with their original Plumb5 label and flagged in the handoff document for the customer to rename or remap post-migration.

Plumb5 auto-segmentation generates dynamic audience segments based on behavioral scoring rules. Since GoHighLevel handles dynamic segmentation differently (via workflow filters and tag-based lists), we migrate segment membership as static Tag strings on the relevant Contacts. Segment names map to tag group prefixes (e.g., HIGH_INTENT_Buyers, RECENT_INACTIVE_Leads). We document the original segment definitions so the customer can rebuild dynamic equivalents in GoHighLevel using workflow-triggered tag assignment.

Plumb5 session records contain device type, geography, referrer URL, and session duration. GoHighLevel Contacts do not have native session storage. We map the most recent session metadata to custom text fields on the Contact (last_session_device, last_session_geo, last_session_referrer). Historical session aggregates (total sessions, session frequency) migrate as custom numeric fields. Full session history migrates as Tasks with subject prefix SESSION_ to preserve the log without bloating Contact records.

Plumb5 stores derived engagement KPIs per customer: recency (days since last interaction), frequency (interaction count over period), monetary value (revenue attribution if available), and sentiment scores. These derived values migrate as read-only custom numeric fields on the GoHighLevel Contact. We note in the handoff that these fields are point-in-time values at migration time and will not update automatically in GoHighLevel without a workflow-based refresh mechanism.