Migrate from Selligent by Marigold to Microsoft Dynamics 365 Sales

Selligent Individual records (the USERID-keyed primary contact entity) map directly to Microsoft Dynamics 365 Contact. Standard profile fields (email, first name, last name, phone, address) migrate as typed Contact fields. Custom profile properties are extracted from the FieldsDefinition array during scoping, pre-registered as custom fields on the Contact entity in Dynamics 365 before record import, and imported as name-matched field values. Email address serves as the primary dedupe key across the migration.

Selligent stores organizational data as custom properties on the Individual record rather than as a native parent object. We extract organization name, domain, industry, address, and phone from those custom properties, construct a deduplicated Account list, create Account records in Dynamics 365, then back-fill the original Individual records with the resolved AccountID lookup before Contact import. This ensures every Contact has a parent Account reference, which is required for most Microsoft Dynamics 365 Sales workflows.

Selligent Action Lists are LISTID-keyed record collections attached to Individual contacts via USERID and ACTIONCODE with custom field schemas. We export the full Action List definition (field names, types, values) per contact. Since Microsoft Dynamics 365 Sales does not have a native Action List equivalent, we map these to a custom Selligent_Action_List__c entity pre-created in the destination org, with one child record per Action List membership and all custom fields preserved. If the customer has fewer than five Action Lists and prefers a simpler model, we can alternatively store Action List membership as a multi-select text field on the Contact record.

Selligent Dynamic Segments are defined by behavioral and demographic rule sets that are not API-exportable. We export the current member contact set (the real-time segment membership at export time) and attach a segment_membership__c text field to each Contact record listing all segment names. We deliver a written segment criteria summary (the rule conditions, operators, and values) so the customer's admin can recreate the logic as a Dynamics 365 Marketing segment, a Power Automate flow, or a Dataverse query-based security role. The segment definition itself cannot be code-migrated.

Selligent tag assignments (driving personalization and segmentation) migrate as a comma-delimited multi-select text field on the Contact record. The customer chooses whether tags are stored as a single multi-select text field or as separate Boolean custom fields during scoping. If the number of distinct tags exceeds 100, we recommend a separate tagging entity with a many-to-many relationship to Contact.

Selligent tracks online behavioral events (page views, purchases, cart actions) for anonymous and known visitors. Event data is available via integration endpoints but not as a standalone exportable object. We migrate the most recent 12 months of event summary data as structured Note records (with a custom note type for behavioral events) attached to the Contact, containing event name, timestamp, and relevant property values. Full historical event streams migrate as a custom behavioral_event__c entity if the customer requires longitudinal behavioral analysis post-migration.

Selligent email campaign history (subject line, send date, audience size, open/click/subscribe engagement at the contact level) migrates to Dynamics 365 Campaign and CampaignMember records. We create one Campaign record per Selligent campaign, populate send metadata as Campaign fields, and link individual contacts as CampaignMember records with status mapping (Opened maps to Responded, Clicked maps to Sent with an additional activity note). Full email content and template assets require manual re-upload at the destination.

Similar to email campaigns, SMS send history and contact-level engagement (delivered, failed, replied) migrate to Dynamics 365 Campaign records with a custom SMS-specific activity log. Short code configuration, opt-in keyword setup, and SMS template content require rebuild in Dynamics 365's SMS configuration or a partner ISV SMS solution connected to the Dynamics 365 org.

Transactional message flows (order confirmations, shipping notifications, password resets) maintain a contact association in Selligent that we preserve in Dynamics 365. We flag migrated contacts with a transactional_opt_in__c Boolean field indicating they are in a transactional message flow. The trigger configuration for transactional sends is documented and handed off; it requires rebuild in Dynamics 365's Power Automate or a transactional email API integration.

Selligent supports arbitrary custom fields on Individual records passed as key-value prop arrays at write time without upfront schema registration. Dynamics 365 requires custom fields to be defined before data can be written. We extract the full FieldsDefinition array from the customer's Selligent environment during scoping, generate the corresponding custom field creation API calls for the Dynamics 365 Dataverse, and sequence record imports to begin only after field registration is validated in the destination org.

Selligent user accounts and role assignments are organizational settings. We export user email addresses and role names where accessible via the API. Destination user provisioning is customer-controlled in Dynamics 365; we provide the user roster mapping during discovery so the customer's admin can provision Active Directory or Azure AD-linked Dynamics 365 user accounts before record migration begins.