Migrate from Selligent by Marigold to Mailchimp

Selligent Individual records map to Mailchimp Audience members via email address as the primary key. We export all standard profile fields (firstname, lastname, email, phone, address) and custom properties from the FieldsDefinition array. The Selligent USERID is preserved in a custom merge field selligent_userid__c for reconciliation. Phone numbers are stored as Mailchimp phone merge fields. Selligent's GDPR consent flags migrate to Mailchimp's Marketing Permissions array with timestamp. Address fields map to Mailchimp's structured address merge fields. Because Selligent maintains a single shared contact pool across Action Lists, the contact exports once and gets distributed to the correct Mailchimp Audiences based on LISTID membership during import.

We extract the complete FieldsDefinition array from Selligent's CreateActionList API payload during scoping and generate the corresponding Mailchimp merge field creation API calls before any contact import begins. Text, number, date, and boolean custom fields in Selligent map to Mailchimp TEXT, NUMBER, DATE, and PHONE merge field types respectively. Boolean fields stored as string values (true/false, yes/no) in Selligent are normalized to Y/N string values in Mailchimp to avoid type mismatches. Because Mailchimp requires merge fields to exist before contact data can reference them, we sequence merge field registration as the first step in the Mailchimp destination setup phase. Mailchimp's limit is 40 merge fields per Audience on Standard tier and 80 on Premium tier; we flag early if the Selligent schema exceeds the target tier's limit.

Selligent tags drive personalization and segmentation and map directly to Mailchimp Tags on a per-Audience basis. We export the full tag assignment set per Individual record during Selligent extraction and write each unique tag to the Mailchimp Audience Tags API endpoint (POST /lists/{list_id}/tagger) during import. Tags with hierarchical naming conventions (e.g., tier-gold, tier-silver) in Selligent are preserved verbatim in Mailchimp. Mailchimp Tags do not have a native expiration or automatic removal mechanism; we document the original tag application date in a custom merge field so the customer's admin can build retention or pruning automations in Mailchimp if needed.

Selligent Dynamic Segments are defined by behavioral and demographic rule sets that are not exportable via API. We export the full member contact list for each Dynamic Segment and recreate segment membership in Mailchimp by applying the corresponding Selligent tag to each member. The original segment criteria are documented in the migration deliverable so the customer can rebuild the rule-based logic using Mailchimp's Segment builder, which supports similar condition-based rules (location, engagement history, merge field values). Segments with over 50,000 members may exceed Mailchimp's per-segment query performance threshold; we advise the customer on Audience size planning during scoping.

Selligent Action Lists contain LISTID-keyed Individual records with ACTIONCODE and custom field arrays. Each Selligent Action List maps to a separate Mailchimp Audience because Mailchimp's architecture treats contacts in different Audiences as completely separate records with no shared pool. We extract contacts by LISTID from Selligent's Individual API and import them into the corresponding Mailchimp Audience. The Action List name becomes the Audience name, and the LISTID is preserved in a merge field selligent_listid__c. If the customer prefers a single consolidated Audience, we can merge Action Lists into one Audience with a LISTID tag applied per contact; this decision is made during scoping.

Selligent supports organizational hierarchy stored as custom properties or relation tags on Individual records rather than as a native parent object. Company data migrates into Mailchimp by one of two strategies: as a TAG on each member (preferred for companies with few associated contacts and where company-level reporting is not needed) or as a merge field named COMPANY or ORG on each member profile (preferred when the customer needs to segment or filter by company name in Mailchimp reports). We extract the company relationship from Selligent's Individual custom property arrays during scoping and apply the chosen strategy during import. Mailchimp Premium supports Customer Attributes which can serve as a company dimension if the customer upgrades.

Selligent campaign history (subject line, send date, audience size, open rate, click rate, unsubscribe count) migrates to Mailchimp as activity records attached to each member profile. The campaign subject and send timestamp are stored as Mailchimp Campaign activity events on each member. Because Mailchimp does not expose historical campaign content via API, the campaign name in Selligent becomes a documented record in the handoff deliverable with the estimated member engagement metrics. The customer uploads campaign content assets manually to Mailchimp's content studio post-migration if historical email content needs to be reactivated. Transactional message campaign history migrates similarly as engagement events on the member timeline.

Selligent tracks email engagement events (opens via tracking pixel, clicks via link wrapping, unsubscribes via ACTIONCODE) per Individual record. We export the engagement event history per contact and write it to Mailchimp as member activity records using the Members Activity API endpoint (GET /lists/{list_id}/members/{hash}/activity). Open events, click events, and bounce records map to Mailchimp's activity type enumeration. Unsubscribe records from Selligent map to Mailchimp's unsubscribed status and are applied at the Audience level. Engagement timestamp ordering is preserved. Because Selligent's engagement event schema varies by configuration, we extract the full event payload during scoping and build a custom event normalization pipeline before writing to Mailchimp's activity feed.

Selligent transactional message templates and API trigger configurations are not exportable via public API. We extract the contact list associated with each Selligent transactional flow (e.g., order confirmation, password reset, shipping notification) and import those contacts into the corresponding Mailchimp Audience with a transactional tag applied. The trigger setup, template field names, and API configuration are documented in the migration handoff so the customer's developer can recreate the transactional sends using Mailchimp's Transactional API (Mandrill). The customer retains responsibility for re-establishing the e-commerce or application integration that fires transactional events post-migration.

Selligent webhook configurations are not directly exportable via the public REST API. During scoping, we document the webhook URLs, subscribed event types, and authentication method for each active Selligent webhook so the customer can recreate them in Mailchimp's Webhook configuration (Lists > Manage Audience > Settings > Webhooks). Mailchimp webhooks support subscribe, unsubscribe, campaign, and profile update event types. We cross-reference Selligent's event types with Mailchimp's webhook event model and flag any gaps (e.g., Selligent behavioral event webhooks have no direct Mailchimp equivalent). The customer or their developer recreates the webhooks post-migration using the documented configuration.

Selligent Journeys are complex orchestration objects with branching logic, multichannel triggers (email, SMS, push, web personalization), timing rules, and AI-driven audience selection. Selligent does not expose journey definitions via its public REST or SOAP API, making automated migration of Journey logic impossible. We document the structure of every active Journey during scoping: trigger conditions, channel sequence, branch rules, delay logic, and estimated audience size per path. The customer rebuilds these in Mailchimp Automations using Mailchimp's automation builder. Mailchimp Automations support email-focused journey logic and include pre-built templates for welcome series, abandoned cart, and post-purchase flows; multichannel (SMS, push, web) automations require Mailchimp Standard or Premium tier with the respective channel add-ons.

Selligent tracks online behavior for anonymous and known visitors via integration endpoints, including purchase history, page views, and custom event streams. Raw event history is not available as a standalone exportable object from Selligent's public API. We extract the most recent behavioral event summary per contact (e.g., last purchase date, total lifetime value, product category preferences) during scoping and import these as contact-level merge fields in Mailchimp. Behavioral data modeled as multi-value arrays (e.g., recent product views) are stored as pipe-delimited text merge fields or as tags per event type. The customer should plan to re-establish behavioral event tracking through Mailchimp's integration with their e-commerce or analytics platform post-migration (Shopify, WooCommerce, or Google Analytics 4 connector recommended).

Selligent user accounts and role assignments are organizational settings accessible via the access management API. We export user email addresses, display names, and role designations (admin, marketer, viewer) during scoping. Mailchimp user provisioning is customer-controlled via the account settings panel or the Mailchimp API. We document the Selligent user roster with recommended Mailchimp role mappings (Admin, Author, Viewer) in the migration deliverable. Because Mailchimp's permission model is Audience-scoped rather than org-wide, the customer assigns roles per Audience post-migration. We do not create Mailchimp user accounts directly as this requires the customer's admin credentials and is an account administration task rather than a data migration task.