Migrate from NEON-dX to Nutshell

NEON-dX composes each customer profile from demographic fields, behavioral signals, and digital footprint data across channels. We split this into Nutshell Contact (individual-level fields including name, email, phone, and demographic attributes) and Nutshell Company (organization-level fields including company name, domain, and industry). The NEON-dX profile ID is preserved as a custom field neon_profile_id__c on the Contact for audit traceability. Any behavioral signal fields that have no direct Nutshell equivalent are flagged as requiring a custom field or third-party reporting integration.

NEON-dX behavioral segments are defined by rule-based criteria evaluating against customer event streams. We preserve the segment definition rules as a written configuration document mapping each NEON-dX rule to an equivalent Nutshell List filter criterion. Segment membership does not migrate as a static attribute because Nutshell's List membership re-evaluates based on the imported Contact data. The customer rebuilds List membership in Nutshell using the segment rule documentation we deliver.

NEON-dX campaigns and their associated offer content migrate as Nutshell Campaign records with campaign name, type, and status preserved. Rich media assets (images, PDFs) require separate file transfer via Nutshell's file management or an attached ContentDocument equivalent. Any channel-specific offer formats unique to NEON-dX's journey canvas are flagged as requiring redesign in Nutshell's campaign structure.

NEON-dX offer catalogs contain product-level offer content tied to journey triggers. We map offer records to Nutshell Campaign records with product associations where applicable. Offer-level targeting rules are documented as written configuration because Nutshell does not support the same offer catalog abstraction. The customer rebuilds offer targeting in Nutshell's campaign or product configuration layer.

NEON-dX journeys are multi-step orchestration flows with branching logic, wait conditions, and channel assignments. We do not migrate journey configurations as code because Nutshell's automation layer does not support the same event-triggered branching model. We deliver a written journey inventory document describing each journey's trigger, steps, conditions, and channel assignments so the customer's team can rebuild them in Nutshell's automation builder.

NEON-dX generates churn propensity, LTV, and propensity-to-buy scores using its proprietary ML pipeline and live training data. These scores are computed dynamically and are tightly coupled to NEON-dX's feature engineering environment. We do not export predictive scores as static values because they become stale immediately upon export. We deliver a written model configuration summary documenting the score types, input features, and intended thresholds so the customer can evaluate third-party scoring tools for re-implementation in Nutshell.

NEON-dX supports custom object types with standard, formula, and lookup field types via its API. We discover the custom object schema at migration time using API enumeration, generate the equivalent Nutshell custom object schema, and map each field by type (text to text, number to number, date to date, lookup to lookup). Any formula fields are documented as computed fields requiring rebuild in Nutshell's formula syntax. Custom objects with lookup dependencies are sequenced last to ensure parent objects exist before child import.

Channel configurations (SMS gateways, email sender IPs, push credentials, API tokens) are environment-scoped in NEON-dX and cannot be exported. We document the channel type, configuration schema, and credentials list during discovery and deliver a re-authentication checklist for each channel type. Without valid credentials, channel activation will fail in Nutshell. The customer re-enters credentials in Nutshell's integration settings before activating any migrated campaign triggers.

NEON-dX pre-built and custom dashboards reference platform-native metric definitions tied to the predictive analytics layer. We migrate the report structure and column configurations as Nutshell Reports, but destination metric data populates after migration completion based on Nutshell's data model. AI-generated metrics and anomaly detection widgets do not have equivalents in Nutshell's reporting layer and are documented for replacement with manual review processes or third-party BI tools.