CRM migration
Field-level mapping, validation, and rollback between Selligent by Marigold and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Selligent by Marigold
Source
monday CRM
Destination
Compatibility
7 of 9
objects map 1:1 between Selligent by Marigold and monday CRM.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Migrating from Selligent by Marigold to Monday.com CRM is a category shift, not a straightforward record copy. Selligent organizes data around Universal Consumer Profiles, Dynamic Segments, Action Lists, and omnichannel campaign history; Monday.com CRM uses a board-and-item structure with People, Organizations, and Deals as first-class entities. We extract Selligent contacts via the Individual API, map custom profile properties to Monday column types, and preserve tag assignments as Monday tags or group labels. Segments and behavioral event rules are not exportable from Selligent; we deliver a written segmentation rebuild guide instead. Selligent journey definitions, campaign content templates, and journey branching logic have no Monday.com equivalent and require manual rebuild post-migration. Monday's native Work Management boards can be migrated directly using their internal migration path, but CRM-specific entities like People and Deals require FlitStack AI's API-based migration to preserve historical timestamps and custom field values that the internal tool does not carry.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Selligent by Marigold object lands in monday CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Selligent by Marigold
Contact (Individual)
monday CRM
Person (People CRM entity)
1:1Selligent Individual records map to Monday People items on the CRM board. Standard fields (email, first_name, last_name, mobile, address) map directly to Monday person properties. Custom profile properties from Selligent's FieldsDefinition array become Monday columns of the matching type (text, number, date, dropdown, checkbox, etc.). We extract the full custom field schema during scoping, pre-create all columns on the Monday CRM board before record import, and write contacts in batches of 200 via the Monday GraphQL API.
Selligent by Marigold
Company (Organization)
monday CRM
Organization (Companies CRM entity)
1:1Selligent organizations are stored as custom properties or relation tags on Individual records rather than as a native parent object in all configurations. We extract organization data and write it to Monday Organizations. Website, industry, employee_count, and address fields map to Monday Organization properties. Custom company fields from Selligent's schema become Organization columns pre-created before import.
Selligent by Marigold
Action List (LISTID-keyed records)
monday CRM
Board Items (grouped by list)
1:manySelligent Action Lists contain LISTID-keyed contact records with ACTIONCODE and custom fields. We export Action List membership per contact and map each Selligent Action List to a Monday board Group or a dedicated board. The action_code property and any list-specific custom fields become columns on the board. If a contact belongs to multiple Action Lists, we create multiple Board Item entries or use Tags to represent list membership within a single board.
Selligent by Marigold
Dynamic Segment (member contacts)
monday CRM
Board Tags or Filtered Views
1:1Selligent Dynamic Segments are defined by behavioral and demographic rule sets that are not exportable via API. We export the member contact IDs and write them to Monday as Tag assignments on the relevant People items, preserving the contact-level membership data. The segment definition and rule logic are documented in the handoff package for the customer's admin to rebuild as Monday Tags or saved filtered Views.
Selligent by Marigold
Tag (contact-level)
monday CRM
Tag
1:1Selligent tag assignments per contact migrate directly to Monday Tags on People items. Tags drive personalization and segmentation in Selligent; in Monday they serve as flexible labeling for filtering and grouping. We extract the full tag vocabulary during scoping and create matching Monday tags before contact import.
Selligent by Marigold
Custom Fields (profile properties)
monday CRM
Columns (People, Organization, or Deal)
lossySelligent accepts arbitrary custom fields as key-value props at write time without requiring upfront schema registration, while Monday requires columns to exist before data can be written. We extract the complete FieldsDefinition array from Selligent during scoping, map each field to the nearest Monday column type (text, number, date, dropdown, checkbox, link, phone, email), pre-create the columns via the Monday API, and sequence record imports after column registration completes.
Selligent by Marigold
Email Campaign (send history)
monday CRM
Activity Log entries on Person
1:1Selligent email campaign history (subject, send date, audience size, open/click engagement) is available via the Individual API engagement endpoints. We write a summary Activity Log entry to each Person item documenting the last send date, campaign name, and engagement rate. Full campaign content and templates do not migrate; the campaign subject line and send metadata are preserved as a record of send history.
Selligent by Marigold
SMS/Mobile Campaign (send history)
monday CRM
Activity Log entries on Person
1:1Similar to email campaigns, SMS send history and delivery status per contact are migratable from Selligent. We write an Activity Log entry to each Person documenting the SMS send date, message summary, and delivery status. Message content and short code configuration require rebuild at the destination.
Selligent by Marigold
Behavioral Event (summary)
monday CRM
Custom Columns or Activity Log
1:1Selligent tracks online behavior for known visitors. Event summary data is available via integration endpoints but not as a standalone exportable object. We migrate the most recent behavioral summary fields per contact (last viewed product, last session date, page view count) as custom columns on the Person item. Full event history does not migrate due to volume and API constraints.
| Selligent by Marigold | monday CRM | Compatibility | |
|---|---|---|---|
| Contact (Individual) | Person (People CRM entity)1:1 | Fully supported | |
| Company (Organization) | Organization (Companies CRM entity)1:1 | Fully supported | |
| Action List (LISTID-keyed records) | Board Items (grouped by list)1:many | Fully supported | |
| Dynamic Segment (member contacts) | Board Tags or Filtered Views1:1 | Fully supported | |
| Tag (contact-level) | Tag1:1 | Fully supported | |
| Custom Fields (profile properties) | Columns (People, Organization, or Deal)lossy | Fully supported | |
| Email Campaign (send history) | Activity Log entries on Person1:1 | Fully supported | |
| SMS/Mobile Campaign (send history) | Activity Log entries on Person1:1 | Fully supported | |
| Behavioral Event (summary) | Custom Columns or Activity Log1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Selligent by Marigold gotchas
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
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Discovery and Monday CRM account audit
We audit the customer's Selligent environment across contacts, organizations, Action Lists, segments, tags, custom fields, and campaign engagement history. We also audit the destination Monday.com account to determine whether the customer has existing Work Management boards that need to be consolidated with CRM entities. If existing Monday boards are present, we determine whether Option 1 (move boards as-is and add CRM features) or Option 2 (rebuild on CRM entities) applies. This decision affects the migration path and timeline significantly.
Schema extraction and Monday column pre-creation
We extract the complete FieldsDefinition array from Selligent's Individual API during discovery, capturing every custom profile property and its data type. We map each field to the nearest Monday column type and pre-create all columns on the relevant People, Organization, or Deal boards via the Monday GraphQL API before any records are imported. This step resolves the schema-first requirement that Monday.com enforces, which differs from Selligent's flexible write-time field acceptance.
Tag vocabulary extraction and Monday tag creation
We extract the full tag vocabulary from Selligent, including every distinct tag assigned to any contact. We create matching Monday Tags in the destination account before contact import, ensuring that tag assignments can be written as a post-import enrichment step rather than during the high-volume contact write cycle.
Sandbox migration and reconciliation
We run a full migration into a Monday test workspace using production-like record volumes. The customer reconciles record counts (People in, Organizations in, Activity Log entries in), spot-checks 25-50 random records against the Selligent source, and validates that custom column values transferred correctly. Tag assignments and Action List group memberships are verified at this stage. Mapping corrections happen in the test workspace before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Organizations first (since People items link to Organizations), then People (with OrganizationId resolved), then Activity Log entries (email and SMS send history per Person), then Action List group creation (mapped to board Groups or tagged items). Tags are applied as a final step. Each phase emits a row-count reconciliation report before the next phase begins. We use Monday's GraphQL API with batch chunking and exponential backoff on rate-limit responses.
Cutover, segmentation handoff, and automation rebuild guide
We freeze Selligent writes during cutover, run a final delta migration of any records modified during the migration window, then hand the Monday.com account to the customer's team. We deliver the segmentation handoff document (member contact lists per former segment with rebuild recommendations), the journey and campaign rebuild guide (documented triggers, conditions, and message content for manual rebuild in Monday automations), and a one-week hypercare window for reconciliation issues. We do not rebuild Selligent journeys as Monday automation recipes inside the migration scope; that is a separate marketing implementation engagement.
Platform deep dives
Selligent by Marigold
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Selligent by Marigold and monday CRM.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Selligent by Marigold and monday CRM.
Object compatibility
All 8 core objects map 1:1 between Selligent by Marigold and monday CRM.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Selligent by Marigold: Not publicly quantified; connector documentation shows batched behavior at 2500 requests or 10-minute windows.
Data volume sensitivity
Selligent by Marigold exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Selligent by Marigold to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Selligent by Marigold to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Selligent by Marigold
Other ways to arrive at monday CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.