Migrate your Selligent by Marigold data
Enterprise omnichannel marketing automation platform with strong European GDPR compliance, AI-driven personalization, and deep multichannel journey orchestration for B2C brands.
In its favor
Why people choose Selligent by Marigold
The signal that keeps Selligent by Marigold on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
GDPR and European data compliance depth makes Selligent a default choice for B2C brands operating across EU jurisdictions with strict opt-in and right-to-erasure requirements.
Omnichannel campaign management covering email, SMS, mobile push, and web personalization in a single platform eliminates the need for disconnected point solutions.
AI-driven audience selection and predictive send-time optimization appeal to sophisticated B2C marketers looking to automate personalization at scale.
Flexible and open data structure allows importing and exporting data files, API, or automation flows, giving technical teams room to integrate with legacy systems.
Built-in email deliverability consistently outperforms other platforms in user reviews, particularly for high-volume retail and media senders.
Enterprise pricing with non-refundable, non-cancelable contract terms creates sticker shock when teams need to downsize or pivot to a lower-cost platform.
Recent acquisition by Zeta Global in 2025 introduces uncertainty about product roadmap, support continuity, and long-term pricing for existing customers.
Platform complexity requires significant onboarding investment; smaller marketing teams report difficulty achieving full utilization without dedicated technical support.
Journey and campaign configuration is deep but not easily transferable, making migrations feel like rewrites rather than data moves and increasing switching costs.
API documentation and partner ecosystem are less extensive than dominant US-based platforms, leading to frustration when custom integrations are needed.
Reasons to switch
Why people leave Selligent by Marigold
The recurring reasons buyers give for replacing Selligent by Marigold. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Selligent by Marigold fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Selligent by Marigold pricing overview
Selligent by Marigold uses a per-user monthly subscription model with three published tiers ranging from $10 to $50/user/month and a minimum Custom Enterprise commitment around $500/month. Pricing scales with channel access, automation depth, and support tier; the platform does not offer a free trial or freemium entry point, and all contract terms are non-refundable and non-cancelable for the full order period.
Starter
Tier 1 of 4
$10/user/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Selligent by Marigold's schedule — see our quote-based pricing →
What gets migrated
Selligent by Marigold object support
Object-by-object support for Selligent by Marigold migrations. Per-pair details surface during scoping.
Contacts
Fully supportedContacts are the primary individual records in Selligent, tied to a USERID. We export all standard fields and custom profile properties via the Individual API. Addressability fields (email, mobile) are preserved for channel routing at the destination.
Companies/Organizations
Mapping requiredSelligent supports organizational hierarchy but companies are often stored as custom properties or relation tags rather than a native parent object. We map company data into a flat Contact property or custom Company object depending on the destination schema.
Dynamic Segments
Mapping requiredSegments are defined by behavioral and demographic rules. Segment definitions are not directly exportable; we export the member contacts and note the segment criteria so the customer can rebuild logic at the destination.
Action Lists
Fully supportedAction Lists contain LISTID-keyed records with USERID and ACTIONCODE plus custom fields. We export record-level data via the Individual API's AddRecordsToActionList reference, preserving all field values. The list itself can be recreated at the destination as a static list.
Custom Fields
Fully supportedSelligent supports arbitrary custom fields on Contacts and Action Lists, passed as key-value prop arrays. We extract the full FieldsDefinition and apply field creation at the destination before record import.
Tags
Fully supportedTags drive personalization and segmentation. We export tag assignments per contact and write them as tag fields or custom arrays at the destination.
Journeys
Not in this platformAutomated journeys are complex orchestration objects with branching logic, channel triggers, and timing rules. Selligent does not expose journey definitions via API for export. We document journey structure for manual rebuild scoping and migrate the contact audience list only.
Behavioral Events
Mapping requiredSelligent tracks online behavior for anonymous and known visitors. Event data is available via integration endpoints but not as a standalone exportable object. We migrate the most recent event summary per contact where available.
Content Blocks
Not in this platformContent blocks, images, and templates live in Selligent's content library. These are platform-native assets not suited for cross-platform migration; we flag them for manual re-upload at the destination.
Email Campaigns
Mapping requiredCampaign history (subject, send date, audience size) can be exported. Full campaign assets require re-creation at the destination. We export contact-level open/click engagement history where the API exposes it.
SMS/Mobile Campaigns
Mapping requiredSimilar to email campaigns, send history and engagement metrics are migratable. Message content and short code configuration require rebuild at the destination platform.
Transactional Messages
Mapping requiredTransactional message templates and API trigger configurations are not exported. We migrate the contact list associated with each transactional flow and note the trigger setup for the customer to reconfigure.
Webhooks
Mapping requiredSelligent webhook configurations are not directly exportable via public API. We document webhook URLs and event subscriptions during scoping so the customer can recreate them at the destination.
User Permissions
Mapping requiredUser accounts and role assignments are organizational settings. We export user email addresses and roles where accessible, noting that destination user provisioning is customer-controlled.
Reports and Dashboards
Not in this platformReporting widgets, journey reports, and dashboards are platform-native visualizations. Aggregate metrics are migratable as CSV exports; native dashboard definitions are not portable.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Contacts are the primary individual records in Selligent, tied to a USERID. We export all standard fields and custom profile properties via the Individual API. Addressability fields (email, mobile) are preserved for channel routing at the destination. |
| Companies/Organizations | Mapping required | Selligent supports organizational hierarchy but companies are often stored as custom properties or relation tags rather than a native parent object. We map company data into a flat Contact property or custom Company object depending on the destination schema. |
| Dynamic Segments | Mapping required | Segments are defined by behavioral and demographic rules. Segment definitions are not directly exportable; we export the member contacts and note the segment criteria so the customer can rebuild logic at the destination. |
| Action Lists | Fully supported | Action Lists contain LISTID-keyed records with USERID and ACTIONCODE plus custom fields. We export record-level data via the Individual API's AddRecordsToActionList reference, preserving all field values. The list itself can be recreated at the destination as a static list. |
| Custom Fields | Fully supported | Selligent supports arbitrary custom fields on Contacts and Action Lists, passed as key-value prop arrays. We extract the full FieldsDefinition and apply field creation at the destination before record import. |
| Tags | Fully supported | Tags drive personalization and segmentation. We export tag assignments per contact and write them as tag fields or custom arrays at the destination. |
| Journeys | Not in this platform | Automated journeys are complex orchestration objects with branching logic, channel triggers, and timing rules. Selligent does not expose journey definitions via API for export. We document journey structure for manual rebuild scoping and migrate the contact audience list only. |
| Behavioral Events | Mapping required | Selligent tracks online behavior for anonymous and known visitors. Event data is available via integration endpoints but not as a standalone exportable object. We migrate the most recent event summary per contact where available. |
| Content Blocks | Not in this platform | Content blocks, images, and templates live in Selligent's content library. These are platform-native assets not suited for cross-platform migration; we flag them for manual re-upload at the destination. |
| Email Campaigns | Mapping required | Campaign history (subject, send date, audience size) can be exported. Full campaign assets require re-creation at the destination. We export contact-level open/click engagement history where the API exposes it. |
| SMS/Mobile Campaigns | Mapping required | Similar to email campaigns, send history and engagement metrics are migratable. Message content and short code configuration require rebuild at the destination platform. |
| Transactional Messages | Mapping required | Transactional message templates and API trigger configurations are not exported. We migrate the contact list associated with each transactional flow and note the trigger setup for the customer to reconfigure. |
| Webhooks | Mapping required | Selligent webhook configurations are not directly exportable via public API. We document webhook URLs and event subscriptions during scoping so the customer can recreate them at the destination. |
| User Permissions | Mapping required | User accounts and role assignments are organizational settings. We export user email addresses and roles where accessible, noting that destination user provisioning is customer-controlled. |
| Reports and Dashboards | Not in this platform | Reporting widgets, journey reports, and dashboards are platform-native visualizations. Aggregate metrics are migratable as CSV exports; native dashboard definitions are not portable. |
Gotchas
What to watch for in Selligent by Marigold migrations
Issues we've hit on past Selligent by Marigold migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
API rate limits are documented but not fully quantified publicly
Enterprise contracts are non-cancelable with no refunds mid-term
Journeys and campaign templates are not API-exportable
SDC bulk message limit of 100 per request caps throughput
Custom field schema must be pre-created at destination before import
| Severity | Issue |
|---|---|
| Medium | API rate limits are documented but not fully quantified publicly |
| High | Enterprise contracts are non-cancelable with no refunds mid-term |
| High | Journeys and campaign templates are not API-exportable |
| Medium | SDC bulk message limit of 100 per request caps throughput |
| Medium | Custom field schema must be pre-created at destination before import |
Leaving Selligent by Marigold?
Where Selligent by Marigold customers move next
12 destinations Selligent by Marigold can migrate to.
How a Selligent by Marigold migration works
Four steps, Selligent by Marigold-specific
Connect
OAuth 2.0 into Selligent by Marigold. Scopes limited to read-only on the data we move.
Map
We translate Selligent by Marigold-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Selligent by Marigold quirks before production.
Migrate
Full migration with Selligent by Marigold rate-limit handling. Rollback available throughout.
FAQ
Selligent by Marigold migration FAQ
Answers to the questions buyers ask most during Selligent by Marigold migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Selligent by Marigold migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Selligent by Marigold.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Selligent by Marigold setup and destination — written quote back within a business day.