CRM migration
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
Source
Zoho CRM
Destination
Compatibility
6 of 11
objects map 1:1 between Selligent by Marigold and Zoho CRM.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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 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)
Zoho CRM
Contact and Lead
1:manySelligent 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)
Zoho CRM
Account
lossySelligent 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
Zoho CRM
Custom Module or Deal
1:1Selligent 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
Zoho CRM
Tag or Static Group
lossySelligent 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
Zoho CRM
Custom Fields (Leads, Contacts, Accounts, Deals)
lossySelligent 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
Zoho CRM
Tag
1:1Selligent 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
Zoho CRM
Custom Fields on Contact
1:1Selligent 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)
Zoho CRM
Campaign + Campaign Member
1:1Campaign 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
Zoho CRM
Task and Event
1:1Selligent 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
Zoho CRM
User
1:1Selligent 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
Zoho CRM
Webhooks (documented only)
lossySelligent 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.
| Selligent by Marigold | Zoho CRM | Compatibility | |
|---|---|---|---|
| Contact (Individual) | Contact and Lead1:many | Fully supported | |
| Company (organizational hierarchy) | Accountlossy | Fully supported | |
| Action List | Custom Module or Deal1:1 | Fully supported | |
| Dynamic Segment | Tag or Static Grouplossy | Fully supported | |
| Custom Fields | Custom Fields (Leads, Contacts, Accounts, Deals)lossy | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| Behavioral Events | Custom Fields on Contact1:1 | Mapping required | |
| Email Campaign (history) | Campaign + Campaign Member1:1 | Fully supported | |
| Engagement: Calls, Emails, Meetings | Task and Event1:1 | Fully supported | |
| User Permissions | User1:1 | Mapping required | |
| Webhooks | Webhooks (documented only)lossy | Mapping required |
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
Zoho CRM gotchas
API access requires Professional tier or above
Subform fields do not export cleanly via CSV
API credit consumption is non-linear
Export download links expire in 7 days
Owner (User) assignments require pre-mapped user IDs
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Selligent by Marigold
Source
Strengths
Weaknesses
Zoho CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Selligent by Marigold and Zoho CRM.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Selligent by Marigold and Zoho CRM.
Object compatibility
All 8 core objects map 1:1 between Selligent by Marigold and Zoho 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 Zoho CRM migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Selligent by Marigold
Other ways to arrive at Zoho 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.