Migrate from NEON-dX to HighLevel

NEON-dX composes each customer as a single 360-degree profile combining demographic, behavioral, and digital footprint data. GoHighLevel separates this into Contact (person-level data) and Company (organization-level data) with a many-to-one relationship from Contact to Company. We split NEON-dX profile fields during migration: name, email, phone, and behavioral attributes migrate to Contact; organization name, domain, industry, and company-level attributes migrate to Company. The Company record is created first so that Contact import satisfies the Lookup relationship. Any behavioral attributes stored on the NEON-dX profile that have no GoHighLevel Contact equivalent are flagged for custom field creation.

NEON-dX behavioral segments are rule-based criteria evaluated against live event streams. Segment membership is not a static attribute and does not transfer as a stored count. We transfer the segment definition rules as a written inventory mapping to GoHighLevel Smart List filter criteria and Tags. On the destination, segment membership re-evaluates based on GoHighLevel's event and contact data. Customers should not expect identical segment counts immediately after cutover. We document each segment's rule structure so the customer's GoHighLevel admin can replicate the filter logic in Smart Lists.

NEON-dX campaigns and their associated offer content are structured records with templating metadata. We map campaigns to GoHighLevel Campaign records for tracking and reporting, and map campaign offer content to GoHighLevel Workflow templates and Opportunities. Rich media assets require separate file transfer. Channel-specific offer formats that use NEON-dX proprietary templating syntax are flagged as requiring template recreation in GoHighLevel's email and SMS editors. Revenue-linked campaign offers map to Opportunities with a Campaign-to-Opportunity relationship.

NEON-dX customer journeys are multi-step orchestration flows with branching logic, wait conditions, and channel assignments. We preserve the journey structure as a written inventory documenting trigger conditions, step sequence, branch logic, delay rules, and channel assignments. GoHighLevel's Workflow builder uses a different trigger model and node structure, so the journey automation does not transfer as functional code. The customer's GoHighLevel admin or a GoHighLevel-certified partner rebuilds each journey using the documentation we deliver. Channel credentials in the journey are flagged as requiring re-authentication before the rebuilt workflow can execute.

NEON-dX generates churn propensity, LTV, and customer value 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 and require the source platform's live data lineage. Instead, we preserve the score variable names and business context in the migration inventory. GoHighLevel's built-in AI features support scoring logic in workflows but do not replicate NEON-dX's predictive models. Customers should expect a re-warming period after migration before new scoring data becomes actionable in GoHighLevel.

NEON-dX supports custom object types with standard, formula, and lookup field types via its REST API. GoHighLevel natively supports Custom Objects with relationship fields and custom field types. We enumerate the live NEON-dX custom object schema via API at migration time, generate field-level mappings to GoHighLevel custom object equivalents, and pre-create the destination schema before any data import. Any formula fields that reference other custom objects require a dependency graph built during discovery so that objects with inbound lookups are created before objects with outbound references. Custom object naming in GoHighLevel must follow GoHighLevel's naming conventions.

Channel configurations in NEON-dX such as SMS gateway credentials, email sender IPs, push notification keys, and channel API tokens are stored with environment-specific scoping. These cannot be exported as-is. We document all channel type and configuration schema during discovery and deliver a re-authentication checklist for each channel. SMS integrations migrate to GoHighLevel's native Twilio integration requiring new Twilio credentials. Email integrations require SMTP reconfiguration with new sender domains. Push notification credentials require new Firebase or equivalent setup. Without valid channel credentials, journey automation rebuilt in GoHighLevel Workflows will fail silently at the channel dispatch step.

NEON-dX pre-built dashboards and custom reports reference platform-native metric definitions tied to Flytxt's analytics engine. We migrate the report structure and column configurations as a written specification. Destination metric data populates only after migration completes and GoHighLevel has accumulated sufficient event data. GoHighLevel's dashboard builder operates differently with different available metrics. Customers should plan a dashboard reconstruction phase post-migration using the migrated report specifications as reference.

Consent management, data retention policies, and governance frameworks in NEON-dX are platform-native constructs. We map these to equivalent GoHighLevel contact preference settings and GDPR compliance options. Any GDPR or CCPA opt-out records that represent legal obligations transfer as contact-level opt-out flags in GoHighLevel. Governance rules around data retention require manual configuration in GoHighLevel's account settings post-migration.

NEON-dX pre-built journey and campaign templates are available in the platform's template library. We migrate custom templates and flag which standard templates are native to NEON-dX and not portable. GoHighLevel's template library contains its own set of pre-built workflow and funnel templates. The customer's team selects equivalent GoHighLevel templates during the post-migration configuration phase using our migrated template inventory as a functional reference.