Migrate from NEON-dX to Zoho CRM

NEON-dX customer profiles contain demographic attributes, behavioral signals, and digital footprint data across channels. We map demographic fields (name, email, phone, address) to standard Zoho CRM Contact fields and flag behavioral attributes and channel footprint data for custom field creation before import. Any profile fields populated by AI-generated predictive scores are noted separately since those scores do not migrate (see Predictive Scores mapping). Profile completeness varies by data source in NEON-dX, so we audit record-level field fill rates during discovery to set expectations for post-migration data quality.

NEON-dX profiles for B2B companies (telecom, retail, CPG enterprise accounts) include company-level data that maps to Zoho CRM Account. We split company-level attributes from individual contact attributes during the transform phase, creating Account records first so that Contact-to-Account lookups are resolved at insert time. Company domain, annual revenue, and industry classification map to standard Account fields; account-level predictive scores do not migrate.

NEON-dX behavioral segments are defined by rule criteria that evaluate against customer event streams. We transfer the segment definition rules as Zoho CRM Tags (for simple rule-based segments) or as Custom Fields with picklist values representing segment membership at migration time. For complex multi-condition segment rules, we document the equivalent Zoho CRM Advanced Filter criteria so that the customer's admin can rebuild the segment as a Zoho View. Segment membership re-evaluates post-migration because Zoho CRM evaluates membership based on its own event data, not NEON-dX's event history.

NEON-dX campaigns and their associated offer catalogs migrate as Zoho CRM Deals. Campaign name maps to Deal name, offer metadata maps to custom fields on the Deal, and campaign status maps to Deal stage. Rich media assets embedded in offer content require separate file transfer and re-attachment to the migrated Deal record. Any channel-specific offer formats (SMS text offers vs email HTML offers) are flagged during discovery because they may require format conversion to Zoho's supported templates.

NEON-dX multi-step customer journeys with branching logic, wait conditions, and channel assignments have no direct Zoho CRM equivalent. We map the journey structure to Zoho CRM Blueprint stages for process-driven flows and to Workflow Rules for event-triggered actions. Complex multi-channel journey orchestration that uses proprietary NEON-dX event taxonomy requires re-alignment to Zoho's event model during the rebuild phase. We deliver a written journey inventory documenting the original structure and recommended Blueprint/Workflow equivalents for the customer's admin to implement post-migration.

NEON-dX churn propensity, LTV, and customer value scores are generated by Flytxt's proprietary ML pipeline and are tightly coupled to the platform's feature engineering environment. These scores cannot be meaningfully exported as static values because they require NEON-dX's live training data to remain current. We do not transfer predictive scores. During discovery, we capture the feature variables used in each score model and document how to replicate equivalent scoring in Zoho CRM using Zia AI's predictive lead scoring (Enterprise tier) or custom Deluge logic using the migrated behavioral attributes as input variables. A re-warming period of 4-8 weeks is typical before new predictive scores become actionable in Zoho.

NEON-dX exposes custom object types with standard, formula, and lookup field types via its REST API. We enumerate the live custom object schema at the start of each engagement because NEON-dX does not publish a public data dictionary for custom objects. Any formula fields that reference other custom objects require a dependency graph to be built before import sequencing begins. Custom objects migrate to Zoho CRM Custom Modules, with lookup relationships preserved as Zoho Lookup fields. Formula field logic does not migrate automatically; we document the original formula expression so the customer's admin can recreate it as a Zoho CRM Formula field post-migration.

NEON-dX channel configurations (SMS gateway credentials, email sender IPs, push notification keys, and channel API tokens) are stored with environment-specific scoping and cannot be exported as-is. We document the channel type, configuration schema, and any third-party provider references (Twilio for SMS, SendGrid for email, Firebase for push) during the discovery phase and deliver a re-authentication checklist for each channel type. Without valid credentials re-registered in Zoho CRM, journey automation will fail silently post-migration.

NEON-dX pre-built dashboards and custom reports reference platform-native metric definitions tied to the CVM event model. We migrate report structure and column configurations to Zoho CRM Reports and map standard metrics (contact count, deal value, campaign engagement) to equivalent Zoho field references. Metric data populates after migration completion. Reports that reference proprietary NEON-dX scoring metrics require remapping to Zoho Analytics equivalents or to Zia AI anomaly definitions. Dashboard layout migrates as a written specification for manual reconstruction in Zoho Analytics.

NEON-dX consent management, data retention policies, and GDPR/CCPA opt-out records are platform-native governance constructs. We map GDPR and CCPA opt-out records to Zoho CRM Contact fields (HasOptedOutOfEmail for email consent, custom fields for SMS and push consent flags). Data retention policy logic does not have a native Zoho CRM equivalent; we document the original NEON-dX retention schedule and recommend Zoho CRM Data Processing Consent fields or a Zoho Deluge-based automation for record cleanup scheduling.