Migrate from Selligent by Marigold to Twenty CRM

Selligent Individual records map directly to Twenty Person records. The USERID becomes the source_system_id stored on the Person for audit. Standard profile fields (email, first name, last name, phone) map to Twenty's emailAddress, displayName, and phoneNumber fields. Custom profile properties migrate as Twenty custom fields on Person, which must be pre-created via the Twenty /metadata API before the Person import runs. All timestamp fields (createdAt, updatedAt) preserve the original Selligent values.

Selligent organizations are often stored as custom properties on Individual records or as relation tags rather than as a native parent object. We extract all distinct organization values referenced across the Individual corpus, deduplicate them, and create Twenty Company records before the Person import. Each Person record then receives a companyId lookup to the resolved Company. Organizations without a clear name default to the domain extracted from the Individual's email address.

Selligent Action Lists contain LISTID-keyed records with USERID and ACTIONCODE plus custom fields. We assess whether each Action List represents a sales pipeline stage (migrating to Twenty Opportunity) or a membership list (migrating to a custom object). Action Lists with numeric amount fields and stage-like ACTIONCODE values map to Opportunity records; lists used for campaign audience segmentation map to a custom object named after the Action List with all custom fields preserved.

Selligent Dynamic Segments are defined by behavioral and demographic rules that are not API-exportable. We export the member contact list for each segment (the resulting Individuals), write them to Twenty as Person records with a segment-derived tag field, and document the original segment criteria for the customer's admin to rebuild using Twenty's filter and view system. Segment definitions themselves require manual recreation.

Selligent accepts custom field names as key-value properties at write time without requiring upfront schema registration. Twenty requires custom fields to be pre-created via the /metadata API before data can be written. We extract the full FieldsDefinition array from the customer's Selligent environment during scoping, generate the corresponding Twenty metadata API calls to create each custom field with the correct type (text, number, date, select, multiselect), and sequence Person record imports after field registration completes.

Selligent tags drive personalization and segmentation. We export tag assignments per Individual and write them as tag strings on the Person record in Twenty. Tags that represent behavioral classifications (e.g., purchased, churned, VIP) are written to a dedicated custom field of type multiselect; tags that represent source attribution are written to a source field.

Selligent campaign send history (subject, send date, audience size, open/click engagement) is available via API. We export contact-level engagement metrics and write them as Task records attached to the Person, with the campaign name as the Task subject and engagement metrics stored in custom fields. This preserves the marketing interaction timeline for teams that want historical context at the contact level.

Selligent Journey definitions are not exposed via the public REST or SOAP API. Automated journey logic, branching rules, trigger conditions, and message content must be manually rebuilt at the destination. We document the structure of each active Journey during scoping (channel, entry trigger, branches, exit conditions) in a written handoff document that the customer's team uses to recreate logic in Twenty's workflow system.

Selligent user accounts and role assignments are organizational settings that migrate as configuration data. We export user email addresses and role names where accessible and map them to Twenty WorkspaceMember invitations. The customer's admin provisions the actual users in Twenty and accepts the invitations before Person records with owner assignments are imported.

Selligent supports arbitrary custom fields on Individuals and Action Lists. Twenty provides a custom object system built on metadata tables (DataSource, Object, Field) that are queried via the /metadata GraphQL endpoint. We map Selligent custom data structures to Twenty custom objects, pre-creating the schema via metadata API calls before importing any records. Lookup relationships between custom objects require parent records to be created first.