Migrate from Selligent by Marigold to Salesforce Sales Cloud

Selligent Individual records (the primary contact record keyed by USERID) map to Salesforce Contact. The Selligent email address, mobile number, and standard profile fields migrate directly. Custom profile properties from the FieldsDefinition array are pre-registered as Salesforce custom fields (Text, Number, Date, Picklist) before contact import. The Selligent Individual record ID (USERID) is preserved in a custom field selligent_userid__c for reconciliation and deduplication against future Selligent exports.

Selligent Organization data is often stored as custom properties or relation tags on Individual records rather than as a native parent object. We extract organization values from Individual custom fields during scoping, aggregate unique organization names, and map them to Salesforce Account records. The Individual's AccountId is resolved during Contact import by matching organization name to the pre-created Account. If Selligent stores explicit company hierarchy data, we map it to Account hierarchy fields (ParentAccountId).

Selligent Lists are audience containers comparable to Salesforce Campaigns. Each Selligent List becomes a Salesforce Campaign with Campaign Type set to 'Advertisement' or 'Direct Mail' depending on the customer's list usage pattern. List members (Individual records) migrate as CampaignMember records linked to the parent Contact. If the customer uses Selligent Lists for operational segmentation rather than campaign audience, we discuss using Salesforce public groups or a custom List object for the operational use case.

Selligent Dynamic Segments are defined by behavioral and demographic rules. Segment definitions are not directly exportable via API. We export the current member contacts for each active segment and document the segment criteria (rule conditions, filters, time windows) during scoping so the customer can recreate the logic in Salesforce using Reports with filters, Salesforce List Views, or a CDP layer. Member contacts migrate as CampaignMember records against the corresponding Campaign.

Selligent Action Lists contain LISTID-keyed records with USERID and ACTIONCODE plus custom fields. If Action Lists represent campaign participation records (e.g., a send history per contact per campaign), they map to Salesforce CampaignMember with custom fields carrying the ACTIONCODE value and any Action List-specific properties. If Action Lists represent a distinct entity type (e.g., subscription lists, suppression lists), we discuss creating a custom object in Salesforce to preserve the full schema.

Selligent supports arbitrary custom fields passed as key-value props without upfront schema registration. We extract the full FieldsDefinition array from the customer's Selligent environment during scoping, classify each field by data type (string, integer, boolean, date), and generate the corresponding Salesforce custom field creation API calls. Custom field creation is executed in the Salesforce destination org before any record import begins. Field order and grouping are preserved as closely as the Salesforce Page Layout structure allows.

Selligent Tags drive personalization and segmentation. We export tag assignments per Individual record and write them as Salesforce custom multi-select picklist fields on Contact (e.g., selligent_tags__c). If tags are used for classification that requires querying (e.g., 'prefers SMS over email'), we discuss creating a separate Tag assignment custom object with a lookup to Contact to support more granular filtering.

Selligent tracks online behavior (page views, product views, cart events, purchase events) for anonymous and known visitors. Event data is available via integration endpoints but not as a standalone exportable object. We migrate the most recent event summary per contact (last 30-90 days depending on volume) as records in a custom EventHistory__c object with fields for EventType, EventDate, EventValue, and a lookup to the parent Contact. Full historical event streams require a separate data engineering engagement to load into a data warehouse or event store.

Selligent campaign history (subject, send date, audience size, open rate, click rate) can be exported. We migrate contact-level engagement history (opens, clicks, unsubscribes) as Activity records or CampaignMemberStatus updates on the Salesforce Campaign. Campaign content (subject lines, body copy, templates) requires manual re-creation at the destination; we deliver a campaign content inventory document listing each campaign name, send date, and linked contact count.

Similar to email campaigns, SMS send history and engagement metrics are migratable. Message content and short code configuration require rebuild in Salesforce (using an SMS integration such as Marketing Cloud MobileConnect or a third-party SMS gateway). We migrate SMS engagement history as custom Activity records on the Contact. The customer's IT team configures the SMS gateway at the destination before campaign operations resume.

Selligent transactional message templates and API trigger configurations are not exported. We migrate the contact list associated with each transactional flow and note the trigger setup (event name, API endpoint, message template variables) for the customer to recreate using Salesforce's Transactional Messaging API or a third-party transactional email service (e.g., SendGrid, Mailgun) integrated via Apex.

Selligent user accounts and role assignments are organizational settings. We export user email addresses and roles where accessible via the API. Destination Salesforce User provisioning is customer-controlled; we provide a user mapping table (Selligent user email to Salesforce User ID) for the customer's admin to resolve before record import. If the customer uses Salesforce for sales operations post-migration, owner assignments on migrated records depend on this user mapping being complete.

Selligent webhook configurations are not directly exportable via public API. We document webhook URLs, event subscriptions, and payload structure during scoping as a written inventory so the customer can recreate them using Salesforce Platform Events, Outbound Messages, or a middleware layer (MuleSoft, Workato) post-migration.

Automated journeys are complex orchestration objects with branching logic, channel triggers, and timing rules. Selligent does not expose journey definitions via API. We do not migrate journeys as data. We document every active journey identified during scoping: journey name, entry trigger type, channel sequence (email, SMS, push, web), branching conditions, delay rules, and estimated rebuild complexity. This document is delivered to the customer as a rebuild guide for their admin or a Salesforce implementation partner.

Content blocks, images, and email templates live in Selligent's content library and are platform-native assets not suited for cross-platform migration. HTML content can be extracted as raw text but requires manual review and reformatting for Salesforce Content Builder or Marketing Cloud. We extract and deliver the raw HTML of each template as a reference document for the customer's email developer to rebuild in Salesforce.