Migrate your NEON-dX data
Enterprise AI-driven B2C marketing automation and customer value management platform by Flytxt, built for telecom, retail, and consumer goods companies that need predictive analytics, behavioral segmentation, and omnichannel campaign orchestration at scale.
In its favor
Why people choose NEON-dX
The signal that keeps NEON-dX on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Targets large consumer-facing enterprises in telecom, retail, and CPG that need AI-powered churn reduction, upsell, and retention campaign orchestration at scale
Packages predictive analytics, behavioral segmentation, and omnichannel marketing automation in a single enterprise subscription without requiring separate tools
Offers pre-built industry templates and a best practices library for campaign and journey design, reducing time-to-launch for new marketing teams
Provides omni-channel connectors with open APIs to activate campaigns across email, SMS, push, and digital channels from a unified journey canvas
Delivers real-time dashboards and anomaly detection that flag campaign performance deviations without requiring manual BI setup
Enterprise pricing and custom subscription negotiation create budget unpredictability, especially for mid-market teams that expected tiered SaaS pricing
Complex AI model outputs such as churn scores and propensity models require interpretation support that many teams lack internally
Integration with existing data warehouses and BI tools is limited to pre-built connectors, forcing custom ETL work for non-standard architectures
Onboarding onto the platform requires significant training and change management for teams accustomed to simpler marketing automation tools
Multi-channel journey orchestration across digital channels introduces technical complexity that exceeds the capabilities of typical marketing operations teams
Reasons to switch
Why people leave NEON-dX
The recurring reasons buyers give for replacing NEON-dX. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where NEON-dX fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
NEON-dX pricing overview
NEON-dX follows a tiered subscription model: a free tier for evaluation and prototyping, a usage-based Launch tier with typical spend around $15–50/month for development workloads, and a custom enterprise tier priced by user count, data volume, and deployment scope with dedicated support and SLA commitments.
Free
Tier 1 of 3
$0
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on NEON-dX's schedule — see our quote-based pricing →
What gets migrated
NEON-dX object support
Object-by-object support for NEON-dX migrations. Per-pair details surface during scoping.
Customer Profiles (360° View)
Mapping requiredNEON-dX composes each profile from demographic, behavioral, and digital footprint data. Profile completeness varies by data source. We preserve all standard profile fields and flag fields populated by AI models that may behave differently in a destination with different data enrichment signals.
Behavioral Segments
Mapping requiredSegments are built from rule-based criteria and ML model outputs. Migration preserves the segment definition rules but re-evaluates membership after import because the underlying behavioral events may differ in the destination platform.
Campaigns / Offers
Mapping requiredCampaigns and their associated offer content are migrated as structured records with templating metadata. Rich media assets require separate file transfer. We flag any channel-specific offer formats that are not compatible with the destination.
Customer Journeys
Mapping requiredJourneys are multi-step orchestration flows with branching logic, wait conditions, and channel assignments. Migration preserves the journey structure but re-registers channel credentials on the destination because webhook and API credentials are environment-specific.
Predictive Scores (Churn, Propensity, LTV)
Not in this platformPredictive scores are model-generated outputs that depend on NEON-dX's proprietary ML pipeline and training data. These cannot be meaningfully transferred because they require the source platform's live feature engineering environment to remain valid.
Custom Objects
Mapping requiredNEON-dX supports custom object types with standard, formula, and lookup field types via its API. We discover the custom object schema at migration time and generate field-level mappings for each destination system.
Channels and Connectors
Mapping requiredChannel configurations such as SMS gateways, email IPs, push credentials, and API connectors are environment-scoped. We migrate the channel type and configuration schema but require re-authentication of credentials in the destination environment.
Analytics and Dashboards
Mapping requiredPre-built dashboards and custom reports reference platform-native metric definitions. We migrate the report structure and column configurations. Destination metric data populates after migration completes based on live destination events.
Privacy and Governance Rules
Mapping requiredConsent management, data retention policies, and governance frameworks are platform-native constructs. We map these to equivalent destination settings and flag any GDPR or CCPA opt-out records that require preservation across systems.
Campaign Templates and Best Practices Library
Mapping requiredPre-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.
| Object | Support | Notes |
|---|---|---|
| Customer Profiles (360° View) | Mapping required | NEON-dX composes each profile from demographic, behavioral, and digital footprint data. Profile completeness varies by data source. We preserve all standard profile fields and flag fields populated by AI models that may behave differently in a destination with different data enrichment signals. |
| Behavioral Segments | Mapping required | Segments are built from rule-based criteria and ML model outputs. Migration preserves the segment definition rules but re-evaluates membership after import because the underlying behavioral events may differ in the destination platform. |
| Campaigns / Offers | Mapping required | Campaigns and their associated offer content are migrated as structured records with templating metadata. Rich media assets require separate file transfer. We flag any channel-specific offer formats that are not compatible with the destination. |
| Customer Journeys | Mapping required | Journeys are multi-step orchestration flows with branching logic, wait conditions, and channel assignments. Migration preserves the journey structure but re-registers channel credentials on the destination because webhook and API credentials are environment-specific. |
| Predictive Scores (Churn, Propensity, LTV) | Not in this platform | Predictive scores are model-generated outputs that depend on NEON-dX's proprietary ML pipeline and training data. These cannot be meaningfully transferred because they require the source platform's live feature engineering environment to remain valid. |
| Custom Objects | Mapping required | 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 and generate field-level mappings for each destination system. |
| Channels and Connectors | Mapping required | Channel configurations such as SMS gateways, email IPs, push credentials, and API connectors are environment-scoped. We migrate the channel type and configuration schema but require re-authentication of credentials in the destination environment. |
| Analytics and Dashboards | Mapping required | Pre-built dashboards and custom reports reference platform-native metric definitions. We migrate the report structure and column configurations. Destination metric data populates after migration completes based on live destination events. |
| Privacy and Governance Rules | Mapping required | Consent management, data retention policies, and governance frameworks are platform-native constructs. We map these to equivalent destination settings and flag any GDPR or CCPA opt-out records that require preservation across systems. |
| Campaign Templates and Best Practices Library | Mapping required | 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. |
Gotchas
What to watch for in NEON-dX migrations
Issues we've hit on past NEON-dX migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Predictive model outputs are not transferable
Channel credentials require re-authentication post-migration
Custom object schema discovery requires API enumeration
Segment membership is event-dependent and re-evaluates post-migration
| Severity | Issue |
|---|---|
| High | Predictive model outputs are not transferable |
| Medium | Channel credentials require re-authentication post-migration |
| Medium | Custom object schema discovery requires API enumeration |
| Medium | Segment membership is event-dependent and re-evaluates post-migration |
Leaving NEON-dX?
Where NEON-dX customers move next
12 destinations NEON-dX can migrate to.
How a NEON-dX migration works
Four steps, NEON-dX-specific
Connect
API key / Bearer token (environment-scoped) into NEON-dX. Scopes limited to read-only on the data we move.
Map
We translate NEON-dX-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate NEON-dX quirks before production.
Migrate
Full migration with NEON-dX rate-limit handling. Rollback available throughout.
FAQ
NEON-dX migration FAQ
Answers to the questions buyers ask most during NEON-dX migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your NEON-dX migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate NEON-dX.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your NEON-dX setup and destination — written quote back within a business day.