Migrate from Loyalistic to Microsoft Dynamics 365 Sales

Loyalistic Contacts with qualification signals (opened multiple emails, visited pricing page, or assigned to a segment indicating buying intent) map to Salesforce Lead. Loyalistic Contacts with an associated company name and explicit close or conversion signal map to Dynamics 365 Contact tied to an Account. We resolve the split at migration time using Loyalistic segment membership and tag lists as the qualification proxy, and preserve the original Loyalistic contact record ID in a custom field loyalistic_contact_id__c on both Lead and Contact for audit and cross-reference.

Loyalistic Customer Profiles aggregate contact details with enrichment data sourced from third-party providers. We extract the underlying contact fields and company name to create Dynamics 365 Account records, with enrichment provenance noted in a custom field enrichment_source__c. Because Loyalistic does not enforce a normalised Account-Contact relationship, we treat the company name as the dedupe key and attach all Contacts sharing that company name to the same Account during import.

Loyalistic Tags are flat labels applied to contacts for grouping and marketing segmentation. We export tag names and re-apply them as Dynamics 365 Contact Tags (native from Sales Professional) or as a multi-select picklist custom field loyalistic_tags__c depending on whether the customer's use case requires tag-based filtering in views and reports. The customer selects the strategy during scoping.

Loyalistic Segments are behavioural group memberships defined by rule-based criteria. Segment names migrate as Marketing List names (static lists of Contact or Lead records) with member lists preserved. Segment logic itself—rule conditions and operator criteria—does not migrate and must be recreated in Dynamics 365 using Marketing List filters or Power Automate. We deliver a written segment inventory with each segment's name, member count, and a Dynamics 365 equivalent recommendation.

Loyalistic Campaign records with title, status, and timing map to Dynamics 365 Campaign. Engagement events (opens, clicks, sends) attach as Activity records (Task and EmailMessage) linked to the Campaign via WhatId. CampaignMember records link the original Contact or Lead to the Campaign, preserving response status. Campaign budgets and planned costs from Loyalistic migrate as custom fields on the Dynamics 365 Campaign record.

Survey definitions (question text, type, order) from Loyalistic migrate as a custom Dynamics 365 entity schema (SurveyDefinition__c) or as structured Note records on the originating Contact. Survey responses migrate as response records linked to the Contact, with each answer mapped to a typed custom field. Question branching logic does not migrate; we document the branching path as a written reference for the customer's admin to reconstruct in Dynamics 365 Forms or a third-party survey tool.

Loyalistic custom fields on Contact migrate to equivalent Dynamics 365 custom fields on Contact or Lead. We perform field-level sampling during scoping to identify every active custom property, validate data types (text, number, date, picklist), and map them to typed Dynamics 365 fields before migration. Fields with picklist values that do not match Dynamics 365 allowed values require a value-mapping step before import.

Loyalistic engagement events—email opens, link clicks, form submissions, and meeting responses—migrate as Dynamics 365 Task records (for non-time-based events) or Event records (for scheduled meetings) linked to the originating Contact or Lead via WhoId and to the associated Campaign via WhatId. Open and click timestamps migrate as ActivityDate to preserve the engagement timeline ordering. High-volume engagement histories require Dynamics 365 Bulk API with batch chunking and parent-record lookup resolution.