Migrate from Selligent by Marigold to Pipedrive

Selligent contacts (Individual API records keyed by USERID) map directly to Pipedrive People. The contact's email address becomes the Person's primary email and the dedupe key. Standard fields (first name, last name, phone, address) map to Pipedrive's name, email, phone, and address fields. Custom profile properties extracted from Selligent's FieldsDefinition array are pre-created as custom fields on the Person object in Pipedrive before any record insert. We batch contacts at 2000 records per request to stay within Selligent's SDC rate-limit guidance and use exponential backoff on 429 responses.

Selligent stores organizational data often as custom properties or relation tags rather than a native parent object. We extract organization values from contact custom properties (e.g., company_name, account_id), deduplicate them, and bulk-insert into Pipedrive Organizations before contact import. Each Organization gets a unique ID that is then resolved as a custom Organization ID field or Pipedrive Organization lookup on the Person record. If Selligent has no organizational field, we offer a split strategy: create a default Organization for unassociated contacts or skip Organization creation entirely.

Selligent Action Lists (LISTID-keyed records with USERID and ACTIONCODE) represent campaign membership or behavioral classifications. We map Action List membership to Pipedrive by either (a) creating a custom multi-select picklist field on Person storing each list membership, or (b) creating a Pipedrive Deal per Action List with the associated contacts as Deal Participants, depending on how the customer uses Action Lists operationally. The mapping strategy is decided during scoping. Action List schema and record counts are extracted during discovery.

Selligent Dynamic Segments are defined by behavioral and demographic rule logic that is not API-exportable. We export the member contact IDs for each segment and write them to a custom field or tag in Pipedrive, preserving who was in the segment at migration time. The segment criteria rules (behavioral triggers, demographic conditions) are documented in a written segment inventory that the customer uses to rebuild equivalent static filters or automation triggers in Pipedrive. Segments are not migrated as active automation.

Selligent contacts carry arbitrary custom fields passed as key-value prop arrays. Pipedrive requires custom fields to be registered before data can be written. We extract the full FieldsDefinition array from Selligent during scoping, map each field's data type to the closest Pipedrive field type (text, number, date, varchar, multi-select), create the corresponding custom fields via Pipedrive's Fields API before any Person record is inserted, and then write the values during the contact import phase. Pipedrive Growth and above support custom fields; we confirm the customer's Pipedrive tier during discovery.

Selligent tags drive personalization and segmentation and are stored as arrays on the contact record. We export all tag assignments per contact and write them as a comma-separated custom text field, a multi-select picklist (if the tag set is small and stable), or Pipedrive Labels on the Person. Tags with high cardinality (more than 50 distinct values) are written as a JSON-encoded array in a single custom field to avoid creating dozens of Pipedrive picklist values.

Selligent campaign send history (subject line, send date, audience size) is available via API export. We create Pipedrive Activity records of type Note linked to the Person, recording the campaign subject, send date, and engagement summary. Open/click engagement data from Selligent's behavioral tracking is written as a separate Activity note block. Full email content and HTML templates are not migrated; we note the campaign subject and audience for the customer to re-create in Pipedrive's email sequencing or a connected marketing tool.

Selligent tracks online behavior for known visitors (page views, product views, cart events) via integration endpoints. The most recent event summary per contact migrates as a formatted Activity note on the Person record. Behavioral event data is not a standalone exportable object with full history, so we extract what the API makes available and document the event types present for the customer to configure Pipedrive Activities or a third-party enrichment tool to maintain this data post-migration.

Transactional message flows in Selligent associate contacts with a specific message trigger (e.g., order confirmation, shipping notification). We export the contact list associated with each transactional flow and write a custom field on the Person record (e.g., transactional_flow_ids) listing which flows the contact is enrolled in. The trigger configuration, API credentials, and template content are not exported; we document each flow's trigger setup for the customer to reconfigure in Pipedrive's automation tools or a dedicated transactional email service.

Selligent user accounts and role assignments are organizational settings that migrate as a lookup against Pipedrive's User table by email match. We extract user email addresses and roles where accessible and note that destination user provisioning is customer-controlled. Pipedrive requires active Users to be pre-provisioned before Deals or Activities can be assigned to them. Any Selligent user without a matching Pipedrive User goes to a reconciliation queue.