Migrate from Selligent by Marigold to HighLevel

Selligent Individual records are the primary contact entity tied to a USERID. We export all standard profile fields (email, first name, last name, phone, address) plus custom profile properties via the Individual API. The email address serves as the dedupe key during GoHighLevel import. Selligent's GDPR fields (consent timestamps, opt-in status) migrate to GoHighLevel contact custom fields. Phone number formats are normalized before import to match GoHighLevel's validation format.

Selligent Action Lists store LISTID-keyed records with USERID and ACTIONCODE plus custom fields unique to each list. We extract the FieldsDefinition array from Selligent's CreateActionList API payload during scoping, generate the corresponding GoHighLevel custom field creation calls (via Settings > Custom Fields > Contact Custom Fields), and sequence contact imports after field registration completes. Each Action List may have different custom field schemas; we iterate this process per list and merge non-conflicting fields into a single GoHighLevel custom field set where possible.

Tags in Selligent drive personalization and segmentation and are stored as per-contact associations. We export tag assignments per Individual record and write them as GoHighLevel contact tags during import. GoHighLevel supports multiple tag assignment per contact, so the migration is direct. We preserve tag names exactly as they appear in Selligent to maintain segment continuity. If tag counts exceed GoHighLevel's display limit in the UI, we discuss pagination strategy with the customer during scoping.

Selligent Dynamic Segments are defined by behavioral and demographic rule sets that are not exportable via API. We export the member contacts for each segment and write them as GoHighLevel contacts with a custom field segment_origin__c carrying the segment name. GoHighLevel Smart Lists with equivalent filter logic must be rebuilt manually; we deliver a written segment inventory listing each Selligent segment's criteria (captured during scoping) with recommended GoHighLevel Smart List filter equivalents.

Selligent often stores organizational data as custom properties or relation tags on Individual records rather than as a native parent object. Companies referenced in Selligent migrate to GoHighLevel Location records attached to the primary contact. If the customer has a significant company hierarchy, we map organizational name to Location > Company Name and create location-contact links via GoHighLevel's contact-company relationship.

Selligent tracks online behavior for anonymous and known visitors via integration endpoints. Event data is available through API but not as a standalone exportable object with full schema. We migrate the most recent event summary fields (last product viewed, last category visited, last purchase date) as GoHighLevel contact custom fields. Full event history requires a separate data engineering scope if the customer needs behavioral timeline reconstruction.

Selligent email campaign send history (subject, send date, audience size, open/click engagement) is migratable per contact. We write campaign engagement as GoHighLevel contact activity notes with timestamp, noting the campaign name and engagement type (Opened, Clicked). The full campaign assets (templates, content, images) do not migrate; we deliver a campaign content inventory for the customer to re-upload manually.

Selligent user accounts and role assignments are organizational settings accessible via the Admin API. We export user email addresses, names, and role designations where the API exposes them. GoHighLevel user provisioning is customer-controlled; we deliver a user-role mapping table and the customer provisions GoHighLevel users before or during the migration window.