CRM migration

Migrate from Selligent by Marigold to Freshsales

Field-level mapping, validation, and rollback between Selligent by Marigold and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.

Selligent by Marigold logo

Selligent by Marigold

Source

Freshsales

Destination

Freshsales logo

Compatibility

63%

5 of 8

objects map 1:1 between Selligent by Marigold and Freshsales.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Selligent by Marigold to Freshsales is a migration from an omnichannel marketing automation platform to a sales-focused CRM. Selligent uses Individuals as the primary contact records with Organizations for company data and Action Lists for audience segmentation; Freshsales uses the standard CRM model of Contacts, Accounts, and Deals. We export the Selligent Individual records via the Individual API, resolve organization associations, and map Action List membership to Freshsales Deals with tag-based segmentation carried over as custom properties or topic assignments. Automated journeys, campaign templates, and behavioral event triggers are not portable and are documented for admin rebuild. We sequence the Selligent field schema extraction first so that Freshsales custom fields are registered before any record write to avoid import rejection.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Selligent by Marigold logo

Selligent by Marigold

What's pushing teams away

  • 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.

Choosing

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How Selligent by Marigold objects map to Freshsales

Each row shows how a Selligent by Marigold object lands in Freshsales, 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

Individual

maps to

Freshsales

Contact

1:1
Fully supported

Selligent Individuals (primary contact records) map directly to Freshsales Contacts. The Selligent Individual API exposes standard addressability fields (email, mobile, first_name, last_name) plus custom profile properties. We export all standard fields and custom key-value props, then create the corresponding Freshsales contact fields before import. The Selligent USERID becomes a custom field selligent_user_id__c for audit and cross-reference. Email address serves as the dedupe key during upsert.

Selligent by Marigold

Organization

maps to

Freshsales

Account

1:1
Fully supported

Selligent Organizations store company-level data, often as custom properties or relation tags rather than a native parent object in Selligent's Individual API model. We extract organization associations from the Individual record's organization property or tag array, then create Freshsales Accounts before Contact import so that the Account-Contact relationship is satisfied at insert time. Website, phone, and industry fields map where present.

Selligent by Marigold

Action List

maps to

Freshsales

Deal

1:many
Fully supported

Selligent Action Lists contain LISTID-keyed records with USERID and ACTIONCODE plus custom fields. Each Action List maps to a Freshsales Deal record with the Action List name as the Deal name. Individual membership in an Action List is preserved as a contact tag or a custom multi-select field listing the Action Lists each contact belongs to. Action List-specific custom fields map to Deal custom fields. We resolve the parent Contact reference at migration time.

Selligent by Marigold

Dynamic Segment

maps to

Freshsales

Contact List or Custom Property

1:1
Fully supported

Selligent Dynamic Segments are defined by behavioral and demographic rules; the segment definitions themselves are not API-exportable. We export the member contacts from each segment and note the segment criteria so the customer can rebuild the logic in Freshsales using contact filters. Segment membership is preserved as contact tags or as values in a custom segmented field. We flag segments with over 1,000 members for manual rebuild priority.

Selligent by Marigold

Tag

maps to

Freshsales

Contact Tag or Custom Field

lossy
Fully supported

Selligent tags drive personalization and segmentation. We export tag assignments per contact and write them as Freshsales contact tags (using Freshsales' native tag API) or as values in a custom multi-select field depending on the tag count. Tags used for behavioral classification migrate as a separate custom field; tags used for simple label assignment migrate as native tags.

Selligent by Marigold

Custom Field (FieldsDefinition)

maps to

Freshsales

Custom Field

lossy
Fully supported

Selligent supports arbitrary custom fields on Individuals and Action Lists, passed as key-value prop arrays without upfront schema registration. Freshsales requires custom fields to be defined before data can be written. We extract the full FieldsDefinition array from Selligent during scoping, generate the corresponding Freshsales field creation API calls, and sequence record imports after field registration completes. Field type mapping: string arrays map to multi-select picklists, dates map to date fields, numerics map to number fields.

Selligent by Marigold

Behavioral Event Summary

maps to

Freshsales

Custom Field (Contact level)

1:1
Fully supported

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 (last purchase date, last engagement channel, engagement frequency) as contact-level custom fields on the Individual record. Full behavioral event history (timestamps, event types, session data) is documented as a separate export for manual re-entry or BI tool use.

Selligent by Marigold

Email Campaign History

maps to

Freshsales

Activity Timeline Note or Custom Field

1:1
Fully supported

Campaign history (subject, send date, audience size) can be exported from Selligent. We map campaign engagement (opens, clicks) to Freshsales contact activities stored as notes or custom activity fields on the contact. Full campaign content and design templates do not migrate; we flag them for manual re-upload at Freshsales. The Selligent campaign identifier is preserved for audit.

Gotchas + challenges

What specifically takes care here

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 logo

Selligent by Marigold gotchas

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

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Journeys and automated campaigns are not API-exportable

    Selligent does not expose journey definitions or campaign content templates via its public REST or SOAP API. Automated journey logic, branching rules, trigger conditions, and message content must be manually rebuilt at Freshsales. We document every active journey and campaign configuration during scoping and deliver a written rebuild guide with the Selligent journey structure mapped to Freshsales workflow equivalents. This is scoped as a separate workstream; the customer's marketing team or a Freshworks implementation partner rebuilds journeys post-migration.

  • Selligent API rate limits require batch-pacing during export

    Selligent's Individual API batches requests at 2,500 records per request with a 10-minute window and 20MB body size limit. We mitigate this by chunking contact exports into 2,000-record batches, monitoring for 429 responses, and applying exponential backoff with a 30-second base delay. For migrations exceeding 50,000 records, this pacing extends the export phase by several hours and is factored into the timeline estimate during scoping.

  • Organization data is often stored as tags or custom properties rather than a native object

    Selligent Organizations are not always a native parent object in the Individual API; company data frequently lives as custom properties, relation tags, or a separate Organization list. We resolve the organization reference during scoping by checking which Selligent list structure the customer uses for company records, then map accordingly. If company data is stored in a flat contact property (company_name field), we create Freshsales Accounts from that field value and link contacts during import.

  • Custom fields must be pre-created in Freshsales before record import

    Freshsales requires custom properties to be defined before data can be written to them. Selligent accepts custom field names as key-value props at record write time without upfront registration. We extract the full FieldsDefinition array from the customer's Selligent environment during scoping, generate the Freshsales field creation API calls, and sequence record imports after field registration completes. Skipping this step results in silent field drops during import.

Migration approach

Six steps for a successful Selligent by Marigold to Freshsales data migration

  1. Discovery and Selligent environment audit

    We audit the source Selligent environment: Individual record count, Organization structure (native vs tag-based), Action List count and schema, Dynamic Segment definitions, custom field definitions (FieldsDefinition array), tag taxonomy, and campaign history volume. We also identify active journeys and automated campaigns that require rebuild documentation. The output is a written migration scope with object mapping, record counts per phase, and a timeline estimate. We advise on contract timing if the customer is mid-term on a non-cancelable Selligent order.

  2. Freshsales schema pre-creation

    We create all required Freshsales custom fields, custom objects, and contact tags before any record import. This includes mapping Selligent's FieldsDefinition array to Freshsales field types, pre-creating Freshsales Accounts from the Selligent Organization list (or resolving from contact properties), and configuring Action List-to-Deal field mappings. Freshsales custom field creation uses the Freshsales CRM API. Schema is validated in a Freshsales sandbox or test account before production migration begins.

  3. Selligent Individual and Organization export

    We export Selligent Individuals via the Individual API in batches of 2,000 records, applying exponential backoff on 429 responses. Organization data is extracted either from the native Organization list or resolved from contact-level company properties. Each Individual record receives a selligent_user_id__c custom field for cross-reference. The export outputs a structured JSON file per Selligent list, with tag arrays preserved as tag fields.

  4. Action List export and Deal creation

    We export Action List records (LISTID-keyed with USERID and ACTIONCODE) for each active list. Each Action List becomes a Freshsales Deal record, with list-specific custom fields mapped to Deal custom fields. Contact membership in each Action List is written as contact tags. The parent Contact reference is resolved by matching Selligent USERID to the migrated contact's selligent_user_id__c.

  5. Production import in dependency order

    We import into Freshsales in record-dependency order: Accounts first (from Organizations or resolved company properties), then Contacts (with AccountId resolved), then Deals (with ContactId resolved). Tags are written after contacts to capture all membership. Each phase emits a row-count reconciliation report. We use the Freshsales CRM API with batch upsert and monitor for field-validation errors that indicate a custom field was missed during schema pre-creation.

  6. Cutover, validation, and automation rebuild handoff

    We freeze Selligent writes during cutover, run a final delta migration of any records modified during the migration window, then enable Freshsales as the system of record. We deliver the Journey and Campaign rebuild documentation to the customer's admin team with Freshsales workflow equivalents mapped. We support a one-week hypercare window for reconciliation issues. Workflows, automated campaigns, and journey logic are outside the migration scope; they are documented for admin rebuild.

Platform deep dives

Context on both ends of the pair

Selligent by Marigold logo

Selligent by Marigold

Source

Strengths

  • Email deliverability rates consistently praised in user reviews across retail and media verticals.
  • Native support for GDPR, CCPA, and CAN-SPAM compliance with documented sub-processor list.
  • Flexible custom field and data modeling accommodates complex B2C schemas without schema locks.
  • Multichannel journey orchestration across email, SMS, push, and web personalization in one platform.
  • AI-powered audience selection and send-time optimization built into the core platform.

Weaknesses

  • Public API documentation lacks comprehensive rate-limit tables and bulk export endpoints.
  • Journey builder configurations are not exportable via API, making migrations require full manual rebuilds.
  • Non-refundable contract terms mean customers pay for the full order term regardless of early termination.
  • Platform complexity creates a steep learning curve compared to simpler email-focused tools.
  • Ownership transition to Zeta Global introduces uncertainty for existing Marigold/Selligent customers.
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Selligent by Marigold and Freshsales.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Selligent by Marigold: Not publicly quantified; connector documentation shows batched behavior at 2500 requests or 10-minute windows.

  • Data volume sensitivity

    A

    Selligent by Marigold exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Selligent by Marigold to Freshsales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Selligent by Marigold to Freshsales data migrations

Answers to the questions buyers ask most during Selligent by Marigold to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Selligent by Marigold to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between three and five weeks for accounts under 15,000 contacts and 20 action lists with no behavioral event history export. Migrations with large contact databases (over 50,000 records), complex custom field schemas (over 50 properties), or behavioral event summaries extend to six to ten weeks because of Selligent API rate-limit pacing and Freshsales custom field pre-creation before record imports can begin.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Selligent by Marigold.
Land in Freshsales, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day