Migrate from Encharge to Freshsales

Encharge People records map 1:1 to Freshsales Contacts. Standard fields (email, first name, last name, phone, address) transfer directly. Custom person fields migrate to Freshsales custom contact fields, which must be pre-created in Admin Settings before migration. Email serves as the unique identifier for deduplication. Encharge's behavioral properties (lifecycle stage, lead score) transfer as custom fields if the customer has configured them.

Encharge company Accounts map directly to Freshsales Accounts. Company name, domain, address, phone, and industry fields align. Custom company fields migrate to Freshsales custom account fields. Accounts must be imported before Contacts so that the Account-Contact relationship is satisfied at insert time. If a Contact has no associated Account in Encharge, we create a placeholder Account using the contact's domain or email domain.

Encharge flat string tags attached to People export as a tag list. We reapply tags to Freshsales Contacts as native tag assignments. If the customer uses a large tag vocabulary (over 200 unique tags), we recommend consolidating during migration to avoid tag sprawl in Freshsales. Tags used for segmentation logic are preserved so the customer can reference them when rebuilding Segments in Freshsales.

Encharge Custom Objects (commonly used for Deals, Orders, Invoices, Subscriptions) require field-level mapping. We analyze the custom object schema during discovery, then pre-create the corresponding custom fields on the appropriate Freshsales object (Deal for sales pipeline data, Account for company-level financial data, Contact for person-level subscription data). Lookup relationships between custom objects in Encharge map to Freshsales lookup fields or multi-select references where the schema supports it. Edition note: custom fields are available from Freshsales Growth plan ($9/user/month) with no setup fee.

Encharge behavioral activities (email opens, page views, custom events, Stripe payment events) map to Freshsales Task records with event name and timestamp preserved. We classify activities by type: timed events become Tasks with the activity description in the subject and event metadata in the custom fields; meeting-style events (if tracked) become Appointments. Note that Freshsales' activity timeline is optimized for sales interactions (calls, emails, meetings), not marketing behavioral events, so we flag during scoping whether the full behavioral history is required in Freshsales or can be exported as a CSV reference for reporting purposes.

Encharge HTML email templates with subject lines, sender names, and metadata export as HTML files with inline styles and image references preserved. We import templates into Freshsales' Email Template library, preserving subject lines and sender configurations. Templates that reference Encharge-specific merge tags (such as encharge person fields) require manual tag update to Freshsales merge field syntax before activation.

Encharge Campaigns group emails and automation steps but do not export campaign-flow associations. We migrate campaign names, descriptions, status, and date ranges as Freshsales Campaign records. Campaign enrollment history (which People were enrolled at what point) migrates as Campaign Member records if Freshsales Campaign is used, or as a Note attachment on each Contact if the customer prefers not to use the Campaigns module. We document the campaign-flow association during scoping so the customer's admin can reconnect campaign logic in Freshsales Workflows.

Encharge Segments are dynamic filter-based groups of People. We export the segment definition (filter rules, operator logic, and group conditions) as a written specification. Segments cannot be imported directly into Freshsales because Freshsales uses a different segmentation model (filter-based Views and Lists rather than dynamic audience groups). We deliver a segment inventory document during migration with Freshsales View configuration steps for each Encharge Segment, and the customer's admin recreates them post-migration. Segment definitions are preserved so the rebuild is guided, not from scratch.

Encharge Places store structured location data associated with People or Accounts. We map Places to Freshsales address fields on Contact and Account (street, city, state, postal code, country). Structured location data preserves during migration; geocoordinates stored in Encharge migrate to Freshsales custom number fields if the customer has a use case for them.