Migrate from Listrak to HubSpot

Listrak contact records map 1:1 to HubSpot contacts. Every standard property (name, email, phone, address) migrates as the equivalent HubSpot property. Custom profile fields on the Listrak contact become HubSpot custom properties. Listrak's internal contact ID is stored as a custom field (listrak_id__c) for traceability and delta-run de-duplication.

Email address on the Listrak contact maps to HubSpot's email property. This is the primary key for contact matching during delta runs. Listrak supports multiple email addresses per contact in some tiers; the primary email is mapped, and secondary addresses are stored as HubSpot custom properties.

SMS-capable mobile numbers on the Listrak contact migrate to HubSpot's mobilephone property. HubSpot uses this field for SMS-based workflows, the mobile contact channel, and SMS marketing campaigns. Country code formatting is normalized to E.164 during migration if Listrak stores local formats, ensuring consistent international phone number representation across the migrated dataset.

Listrak contacts may carry a company or brand affiliation property even though Listrak has no formal account object. We extract these into HubSpot Companies, creating a Company record per unique brand name found across the contact list, then associate the corresponding contacts via HubSpot's primary company link.

Listrak audience segments (named subscriber lists) are converted to either a HubSpot contact property with multi-select values or static HubSpot lists. High-cardinality segments (thousands of unique values) are mapped as a custom multi-select property; low-cardinality segments are converted to HubSpot static lists.

Listrak's predictive engagement scoring or RFM (recency, frequency, monetary) scores stored on the contact profile migrate to HubSpot custom numeric properties. These custom fields are not native HubSpot properties and must be created in your destination account before migration begins. Once migrated, they feed into HubSpot's contact-scoring workflows and can be referenced in HubSpot's reporting and list segmentation tools post-migration.

Listrak's per-contact campaign interaction timestamps (last email open date, last email click date, last SMS send date, last SMS click date) migrate as HubSpot engagement events on the contact record. These populate HubSpot's timeline view so reps see the full interaction history from the Listrak period.

Listrak exports unsubscribed and suppressed contacts as a flat list. We cross-reference this against the contact universe: active contacts with a suppression entry are marked as unsubscribed in HubSpot (emailoptout = true), and the original Listrak opt-out date is preserved as a custom datetime property. Suppression list entries without a corresponding contact record are imported as a HubSpot suppression record.

Listrak campaign-level conversion data (total campaign revenue attributed, campaign name, send timestamp) per contact is extracted and stored as HubSpot custom properties on the contact. This preserves attribution data that would otherwise live only in Listrak reports. Multiple campaigns are appended as a JSON-formatted custom string property.

Listrak's journey enrollment state (which automation a contact is enrolled in, current step) has no native HubSpot equivalent. We store the journey names and last-step timestamp as custom contact properties for reference, but the automation logic must be rebuilt in HubSpot Workflows or Operations Hub post-migration.

Listrak contacts may carry an internal owner or assigned CSM. We resolve by email against HubSpot users. Unmatched owners are flagged and assigned to a fallback HubSpot user. Listrak does not expose a formal owner object, so this is a best-effort association based on any owner email fields present in the contact export.

Listrak stores the original SMS or email opt-in date per contact. We map this to a custom datetime property (listrak_optin_date__c) on the HubSpot contact. HubSpot's Createdate reflects the migration import date; the original opt-in date is preserved separately for compliance and re-engagement campaign targeting.

Listrak HTML email templates cannot be migrated as functional templates in HubSpot. We export the template HTML and provide it to your team as a rebuild reference for HubSpot's email template builder. Templates that use Listrak-specific dynamic content syntax (e.g., Listrak's personalization tokens) will need token substitution during rebuild.

Listrak Journey Hub workflows (abandoned cart flows, replenishment triggers, welcome series, win-back sequences) are platform-specific and do not export in a transferable format. We document each journey's trigger, steps, and timing as a written specification so your HubSpot admin can rebuild them in HubSpot Workflows or the new Journey Automation tool.

If Listrak contacts carry product interest or purchase history data (SKUs viewed, categories browsed, product affinity scores), these map to HubSpot custom contact properties. For purchase history, HubSpot Line Items or a Deal association can represent orders; we assess the source data shape during the discovery phase and recommend the best structure.