Migrate from NEON-dX to HubSpot

NEON-dX contacts map directly to HubSpot contacts. All standard properties (name, email, phone, address) migrate as HubSpot standard fields. Custom properties and behavioral data migrate as HubSpot custom properties. Contacts without an email address are flagged for manual review since HubSpot contacts require an email for the contact record to function fully.

NEON-dX accounts map to HubSpot companies. Account hierarchies in NEON-dX (parent-child with unlimited depth) are flattened — the top-level account becomes the primary company in HubSpot and the full hierarchy path is stored in a custom property (Account_Hierarchy_Path__c) so the relationship can be reconstructed in reporting.

NEON-dX campaigns carry engagement metrics, channel metadata, and targeting criteria. These map to a HubSpot static list (campaign membership) plus a set of custom properties on contacts that store campaign-level attributes (e.g., Campaign_Channel__c, Campaign_Start_Date__c) since HubSpot does not have a native campaign object outside of its marketing hub.

NEON-dX journey definitions — multi-step conditional paths with AI-driven decision branches, wait steps, and channel actions — have no direct HubSpot equivalent. The journey structure and step logic are exported as a documentation reference. HubSpot workflows (if/then sequential builders) must be rebuilt by your marketing ops team using the exported journey map as a rebuild guide.

NEON-dX behavioral and demographic segments map to HubSpot lists. Static segments migrate as HubSpot static lists by direct record membership. Dynamic segments require recreating the filtering criteria as HubSpot's list filter builder — behavioral segments that reference NEON-dX-specific properties are stored as contact properties first, then used as filter criteria in HubSpot dynamic lists.

NEON-dX AI-driven engagement scores do not have a native HubSpot equivalent. The numeric score value is preserved as a custom property (Engagement_Score__c) on HubSpot contacts. HubSpot's own contact scoring (if enabled in your subscription) can replace this with rules-based scoring post-migration, but the historical NEON-dX score is stored separately for continuity.

NEON-dX custom objects (with custom fields, formula fields, and associations) map 1:1 to HubSpot custom objects. N:N associations in NEON-dX require HubSpot junction objects or association labels. Formula fields are extracted as static values since HubSpot does not support formula fields natively — we preserve the original formula expression in a text property for reference during post-migration recalculation.

NEON-dX engagement records (calls, emails, meetings, notes with metadata) map to HubSpot engagement logs on the contact timeline. Original timestamps and owners are preserved. Meeting metadata (duration, location, attendees) is stored in engagement properties or notes. Real-time engagement tracking from NEON-dX does not transfer since HubSpot handles live engagement differently.

NEON-dX opportunity data (deal name, amount, stage, close date, owner, associated contacts and account) maps directly to HubSpot deals. Stage names are mapped value-by-value to HubSpot deal pipeline stages. Campaign attribution from NEON-dX opportunities is preserved as custom properties (e.g., Opportunity_Source_Campaign__c) for reporting continuity.

NEON-dX users and team owners are matched to HubSpot owners by email address. Unmatched owners are flagged before migration so the team can create corresponding HubSpot user accounts or reassign records to a fallback owner. No record lands in HubSpot without a resolved owner to maintain data integrity in HubSpot's ownership model.

NEON-dX multi-touch attribution models and touchpoint history have no native HubSpot equivalent. Attribution metadata (campaign IDs, channel, touchpoint type, attribution credit) migrates as custom properties on the contact record. The attribution reporting logic itself must be rebuilt using HubSpot's attribution reporting tools post-migration.

NEON-dX file attachments linked to contacts, accounts, or custom objects are downloaded and re-uploaded to HubSpot Files. Files are reattached to the corresponding HubSpot record. HubSpot's 25MB per-file limit applies; files exceeding this are flagged for manual review or chunked upload by your team.