Migrate from NEON-dX to monday CRM

NEON-dX customer profiles compose demographic data, behavioral signals, and digital footprint into a unified record. We map standard profile fields (name, email, phone, address, demographics) directly to Monday.com Person fields. Fields populated by NEON-dX's AI pipeline (propensity signals, engagement scores) are flagged as AI-derived and preserved in custom columns for re-evaluation post-migration. Any multi-value demographic attributes are mapped to multi-select columns in Monday.com. Profile completeness varies by data source in NEON-dX; we preserve null values where they exist rather than inferring missing data.

NEON-dX company records map to Monday.com Organization items. The company name becomes the Organization name, and the NEON-dX company ID is preserved in a custom text column as a reference key for downstream lookups. Address, industry, and revenue fields map to their Monday.com equivalents or custom columns. Organizations are imported before Person records so that the People-Organization relationship is established at insert time.

NEON-dX behavioral segments are rule-based criteria evaluated against customer event streams. We transfer the segment definition rules as written documentation (the rule criteria, conditions, and logical operators). In Monday.com, we create Groups that represent the target audience or a filtered board view that approximates the segment logic using available column values. Segment membership re-evaluates post-migration because Monday.com does not have a live event-stream evaluation engine equivalent to NEON-dX's behavioral engine. Customers should expect different segment counts immediately after cutover as the destination platform re-evaluates membership against its own data.

NEON-dX campaigns and their associated offer content migrate as board items with campaign-type columns (campaign name, status, channel, start date, end date, budget). Rich media assets (images, attachments) require separate file transfer via Monday.com's file upload API or a designated storage integration. Channel-specific offer formats (SMS text, push notification copy) are mapped to long-text columns with channel tags. Campaign templates from NEON-dX's best practices library that are standard Flytxt templates are flagged as non-portable; custom campaign templates migrate as board templates in Monday.com.

NEON-dX multi-step journey flows with branching logic, wait conditions, and channel assignments are represented as Monday.com boards with a Status column for each journey stage. The journey entry trigger (event-based in NEON-dX) is documented as a written specification for rebuilding as a Monday.com Automation Center recipe. Wait conditions and time delays do not have a direct Monday.com equivalent and must be rebuilt manually using the Automation Center's delay features. Channel assignments (email, SMS, push) migrate as status column tags but require re-authentication of channel credentials in the destination.

Predictive churn, LTV, and propensity scores are generated by NEON-dX's proprietary ML pipeline using live training data and feature engineering that is tightly coupled to the source platform. These scores are computed dynamically and become stale immediately upon export. We do not transfer them as static values. We preserve the model configuration and feature list in a written document for the customer's data science team to re-implement using Monday.com's AI capabilities or an external analytics tool. Customers should expect a re-warming period of two to eight weeks before new predictive scores become actionable post-migration.

NEON-dX custom object types (with standard, formula, and lookup field types) migrate to Monday.com as item types with equivalent custom columns. Formula fields that reference other custom objects require a dependency graph built during schema discovery; migration sequencing respects this dependency order so that parent records exist before child records are inserted. Cross-object lookups in NEON-dX map to Monday.com Relations, which link items across boards bidirectionally. Any validation rules or conditional requirements from NEON-dX formula fields are documented as column validation rules in Monday.com or flagged for manual configuration.

Channel configurations (SMS gateway credentials, email sender IPs, push notification keys, API tokens) are environment-scoped in NEON-dX and cannot be exported as-is. We document the channel type, configuration schema, and any endpoint URLs during the discovery phase. Re-authentication of each channel in Monday.com's Integration Center is required post-migration. We provide a re-authentication checklist for each channel type (email provider, SMS gateway, push notification service) as part of the cutover handoff. Without valid credentials, automation recipes in Monday.com that rely on those channels will fail silently.