Migrate from NEON-dX to Pipedrive

NEON-dX Customer Profiles combine demographic data, behavioral signals, and digital footprint into a single record. We split this into Pipedrive Person (name, email, phone, title, address fields) and Organization (company name, domain, industry, size). The NEON-dX profile ID is preserved as a custom field neon_profile_id__c for audit and cross-reference. Any behavioral attributes stored as custom fields on the profile migrate to custom fields on the Person record in Pipedrive.

NEON-dX behavioral segments are defined by rule criteria evaluated against live event streams and are not static membership attributes. We migrate the segment definition logic as a written document describing each segment's rule criteria. Segment membership cannot be preserved as static values because it re-evaluates on the destination. In Pipedrive, we create static Person Lists representing the current segment membership at migration time. Customers should expect segment re-evaluation to occur post-migration based on Pipedrive's activity and deal data.

NEON-dX campaigns and their associated offer content are structured records with templating metadata. We map campaign name, status, start and end dates, and channel assignments to a Pipedrive Deal with custom fields. Offer content and rich media asset references are stored as a Note attached to the Deal. Channel-specific offer formats that are incompatible with Pipedrive are flagged during discovery and documented for manual rebuild in Pipedrive's workflow or email tools.

NEON-dX customer journeys are multi-step orchestration flows with branching logic, wait conditions, and channel assignments. Pipedrive does not support equivalent journey orchestration. We document the journey structure in a written inventory delivered to the customer's admin, identifying which Pipedrive Workflow triggers can replicate each journey step. Automated multi-step journey execution does not migrate; it requires a separate implementation scope in Pipedrive or a dedicated journey tool.

NEON-dX custom objects with standard, formula, and lookup field types migrate to Pipedrive custom fields. Pipedrive supports custom fields of type text, integer, decimal, date, datetime, monetary, boolean, single-select, and multi-select. Lookup relationships between custom objects in NEON-dX are resolved by flattening the relationship into denormalized custom fields on the primary record, or by storing the related object ID in a text custom field. We enumerate the live NEON-dX custom object schema via API at migration start and generate the destination field definitions before import begins.

NEON-dX predictive scores are model-generated outputs from Flytxt's proprietary ML pipeline and cannot be meaningfully transferred to Pipedrive. Scores computed at export time become immediately stale. We do not export them as static values. Instead, we document the score configuration (feature inputs, model type, scoring frequency) so the customer's data science or analytics team can reproduce scoring logic in their preferred environment. Pipedrive's AI Sales Assistant provides deal-level predictions from the Professional plan ($49/user/mo) but uses a different model architecture. We flag this as a scoring gap in the handoff documentation.

NEON-dX channel configurations (SMS gateway credentials, email sender IPs, push notification keys, channel API tokens) are environment-scoped and cannot be exported as-is. We document all channel type, protocol, and configuration schema during the discovery phase and provide a re-authentication checklist for each channel. Pipedrive's Marketplace provides channel integrations (email sync, Twilio for SMS, push notification tools) that the customer's admin re-connects post-migration. Without valid credentials, automated journey steps in Pipedrive that rely on these channels will fail silently.

NEON-dX engagement records (calls, emails, meetings, tasks, notes) are stored with timestamps, disposition, and linked customer references. These migrate to Pipedrive Activity records using the appropriate type: Call, Email, Meeting, or Task. Activity dates and durations preserve from the source. Note bodies migrate as Pipedrive Notes linked to the Person or Organization record. Pipedrive's API exports calls and emails from active users only; we coordinate with the customer to ensure user accounts are active or use the appropriate API filters during extraction.

NEON-dX pre-built dashboards and custom reports reference platform-native metric definitions tied to campaign performance, behavioral scoring, and journey KPIs. These cannot migrate to Pipedrive because Pipedrive's Insights module uses deal pipeline, activity, and revenue metrics. We deliver a written inventory of every source report with its metric definitions, column structure, and filters. Pipedrive's Insights setup is handled by the customer's admin post-migration, or it can be scoped as a separate reporting implementation engagement.

NEON-dX consent management, data retention policies, and governance frameworks are platform-native constructs. We map GDPR and CCPA opt-out records to Pipedrive Person fields (typically a boolean consent flag and a consent date custom field) and flag any records that require suppression based on retention policy. Pipedrive's data management settings (data retention, user access controls) are configured by the customer's admin post-migration.