CRM migration

Migrate from Selligent by Marigold to Zoho CRM

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

Selligent by Marigold logo

Selligent by Marigold

Source

Zoho CRM

Destination

Zoho CRM logo

Compatibility

55%

6 of 11

objects map 1:1 between Selligent by Marigold and Zoho CRM.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Selligent by Marigold to Zoho CRM is a cross-category migration from a B2C marketing automation platform to a sales-and-account-management CRM. Selligent organizes data around Universal Consumer Profiles, Action Lists, and behavioral event history; Zoho CRM uses a Leads-Contacts-Accounts-Deals module structure that requires a schema redesign before any record import. We extract the full FieldsDefinition array from your Selligent environment during scoping, generate the corresponding Zoho custom field creation API calls, and apply the field schema before any records are written. Action Lists migrate as either custom modules or lookup-linked records against Zoho Accounts, preserving LISTID and ACTIONCODE associations. Journey logic, campaign templates, and automation rules do not port; we deliver a written inventory documenting every journey trigger, branching rule, and channel sequence so your admin can rebuild them in Zoho Workflows. Behavioral event history migrates partially as contact-level custom properties since Zoho does not support a native event stream object. Ownership transition risk from Selligent's 2025 acquisition by Zeta Global is a common migration driver, and the non-refundable contract terms mean scoping should ideally align with your renewal window.

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

Zoho CRM logo

Zoho CRM

What's pulling them in

  • Free tier is genuinely usable for up to 3 users with leads, pipeline management, and email tracking — no credit card required, making it easy to evaluate before committing.
  • Pricing undercuts Salesforce by 80–90% at equivalent feature tiers, with Enterprise plans offering capabilities that cost 3–4× more on competing platforms.
  • Deep ecosystem of 45+ integrated apps (Books, Desk, Creator, Campaigns) means companies already in the Zoho suite get native integrations without third-party connectors.
  • Highly customizable: custom modules, custom fields, Canvas drag-and-drop layouts, and Blueprint workflow automation without requiring developer resources.
  • Small-business reviewers highlight real-time team visibility, daily time savings of 60–90 minutes, and the ability to mold the CRM to any industry vertical.

Object mapping

How Selligent by Marigold objects map to Zoho CRM

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

maps to

Zoho CRM

Contact and Lead

1:many
Fully supported

Selligent Individual records map to both Zoho Contact and Zoho Lead depending on addressability and lifecycle context. Email-addressable individuals with a known organization become Zoho Contacts attached to a Zoho Account; email-addressable individuals without organizational affiliation become Zoho Leads. We resolve this split during scoping using Selligent's addressability flags and any organizational tag properties, and preserve the original Selligent USERID as a custom field selligent_userid__c on both Lead and Contact for cross-reference.

Selligent by Marigold

Company (organizational hierarchy)

maps to

Zoho CRM

Account

lossy
Fully supported

Selligent stores organizational data as custom properties or relation tags rather than a native parent object. We extract company-related field values (company name, industry, revenue tier) from each Individual record, aggregate unique company names, and create Zoho Accounts. The Account acts as the parent for subsequent Contact linking.

Selligent by Marigold

Action List

maps to

Zoho CRM

Custom Module or Deal

1:1
Fully supported

Selligent Action Lists contain LISTID-keyed records with USERID and ACTIONCODE plus custom fields. Each Action List becomes either a Zoho custom module (named with the LISTID for disambiguation) or maps to the Zoho Deals module if the list represents opportunity-stage records. We preserve the full field schema per Action List by extracting the FieldsDefinition array during scoping and creating matching Zoho custom fields before record import.

Selligent by Marigold

Dynamic Segment

maps to

Zoho CRM

Tag or Static Group

lossy
Fully supported

Selligent Dynamic Segments are defined by behavioral and demographic rule sets that cannot be exported. We export the segment membership (the list of contact USERIDs in each segment) and recreate segment membership in Zoho as either Tags applied to the Contact record or as entries in a Zoho Static Group. The segment criteria rules are documented in the handoff inventory for manual rebuild in Zoho using the segment builder.

Selligent by Marigold

Custom Fields

maps to

Zoho CRM

Custom Fields (Leads, Contacts, Accounts, Deals)

lossy
Fully supported

Selligent accepts custom field names as key-value props at record write time without requiring upfront schema registration. Zoho requires custom fields to be defined before data can be written. We extract the full FieldsDefinition array from the customer's Selligent CreateActionList API payload and the Individual record schema during scoping, generate the Zoho custom field creation API calls for each target module (Leads, Contacts, Accounts, Deals), and sequence record imports after field registration completes.

Selligent by Marigold

Tag

maps to

Zoho CRM

Tag

1:1
Fully supported

Selligent tags drive personalization and segmentation and are stored as arrays on each Individual record. We export tag assignments per contact and write them to Zoho Contact Tags using the Zoho CRM Tags API. Tags on Accounts map to Account Tags. The tag vocabulary is preserved as-is with no transformation.

Selligent by Marigold

Behavioral Events

maps to

Zoho CRM

Custom Fields on Contact

1:1
Mapping required

Selligent tracks behavioral events (page views, product interactions, purchase events) for known and anonymous visitors. Zoho does not have a native event stream object, so we migrate the most recent and relevant event summaries as custom fields on the Contact record (e.g., last_purchase_date__c, last_page_view__c, total_sessions__c). Full event history is not migratable as a time-series object in Zoho CRM.

Selligent by Marigold

Email Campaign (history)

maps to

Zoho CRM

Campaign + Campaign Member

1:1
Fully supported

Campaign send history (subject, send date, audience size, open rate, click rate) migrates to Zoho Campaign records linked via Campaign Members to the corresponding Contacts. Message content, template assets, and creative files are not migratable; we document the campaign list and note which assets require re-upload at the destination.

Selligent by Marigold

Engagement: Calls, Emails, Meetings

maps to

Zoho CRM

Task and Event

1:1
Fully supported

Selligent stores engagement history (calls, emails, meetings) on the Individual profile. We export engagement records and write them to Zoho Tasks (for calls and standalone tasks) and Zoho Events (for meetings) linked to the Contact or Account. Activity timestamps are preserved to maintain the chronological timeline. Email content migrates as Task or Note body text.

Selligent by Marigold

User Permissions

maps to

Zoho CRM

User

1:1
Mapping required

Selligent user accounts and role assignments are organizational settings. We export user email addresses, names, and role labels from Selligent where accessible. Zoho User provisioning is customer-controlled; we provide a user mapping table with email-match recommendations and flag any users in Selligent who have no corresponding Zoho user account for admin provisioning before Contact assignment.

Selligent by Marigold

Webhooks

maps to

Zoho CRM

Webhooks (documented only)

lossy
Mapping required

Selligent webhook configurations are not directly exportable via the public API. We document webhook URLs, subscribed event types, and payload configurations during scoping so the customer can recreate them in Zoho using Zoho CRM Webhooks or Zoho Flow. This is a manual rebuild item included in the handoff inventory.

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

Zoho CRM logo

Zoho CRM gotchas

High

API access requires Professional tier or above

High

Subform fields do not export cleanly via CSV

Medium

API credit consumption is non-linear

Medium

Export download links expire in 7 days

Medium

Owner (User) assignments require pre-mapped user IDs

Pair-specific challenges

  • Selligent SDC API caps bulk message throughput at 100 per request

    The Selligent Delivery Cloud API limits bulk message sends to 100 records per request with a 4MB JSON body maximum. For migrations involving tens of thousands of contacts, this requires hundreds of sequential API calls. We handle this with a queuing pipeline that batches contacts into 80-record chunks to account for field overhead, and we parallelize requests across multiple authenticated sessions where the customer's Selligent license supports it. Without this pipeline, large-contact migrations stall or time out.

  • Custom field schema must pre-exist in Zoho before any import

    Selligent accepts custom field names as key-value props at record write time with no upfront schema registration. Zoho CRM requires custom fields to be defined before data can be written. We extract the complete FieldsDefinition array from the customer's Selligent environment during scoping, generate the Zoho custom field creation API calls for each target module, and deploy the schema before record imports begin. Migrations that skip this step result in silent field drops where custom properties are accepted by Selligent but rejected by Zoho on write.

  • Dynamic Segment rule logic is not portable across platforms

    Selligent Dynamic Segments are defined by behavioral and demographic rule sets that evaluate at send time and cannot be exported as static rules. We export segment membership (the resulting contact USERIDs) and recreate that membership as Zoho Tags or Static Group entries, but the dynamic evaluation logic must be rebuilt manually in Zoho's segment builder. We document every segment's criteria in the handoff inventory with a Zoho equivalent recommendation.

  • Behavioral event history has no native destination in Zoho CRM

    Selligent's behavioral event stream (page views, product interactions, purchase events) stores time-series event data per contact that has no equivalent object in Zoho CRM. We migrate the most recent summary fields as custom contact properties, but full event history cannot be represented as a time-series object in Zoho. If event-level reporting is business-critical, customers should plan a separate analytics integration (Zoho Analytics, Mixpanel, or a data warehouse) to receive the event export.

  • Zoho's Data Migration Wizard is CSV-based, not API-driven

    Zoho's built-in Data Migration Wizard accepts CSV files up to 5GB per file with a 25GB total cap and up to 200 files per import batch. For Selligent migrations that require custom field handling, chunked SDC API extraction, and engagement history imports, we use Zoho's REST API (Leads, Contacts, Accounts, Deals endpoints) rather than the wizard to maintain field-level control, custom field mapping, and activity timestamp preservation. The wizard is best suited for simpler record types without custom field dependencies.

Migration approach

Six steps for a successful Selligent by Marigold to Zoho CRM data migration

  1. Discovery and schema extraction

    We audit the source Selligent environment: contact volume, Action List count and schema per list, custom field definitions (FieldsDefinition array), Dynamic Segment count, engagement history volume, user list, and webhook configurations. We pair this with a Zoho CRM edition review (Standard, Professional, or Enterprise) to confirm that required modules (custom fields, Blueprint, Workflows, Campaigns) are available at the target tier. The discovery output is a written migration scope, custom field map, and Zoho edition recommendation.

  2. Zoho custom field and module creation

    We generate and deploy the Zoho custom field schema using the Zoho CRM API. Custom fields are created on the appropriate modules (Leads, Contacts, Accounts, Deals, or custom modules for Action Lists) before any record imports. Field types are matched: Selligent text fields map to Zoho single-line or multi-line text, numeric fields map to number or currency, date fields map to Zoho date or datetime. Custom modules for Action Lists are created with a _C suffix following Zoho convention and linked to Accounts or Contacts via lookup fields.

  3. Selligent data export and transformation

    We extract data from Selligent using the Individual API, paginating through contacts in batches of 2000 to respect rate limits and using exponential backoff on 429 responses. For each batch, we apply the field mapping transformation: USERID is preserved as selligent_userid__c, custom field values are written to their Zoho equivalents, and organization names are aggregated into a staging table for Account creation. Action List records are extracted per LISTID with the full field payload.

  4. Account and Contact import in dependency order

    We import data into Zoho in dependency order: Accounts are created first from the aggregated organization table, then Contacts are created with the resolved AccountId lookup, then Leads are created for unassociated contacts. Owner resolution maps Selligent owner email to Zoho User email. Each phase emits a row-count reconciliation report showing records written, records skipped (with reason), and duplicate count before the next phase begins.

  5. Engagement history and Action List migration

    Call, email, and meeting engagement records are imported as Zoho Tasks and Events linked to the Contact or Account. Action List records are written to their corresponding custom modules with lookup resolution to the parent Account or Contact. Tag assignments are written via the Zoho Tags API after all contact records are settled. We validate tag coverage against the original Selligent export to confirm no tag assignments were dropped.

  6. Cutover, validation, and automation rebuild handoff

    We run a final delta migration of any records modified during the migration window, then deliver the handoff package including the journey and segment inventory (with rule documentation for manual Zoho rebuild), webhook configuration table, campaign list with asset re-upload checklist, and user mapping table with any unresolved Zoho User gaps flagged for admin provisioning. Workflows, Blueprints, and automation rules are not migrated as code; the inventory document enables your admin to rebuild them in Zoho Workflows.

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.
Zoho CRM logo

Zoho CRM

Destination

Strengths

  • Generous free tier (3 users) with real CRM functionality — no artificial feature restrictions that prevent valid use cases.
  • Per-seat pricing is transparent and predictable; no contact-based billing surprises that inflate monthly invoices.
  • Blueprint visual workflow builder lets sales ops teams automate stage progressions without developer involvement.
  • Canvas drag-and-drop layout editor lets non-technical users customize module views and forms per role.
  • Active development cadence: API v8 is well-documented, supports bulk endpoints, and COQL queries handle complex filtering.

Weaknesses

  • Poor support quality and inconsistent SLA — Enterprise tier requires 50+ user minimum for Priority Phone support.
  • Daily export limits in the UI vary by plan tier, making large dataset extraction slow and planning-dependent.
  • Zia AI features are gated behind $40+/user Enterprise tier, not available to most SMB customers who chose Zoho for cost savings.
  • User-reported occasional UI inconsistencies and performance slowdowns on large datasets with many custom fields.
  • No EU-hosted option limits appeal for GDPR-sensitive companies; some competitors offer data residency guarantees Zoho does not.

Complexity grading

How hard is this migration?

Standard CRM migration. All 8 core objects map 1:1 between Selligent by Marigold and Zoho CRM.

B

Overall complexity

Standard migration

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

  • Object compatibility

    A

    All 8 core objects map 1:1 between Selligent by Marigold and Zoho CRM.

  • 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 Zoho CRM 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 Zoho CRM data migrations

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

Can't find your answer?

Walk through your Selligent by Marigold to Zoho CRM 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 50,000 contacts, up to 50 custom fields, and a single Action List structure. Migrations with behavioral event history, multiple Action Lists requiring custom module creation, engagement history imports (calls, emails, meetings), or large organization hierarchies move to six to nine weeks because of the custom module build, parent-record lookup resolution, and the multi-phase import sequencing required in Zoho.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Selligent by Marigold.
Land in Zoho CRM, 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