Migrate from NEON-dX to Twenty CRM

NEON-dX's unified 360-degree profile stores demographic fields, behavioral signals, and digital footprint in a single record. Twenty CRM separates individuals into Contact and organizations into Company. We decompose the source profile by splitting demographic data (name, email, phone, address) onto Contact, organizational data (company name, industry, employee count, annual revenue) onto Company, and behavioral signals (engagement score, channel preferences, acquisition source) into custom fields on Contact. The Company is looked up or created first during migration so that the Contact-Company relationship is established at insert time. Any profile records without an organizational affiliation become standalone Contacts.

NEON-dX behavioral segments are defined by rule criteria evaluated against customer event streams. These rules cannot be replicated as a dynamic engine in Twenty CRM because the platform has no native event-stream segmentation. We migrate the segment membership snapshot as static Tag values (one tag per segment the contact was a member of at migration time) and deliver a written segment rule inventory with recommended tag-based equivalents in Twenty CRM. Segment counts will re-evaluate after migration based on the customer's new behavioral data collection approach.

NEON-dX campaigns and associated offer content migrate as structured records with templating metadata. We map campaign name, description, start and end dates, and budget to Twenty CRM Opportunity fields (Name, Description, CloseDate, Amount). Offer content (discounts, promotions, product references) migrates to a custom Offer object or Opportunity Line Items depending on the customer's data model. Rich media assets (images, templates) require separate file transfer and are documented in the media asset manifest.

NEON-dX journeys are multi-step orchestration flows with branching logic, wait conditions, and channel assignments. Twenty CRM has no native journey orchestration engine. We extract every journey definition from NEON-dX (step sequence, branching conditions, wait durations, channel assignments) and deliver a written journey inventory document describing each journey in Twenty CRM terms. Channel assignments require re-registration because credentials cannot be exported. The customer's admin rebuilds journey logic using Twenty CRM's automation capabilities or a third-party orchestration layer post-migration.

NEON-dX churn propensity, LTV, and customer value scores are generated by Flytxt's proprietary ML pipeline with live training data. They cannot be meaningfully exported because they require NEON-dX's feature engineering environment and become immediately stale upon export. We preserve the score field names and the last-known values as static custom fields in Twenty CRM for audit reference, but we do not treat these as actionable post-migration. Customers should plan a re-scoring period using Twenty CRM's own analytics views or a connected BI tool after migration completes.

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, build a dependency graph for formula fields that reference other custom objects, map API names to Twenty CRM's custom object naming conventions, pre-create the destination schema in Twenty CRM (including all custom fields, lookup relationships, and any validation rules), and import in dependency order. Custom objects with lookups to standard objects (Contact, Company, Opportunity) are imported after the standard objects to satisfy the foreign key constraint.

NEON-dX channel configurations (SMS gateway credentials, email sender IP addresses, push notification keys, API tokens) are stored with environment-specific scoping and cannot be exported as-is. We document every channel type, configuration parameter, and current credential status during the discovery phase and deliver a re-authentication checklist for each channel. The customer's admin registers fresh credentials in Twenty CRM before cutover. Without valid credentials, any migrated journey or campaign that references a channel will fail silently.

NEON-dX email engagements (sent, opened, clicked, bounced) migrate to Twenty CRM as Comment records linked to the target Contact, with the original timestamp preserved in the record's createdAt field. Email subject, body, and metadata (open count, click count, bounce status) migrate as structured fields on the Comment record. We resolve the Contact reference by email match before insert to ensure the timeline links correctly.

NEON-dX call engagements (duration, disposition, recording URL) migrate to Twenty CRM as Task records linked to the target Contact and optionally to the related Company or Opportunity. Call duration, disposition, and recording URL migrate to custom Task fields. Activity ordering is preserved by setting the Task's due date to the original NEON-dX timestamp.

NEON-dX meeting engagements migrate to Twenty CRM CalendarEvent records with title, description, start and end times, and location preserved. Attendee information migrates to CalendarEventParticipant records linked to the CalendarEvent and the attending Contact records.

NEON-dX note engagements migrate to Twenty CRM Comment records linked to the parent Contact, Company, or Opportunity. Note body migrates as rich text. Attachments migrate as File records linked via the target record's ID. Note timestamp is preserved in the Comment's createdAt field.

NEON-dX consent management records, data retention policies, and GDPR/CCPA opt-out flags migrate to Twenty CRM as custom fields on Contact (opt-in status, consent timestamp, consent source, retention category). We flag any contacts with active suppression or withdrawal flags that require special handling during migration to ensure they are not re-enrolled in communications post-migration. The customer configures Twenty CRM's data retention settings manually after migration.