Migrate from NEON-dX to Microsoft Dynamics 365 Sales

NEON-dX 360-degree profiles combine demographic, behavioral, and digital footprint data. We split these into Dynamics 365 Contact (individual-level fields) and Account (household or company-level fields). The NEON-dX profile identifier is preserved as a custom field neon_dx_profile_id__c on Contact for audit trail and future cross-reference. Any behavioral signal fields (recency, frequency, channel preference) migrate as custom fields on Contact because Dynamics standard fields are sales-process-oriented rather than behavioral.

NEON-dX segments defined by rule criteria evaluate against live event streams and are not stored as static membership lists. We migrate the segment definition rules (rule logic, criteria operators, lookback windows) as a written specification document for the customer's admin to rebuild in Dynamics 365 Customer Insights. Segment membership re-evaluates after migration based on the event data in Dataverse. Customers should not expect identical segment counts immediately post-cutover.

NEON-dX campaigns and associated offer content migrate as Dynamics 365 Campaign records with campaign type, status, budgeted cost, and channel assignments. Rich media assets (images, copy blocks) require separate file transfer and are documented in a media asset manifest. Any channel-specific offer formats that are NEON-dX-native are flagged and mapped to Dynamics email templates or marketing asset equivalents.

NEON-dX multi-step journey flows with branching logic, wait conditions, and channel assignments are documented as a written journey map for the customer's admin to rebuild in Dynamics 365 Customer Insights Journeys or Sales Playbooks. Journey structure (steps, branches, delays) transfers as a specification document; channel credentials must be re-registered in the destination environment before journeys can activate. Automated trigger logic does not migrate as executable code.

NEON-dX custom objects with standard, formula, and lookup field types migrate to Dynamics 365 custom entities on Dataverse. We discover the source custom object schema via NEON-dX API enumeration at migration start, build the dependency graph for any formula fields referencing other custom objects, and generate field-level mappings to Dataverse column types. Custom entity API names follow the __c suffix convention. This mapping is available from Microsoft Dynamics 365 Sales Professional tier ($65/user/mo) without additional setup fees.

SMS gateway credentials, email sender IPs, push notification keys, and channel API tokens stored with environment-specific scoping in NEON-dX cannot be exported as-is. We document all channel configurations during discovery and provide a re-authentication checklist for each channel type (email, SMS, push, digital). Without valid credentials, journey automation in Dynamics will fail silently. Channel type and configuration schema transfer as a written specification.

NEON-dX pre-built dashboards and custom reports reference platform-native metric definitions tied to NEON-dX's event taxonomy. We migrate the report structure and column configurations as written specifications. Destination metric data populates after migration completes using Dataverse event data. Customers typically rebuild analytics in Power BI connected to Dataverse rather than using Dynamics-native reports for cross-entity analysis.

NEON-dX consent management, data retention policies, and GDPR/CCPA opt-out records are platform-native constructs. We map consent flags to Dynamics 365 Contact fields (HasOptedOutOfEmail, DoNotTrack) and document any opt-out records that require manual re-entry in the destination. Data retention policies are written as configuration specifications for the customer's admin to implement in Dynamics Security and Compliance settings.