Migrate from Listrak to Pipedrive

Listrak's unified contact profile maps to Pipedrive Person. Email address becomes the Person's email field and serves as the dedupe key during import. First name, last name, and phone migrate directly. Custom contact properties (lifecycle stage, acquisition source, behavioral scores) migrate to Pipedrive custom fields on Person, with type validation before insert. The Listrak contact ID is preserved in a custom field listrak_contact_id__c for audit traceability.

Listrak contact records with an associated company map to Pipedrive Organization, created before Person import so that the organization_id lookup is satisfied at insert time. The Listrak company name becomes the Organization name, and the company domain becomes the Website field. Person-Organization associations are resolved via company name match and written as Organization links on the Person record.

Listrak mobile subscribers require opt-in scrubbing before any export, per Listrak's onboarding requirements. We validate that opted-out contacts are excluded before loading. The mobile number migrates to Pipedrive's phone field on Person with type validation to ensure it imports as text. Original opt-in date migrates to a custom field mobile_optin_date__c. Listrak's SMS engagement flags (delivered, clicked, replied) become custom fields on Person since Pipedrive has no native SMS subscriber concept.

Listrak suppression and unsubscribe lists must load into Pipedrive before active contacts to establish compliance. Each suppressed email address gets HasOptedOutOfEmail set to true on the Person record. If the contact does not yet exist in Pipedrive, we create a minimal Person record with email and the opt-out flag so that Pipedrive's email sending respects the suppression on first send. Suppression date and source (email, SMS, or both) migrate to custom fields for audit.

Listrak segments filter contacts by email behavior, SMS engagement, and channel subscription status. Pipedrive does not have a native audience segment concept. We map each Listrak segment's filter criteria to equivalent Pipedrive custom field values and filter logic, noting that Pipedrive's filtering operates on individual record fields rather than behavioral event histories. Segments requiring cross-field behavioral logic (recency/frequency scoring) are documented as custom report filters or CRM activity segments for the admin to implement post-migration.

Listrak Experience Builder templates export as raw HTML or require manual recreation. We recommend documenting template structure, content blocks, and personalization tokens in a written template inventory rather than raw HTML import, which carries rendering inconsistencies. Pipedrive's email template editor supports basic HTML but not the multi-step conditional content that Listrak's builder supports. The template inventory is handed off for rebuild in Pipedrive or a connected email tool.

Listrak Journey Hub automations (cart abandonment, browse recovery, replenishment, win-back sequences) represent multi-step, multi-channel logic that does not export as transferable objects. Pipedrive's workflow automation is scoped to CRM record actions (deal stage changes, task creation, deal updates, owner assignment) and does not support cross-channel campaign orchestration. We document the full automation tree including triggers, conditions, time delays, and channel sequences, mapping each step to Pipedrive's workflow equivalent where applicable.

Listrak custom contact properties vary in API accessibility: some are available via standard export and some are UI-only fields that require manual extraction. We identify which custom properties appear in the Listrak API versus only in the UI during discovery, flag UI-only fields for manual export, and map all accessible properties to Pipedrive custom fields with matched data types (text, number, date, checkbox, picklist). Pipedrive enforces field type validation on import, so mismatched types are corrected in the mapping workbook before production load.

Listrak campaign performance reports export as flat CSV files on the nightly SFTP schedule. We capture the export configuration during discovery, extract historical reports that exist before the migration cutover, and reload them into Pipedrive's reporting dashboard as CSV imports or as structured data in a custom fields set for historical reference. Real-time analytics reports do not transfer as Pipedrive report objects.

Listrak tracks acquisition channel and keyword campaign sources for mobile subscribers, stored in a separate export that must be joined on mobile number. We extract this data, deduplicate by mobile number, and write the acquisition channel to a custom field acquisition_source__c on the Person record. Attribution data (UTM parameters, keyword, campaign) migrates to custom fields if available in the Listrak export.