Migrate from Selligent by Marigold to Nutshell

Selligent's schemaless write vs Nutshell's field registration requirement

Selligent's Individual API accepts custom field names as key-value properties at insert time without requiring upfront schema registration. Nutshell requires custom fields to be defined before data can be written. We extract the full FieldsDefinition array from the customer's Selligent Action Lists during scoping, generate Nutshell Person custom field creation calls for each unique field, and run field registration before any record import begins. Without this sequencing, record inserts fail silently or are rejected with a field-not-found error. This is the most common point of failure in Selligent-to-Nutshell migrations and is resolved during discovery, not during migration.

Organizations stored as custom properties require manual Company-Person split

Selligent does not have a native Company object—organizational data lives in custom profile properties or relation tags on Contact. Nutshell enforces a Company-Lookup relationship for all business contacts. We extract organization name, domain, and address from Selligent contact properties, deduplicate by domain to create Nutshell Company records, then resolve the Person-Company link during the Person import phase. If multiple Selligent contacts share the same organization but store it inconsistently (variations in spelling, different domain formats), deduplication requires manual review during scoping. Skipping this step results in orphaned Person records with no Company link in Nutshell.

Dynamic Segment definitions are not exportable

Selligent Dynamic Segments are defined by behavioral and demographic rule logic stored in the platform's segmentation engine, not in a data object accessible via API. We can export the current member contact list (the materialized membership at export time) but not the rule definition. The segment criteria must be documented from the Selligent UI during scoping and rebuilt manually in Nutshell using its filter and static list features. If the customer has dozens of complex segments, the rebuild scope can be significant and is scoped as a separate workstream.

Journeys, campaign templates, and content blocks do not migrate

Selligent automated journey definitions, campaign message templates, and content library assets (images, blocks, dynamic content modules) are platform-native objects not accessible via the public REST or SOAP API for export. We migrate contact records and engagement history, but all automated journey logic, message content, and visual assets must be manually rebuilt in Nutshell or another destination platform. We deliver a written inventory of active journeys, campaign counts, and content asset types during scoping so the customer's team knows exactly what requires manual rebuild.

API rate limits and batch sizes constrain migration throughput

Selligent's API rate limits are not publicly quantified in full, but the Tealium connector documentation shows example batch behavior of 2,500 requests per 10-minute window with a 20MB size cap. The SDC bulk message limit caps individual sends at 100 messages per request. We mitigate this by chunking contact lists into batches of 2,000 records per request, using exponential backoff on 429 responses, and parallelizing across multiple authenticated sessions where the Selligent subscription tier allows. Large contact databases (over 50,000 records) require extended migration windows and are scoped accordingly.