Migrate from NEON-dX to Freshsales

NEON-dX composes each customer as a unified profile combining demographic fields, behavioral signals, and digital footprint across channels. We split this into Freshsales Contact (person-level attributes) and Account (organization-level attributes) during migration. Any behavioral signal fields stored as custom properties on the NEON-dX profile migrate to Freshsales custom fields on Contact or Account depending on whether the signal is person-level or organization-level. The original profile completeness score (if stored as a field rather than computed) migrates as a custom field for reference.

NEON-dX segments are defined by rule criteria evaluated against customer event streams. We migrate the segment definition rules as written logic (stored in a mapping document) and recreate them as Freshsales segment filter rules where the destination platform supports equivalent conditions. Where Freshsales cannot replicate a specific event-based rule, we flag the gap and recommend a Freddy AI-based scoring approach to approximate the segment. Segment membership re-evaluates on Freshsales based on that platform's activity data; customers should expect different member counts immediately post-migration.

NEON-dX campaigns and their associated offer content migrate as structured records with templating metadata. Offer name, description, eligibility criteria, and channel assignment map to Freshsales Campaign records and custom fields. Rich media assets (images, files) require separate file transfer and reattachment. Any channel-specific offer formats exclusive to NEON-dX are flagged as unsupported and documented for the customer's admin to redesign in Freshsales or Freshmarketer.

NEON-dX journeys are multi-step orchestration flows with branching logic, wait conditions, and channel assignments. We document the complete journey structure (steps, branches, triggers, delays, channel assignments) in a written inventory delivered to the customer. Freshsales does not natively support NEON-dX-style omnichannel journey orchestration; the equivalent is Freshsales Workflows for CRM automation and Freshmarketer for multi-channel campaign automation. We do not migrate journey logic as executable code; the admin rebuilds journeys in the destination platform using the inventory as a specification.

NEON-dX generates churn propensity, LTV, and customer value scores using its proprietary ML pipeline with live training data. These scores are computed dynamically and are tightly coupled to NEON-dX's feature engineering environment. They cannot be exported as static values because they become stale immediately upon export and cannot be re-created in Freshsales without NEON-dX's underlying model artifacts. We do not transfer predictive scores. Instead, we preserve the behavioral signals and profile attributes that fed the original model so that Freshsales Freddy AI has equivalent input data for re-scoring. Customers should plan for a four-to-eight week re-warming period before Freddy AI scores become actionable.

NEON-dX supports custom object types with standard, formula, and lookup field types accessible via its REST API. We enumerate the live custom object schema at migration time using API calls because no public data dictionary is available. Formula fields that reference other custom objects require a dependency graph to be built before import sequencing can begin. Custom objects migrate to Freshsales Custom Modules, which are available from the Growth tier. We pre-create the destination schema including all custom fields, relationship fields, and validation rules before any data import.

Channel configurations in NEON-dX (SMS gateways, email sender IPs, push notification keys, API tokens) are stored with environment-specific scoping and cannot be exported as valid credentials. We document all channel types, configuration parameters, and connection settings during the discovery phase and deliver a re-authentication checklist for each channel. The customer re-enters credentials in Freshsales (or Freshmarketer for multi-channel automation) before journey automation can run. Without valid credentials, channel sends fail silently in the destination environment.

NEON-dX pre-built dashboards and custom reports reference platform-native metric definitions and anomaly detection algorithms that are specific to the CVM context. We migrate the report structure (column configurations, filter logic, grouping) as Freshsales reports and dashboards. Destination metric data populates after migration completes as Freshsales accumulates activity data. Anomaly detection alerts configured in NEON-dX do not migrate; these require reconfiguration in Freshsales using Freshsales Analytics or a third-party BI tool.

NEON-dX ships a library of pre-built journey and campaign templates for telecom, retail, and CPG use cases. We flag which templates are native to NEON-dX and not portable. Custom templates built by the customer's team migrate as documentation only (structure and parameters) rather than as executable templates. Freshsales and Freshmarketer have their own template libraries that the customer's admin evaluates for equivalent coverage post-migration.