Migrate from Encharge to HubSpot

Encharge Person maps directly to HubSpot Contact. Standard properties (email, firstname, lastname, phone, jobtitle) transfer as HubSpot contact properties. HubSpot requires each Contact to have a primary Company — Encharge Persons without a linked Company receive a placeholder 'Unassigned' Company record.

Encharge Account (B2B account model) maps to HubSpot Company. Account name becomes Company name, domain maps to Website, industry maps to Industry pick-list value-by-value, and number of employees maps to NumberOfEmployees. Parent-child Account hierarchies in Encharge map to HubSpot's Parent Company field.

Encharge's Person-to-Account link becomes HubSpot's Contact-to-Company primary association. HubSpot supports a single primary Company per Contact plus additional associated Companies via the Associations API. We preserve the primary association and surface secondary associations for manual cleanup. This ensures all existing relationships are maintained and can be refined after the migration is complete.

Encharge Segments (membership-based, not behavioral-rule lists) map to HubSpot Static Lists. Dynamic Segments based on behavioral rules do not transfer — the underlying People records move, and your HubSpot admin recreates the dynamic logic as HubSpot Lists using the same filter conditions.

Encharge Tags are flat string labels on People. We map them to a HubSpot multi-checkbox custom property (Tags__c) so each Encharge tag becomes an option. If Tags exceed HubSpot's pick-list limit, we collapse them into a long-text custom property and preserve the full list as a reference export.

Encharge Deal custom objects (Growth and higher) map to HubSpot native Deals when the destination is Sales Hub. If you use Deals alongside Accounts in Encharge, we map them to HubSpot Deals linked to the corresponding HubSpot Company. Deal fields (amount, stage, close date) map to HubSpot Deal properties with value mapping for stage names.

Encharge Order and Invoice custom objects map to HubSpot custom objects. These require HubSpot Enterprise — we create the custom object schema in HubSpot, define the properties, and then import the records. Order-to-Contact and Invoice-to-Company links preserve as custom-object association properties.

Encharge behavioral Events (page views, feature actions, Stripe events) have no native HubSpot equivalent. We map email-related events to HubSpot Engagements (email logged as a Call or generic engagement), and preserve the full event payload as a JSON blob in a custom Timeline Events custom object so the behavioral history is queryable.

Encharge Flows do not migrate. They must be rebuilt in HubSpot's Workflows tool. We export the Flow definition (trigger, conditions, actions, step order) as a structured reference document your HubSpot admin uses to recreate each Flow. We do not automate the recreation because Flow semantics differ between platforms.

Encharge Users are resolved by email match against HubSpot Users. Encharge Person records carry an owner ID — we match that owner's email to the corresponding HubSpot user email and set the OwnerId on the resulting Contact. Unmatched owners are flagged for your team to either invite them to HubSpot or reassign records before the migration runs.

HubSpot's Createdate and LastModifiedDate are set by the import process, not the source system. We preserve the original Encharge created and updated timestamps as custom datetime properties (Original_Create_Date__c and Original_Update_Date__c) on every Contact and Company for historical reporting continuity. These properties allow you to query and report on data based on the original Encharge creation date even after the migration completes.

Standard communication fields (email address, phone number, mobile phone, street address, city, state, postal code, country) map directly to HubSpot's identically named contact properties. Address fields in Encharge may be split or combined — we normalize to HubSpot's address compound property format during the import.