Migrate from NEON-dX to Salesforce Sales Cloud

NEON-dX stores each customer as a unified profile combining demographic, behavioral, and digital footprint data. We split this into Salesforce Account (the organizational or household entity) and Contact (the individual person). Profile fields that represent company-level attributes (industry, annual revenue tier, customer tier) map to Account fields; individual-level attributes (first name, last name, email, phone) map to Contact fields. The NEON-dX profile ID is preserved as an external ID field on Contact for cross-reference during reconciliation.

NEON-dX behavioral segments are defined by rule criteria that evaluate against customer event streams. We migrate the segment definition rules as Salesforce Campaign Audience criteria or as custom multi-select picklist fields on Contact that encode the segment rule logic. Actual segment membership re-evaluates on the Salesforce side based on that platform's event data and activity history. Customers should expect segment counts to diverge after migration as the destination platform re-applies the segment rules against its own data.

NEON-dX Campaign records map directly to Salesforce Campaign. Campaign name, description, start and end dates, status, and budgeted cost migrate. Campaign response tracking (member status, reach, impressions where tracked) migrates to CampaignMember. Offer content embedded in a campaign migrates as Salesforce Campaign content assets.

NEON-dX Offer catalog entries (discounts, promotions, bundles, recommendations) map to Salesforce ContentAsset records if they represent content artifacts, or to a custom Offer object if the customer's business logic treats offers as structured discount records. We enumerate the offer data model during discovery to determine the appropriate mapping strategy per offer type.

NEON-dX Customer Journeys are multi-step orchestration flows with branching logic, wait conditions, and channel assignments. We do not migrate journey flows as executable code because Salesforce Flow and Marketing Cloud Journey Builder are different automation models. Instead, we document the full journey structure including steps, conditions, delays, channel assignments, and entry/exit criteria as a written handoff for the customer's admin to rebuild. Channel assignments require re-authentication on the destination.

Predictive scores generated by NEON-dX's proprietary ML pipeline (churn propensity, LTV tier, next-best-offer propensity, customer value index) are not transferable because they depend on NEON-dX's live training data, feature engineering environment, and model versioning. We preserve the score values at the time of migration as custom fields on Contact for historical reference, but these values become stale immediately. Salesforce Einstein AI provides equivalent predictive scoring capabilities from Enterprise tier that the customer's team can configure and train on Salesforce data.

NEON-dX supports custom object types with standard fields, formula fields, and lookup relationships exposed via REST API. We enumerate the live custom object schema via API at the start of each engagement, build a dependency graph for formula field relationships, then pre-create the destination custom objects in Salesforce with matching field types and lookup relationships before any data import. Formula fields that reference other custom objects are sequenced last to satisfy lookup dependencies.

NEON-dX channel configurations (SMS gateway credentials, email sender IPs, push notification keys, digital channel API tokens) are environment-scoped and cannot be exported. We document the channel type, connector configuration schema, and connection parameters during discovery and deliver a re-authentication checklist for each channel. Without valid credentials on the Salesforce or Marketing Cloud side, journey automation will fail silently after cutover.

NEON-dX engagement events (opens, clicks, sends, bounces, delivery confirmations) that are stored as activity records migrate to Salesforce Task and Event objects with custom engagement metadata fields. The WhoId on each record points to the migrated Contact. High-volume engagement history (over 500,000 records) uses Salesforce Bulk API 2.0 with batch chunking and parent-record lookup resolution.

NEON-dX pre-built dashboards and custom reports reference platform-native metric definitions and real-time data connectors. We migrate the report structure and column configurations as Salesforce Report metadata. Destination metric data populates after migration completes. Dashboards require rebuilding in Salesforce Lightning Dashboard Builder because visualization layout and component bindings are not transferable across platforms.

NEON-dX consent management, data retention policies, and governance frameworks are platform-native. We map these to Salesforce equivalent settings: GDPR and CCPA opt-out flags migrate to HasOptedOutOfEmail and custom consent date fields; data retention rules are documented for the customer's admin to configure in Salesforce Setup. Privacy audit trails migrate as custom Activity records.

NEON-dX pre-built journey and campaign templates in the best practices library are platform-native and not portable. We inventory which standard templates the customer has customized and document the customization scope as a rebuild guide for Salesforce. Salesforce's Campaign Templates and Lightning Bolt solutions provide an equivalent starting point.