Migrate from Listrak to Microsoft Dynamics 365 Sales

Listrak's unified contact profile must split into Dynamics 365 Lead and Contact objects. We apply a split rule during migration scoping based on whether the contact has an associated sales opportunity in Listrak. Contacts with active engagement history and no opportunity map to Lead; contacts with closed-won deals or ongoing opportunities map to Contact attached to an Account. Original opt-in date and email subscription status migrate to Lead or Contact fields, with suppression status checked against the Listrak suppression list before insert.

Mobile subscribers from Listrak migrate as Dynamics 365 Contact records with the mobile phone field populated. Listrak requires opt-in scrubbing before any mobile export; we validate this condition before loading. Mobile number format must be preserved exactly as exported from Listrak since Dynamics 365 does not auto-format international numbers. Opt-in date from Listrak becomes a custom field on Contact; opt-out date becomes a related record or custom field for compliance tracking.

Suppression and unsubscribe lists from Listrak load into Dynamics 365 before any active contact migration. We set HasOptedOutOfEmail = true for each suppressed email address and populate a custom suppression_date field with the original Listrak suppression timestamp. This prevents Microsoft Dynamics 365 Sales from inadvertently sending to opted-out contacts on day one. Suppression lists must load first in the migration sequence so that the compliance posture is established before active records enter.

Listrak company records map to Dynamics 365 Account. Company name becomes the Account Name field; domain maps to Website. We use company name as the dedupe key during import. Account is created before any Contact or Lead import so that the AccountId lookup is satisfied at the moment of record insert.

Listrak segments filter by email behavior, SMS engagement, and channel subscription status. These filter rules do not export as portable logic. We document each Listrak segment definition (filters, conditions, and logic operators) and map it to a Dynamics 365 Marketing List with static membership populated from the migration data, or to a Power Automate flow that recreates the segment logic for ongoing maintenance. Filter syntax translation requires manual rebuild; we do not deliver live segment automation.

Listrak email templates export as raw HTML or must be manually rebuilt. We do not deliver raw HTML import into Dynamics 365 Email Templates because the HTML often carries rendering inconsistencies and lacks mobile responsiveness. We recommend rebuilding templates using Dynamics 365's email template editor or exporting the raw HTML to a design partner for mobile-optimized rebuild. We deliver a template inventory with screenshots and HTML assets for the customer's admin or design resource.

Listrak Journey Hub automations (cart abandonment, browse recovery, replenishment sequences) represent multi-step, multi-channel logic that does not transfer as code. We document each automation tree including triggers, conditions, time delays, and channel sequences. We map each step to a Power Automate equivalent for the customer's admin to rebuild. This documentation is delivered as a written handoff document and is explicitly out of scope for live automation migration.

Listrak custom contact properties migrate to Dynamics 365 custom fields on Lead or Contact. We create the custom field in Dynamics 365 during schema design, matching the Listrak property data type (text, number, date, boolean, or picklist) to the appropriate Dynamics field type. Some Listrak custom properties are only visible in the Listrak UI and not accessible via standard export; we flag these during scoping and note which require manual data entry or a custom Listrak API extraction.

Historical campaign performance data from Listrak exports as flat CSV on the nightly SFTP schedule. We capture the scheduled export configuration and extract available historical reports that exist before the migration cutover date. We deliver these as CSV files and a Power BI template that the customer's analyst can connect to the extracted data. Real-time campaign analytics do not migrate; Microsoft Dynamics 365 Sales reporting covers pipeline and sales activity from go-live onward.