Migrate from Listrak to Nutshell

Listrak Contacts map to Nutshell People. The Listrak email address becomes the Person's email field, first and last name map directly, and the original opt-in date (optin_date or custom property) is written to a Nutshell custom field for compliance audit. Phone number migrates to the Person's phone field. We use email address as the dedupe key so duplicate Listrak records resolve to a single Nutshell Person on re-import.

Listrak Company records map directly to Nutshell Company. The Listrak company name becomes the Company name, and any custom properties map to Nutshell Company custom fields. Company is created before Person import so that the account relationship is satisfied at Person insert if a link field exists in the destination Nutshell configuration.

Listrak mobile subscribers require mobile_number in text data type (not numeric string or varchar) per Nutshell's Engagement Suite requirements. We validate field type before load and flag any numeric-only exports that lack the proper text format. Original opt-in date for mobile must transfer to a custom date field. We load mobile subscribers after verifying the field type, because a numeric-only import will fail silently and the records will not appear in the Engagement SMS inbox.

Listrak suppression and unsubscribe lists export separately from active contacts. We load suppressions into Nutshell's unsubscribe list before any active contact import to prevent the platform from sending to opted-out addresses. Listrak's own migration documentation requires written confirmation that the suppression list has been scrubbed; we validate this condition before processing any mobile contact loads.

Listrak custom contact properties (retention score, customer tier, acquisition channel) map to Nutshell People custom fields. We create the Nutshell custom field first, matching the Listrak property type (text, date, currency, picklist) to the equivalent Nutshell field type. Listrak custom fields that appear only in the UI and not in the API export are flagged and scoped separately; the customer provides API access or the field is noted as requiring post-migration data entry.

Listrak segments filter by email behavior, SMS engagement, and channel subscription status. These segment definitions do not export as transferable objects. We document each Listrak segment's filter logic (field, operator, value) and map it to an equivalent Nutshell Saved Filter for the customer's admin to configure post-migration. The filter syntax differs between platforms; a Listrak 'has opened any email in last 30 days' segment requires a different build in Nutshell's filter UI.

Listrak Experience Builder email templates export as raw HTML or must be manually rebuilt. Nutshell's email templates use a drag-and-drop editor that is not compatible with Listrak's HTML output. We export Listrak templates as raw HTML and recommend rebuilding in Nutshell's editor for mobile responsiveness and deliverability optimization. Raw HTML import is available but often carries rendering inconsistencies that affect inbox placement.

Listrak Journey Hub automations (cart abandonment, browse recovery, replenishment sequences) represent multi-step, multi-channel logic that does not export as a transferable object. We document the full automation tree including triggers, conditions, time delays, and channel sequence steps, and deliver this as a written inventory for the customer's admin to rebuild in Nutshell's Pipeline Automation or Email Sequence editor.