Migrate from Plumb5 to HubSpot

Plumb5's unified customer profile maps to HubSpot Contact. Each Plumb5 customer record becomes one HubSpot contact, with the Plumb5 record ID preserved as Source_System_ID__c for traceability. Email, name, phone, and address fields map directly to HubSpot standard properties. If the Plumb5 profile contains custom properties, those are migrated as HubSpot custom contact properties, preserving data continuity for segmentation and reporting.

Plumb5 company data (firmographics, industry, employee count, revenue range) maps to HubSpot Company properties. When a Plumb5 customer is associated with multiple companies, the primary company link maps to the HubSpot contact's associated company; secondary associations become Company Contact Relationships in HubSpot.

Plumb5 session data (page views, device, geo, UTM source/medium/campaign) has no native HubSpot equivalent. FlitStack creates custom contact properties — Session_Count__c, Last_Session_Date__c, UTM_Source__c, Device_Type__c — to preserve behavioral context on each contact record. Session-level event logs are stored as a JSON or delimited custom property for reference.

Plumb5 generates real-time customer scores across multiple scoring dimensions. These scores are static at migration time — HubSpot does not run Plumb5's scoring model. We migrate the final score values to HubSpot custom Number properties (e.g., Plumb5_Score__c, Engagement_Score__c) so historical scoring context is available on each contact.

Plumb5 auto-segments contacts based on scoring model thresholds and behavioral rules. HubSpot Lists work differently — they are query-based and recalculate on access. We export Plumb5 segment definitions and contact memberships as a reference CSV. HubSpot Lists are rebuilt using the segment names as List titles and the Plumb5 criteria as filter rules inside HubSpot.

Plumb5 campaign membership tracks which customers received a specific campaign treatment. HubSpot has no native campaign membership concept at the Plumb5 level — we map Plumb5 campaign records to HubSpot Lists named after each campaign, with contact memberships preserved as List membership.

Plumb5 form submissions are captured as HubSpot form submissions on the contact record. The form name, submission timestamp, and field values map to HubSpot's form submission log — visible in the contact's activity timeline as a Form Submission event. Any custom fields included in the Plumb5 form are also transferred as HubSpot custom form fields, ensuring that non-standard data points are retained and can be used in HubSpot workflows and reports.

Plumb5 workflows (lead routing, email triggers, score-based actions) do not migrate. FlitStack exports the Plumb5 workflow definitions — trigger conditions, action steps, and branch logic — as a structured JSON reference document. Your HubSpot admin uses this to rebuild equivalent workflows inside HubSpot's workflow builder or Automation Platform.

Plumb5 KPI dashboard tile definitions (metric name, aggregation logic, display format) do not transfer. We export a snapshot of current KPI values at migration time as custom number properties on contacts and companies. HubSpot reports and dashboards are rebuilt from scratch using HubSpot's report builder, using the migrated properties as data sources.

Plumb5 file attachments on customer profiles are downloaded and re-uploaded to HubSpot Files, then linked back to the corresponding contact or company record. File size limits and format compatibility are validated before upload. Supported file types include PDF, images, spreadsheets, and documents, with a check performed against HubSpot's 250 MB per-file limit to avoid rejected uploads.