Migrate from Encharge to Salesforce Sales Cloud

Encharge People records map directly to Salesforce Contact. Standard fields (email, firstname, lastname, phone, address) map to their Salesforce counterparts. Encharge custom person fields migrate as Salesforce custom Contact fields (__c suffix). The email field on Contact is the dedupe key during import. We resolve the related Account via Encharge's company link before insert to satisfy the AccountId Lookup.

Encharge Accounts map to Salesforce Account. The domain field from Encharge populates Account.Website, and Account.Name pulls from the company name. Accounts insert first so that Contact import resolves AccountId lookups at migration time. Company custom fields migrate as Account custom fields.

Encharge tags are flat string labels per Person. We export all tag assignments and either recreate them as Salesforce Topics with TopicAssignment records (better for content and interest taxonomy) or as a custom multi-select picklist field on Contact (better for segmentation logic the admin controls). The customer chooses during scoping. Tags used for lead status classification map to Contact.Status or a custom picklist field.

Encharge Custom Objects (Deals, Orders, Invoices, or any domain entity) migrate to Salesforce custom objects of equivalent API name. We pre-create the destination schema including all custom fields, lookup relationships to standard objects, and validation rules in a Salesforce Sandbox before production migration. Custom object records insert after parent Accounts and Contacts are confirmed to satisfy lookup constraints.

Encharge Flows store automation logic as JSON referencing triggers, conditions, wait-step durations, and downstream actions. There is no public export endpoint. We document the full Flow tree during scoping as a written specification including trigger event, every conditional branch, delay timers, and action sequence. The customer uses this specification to rebuild Flows in Salesforce Flow Builder. Flows do not migrate as code.

Encharge Segments are dynamic filter-based groups of People. We export the segment definition including filter rules, operator logic, and include/exclude criteria as a written segmentation specification. In Salesforce, dynamic segments are approximated by Campaign with member status or by List Views, but the live refresh behavior does not migrate. Static membership migrates as CampaignMember records.

Encharge Activities recording email opens, page views, and custom behavioral events migrate to Salesforce Task records. The event name maps to Task.Subject, the timestamp maps to Task.ActivityDate, and the behavioral metadata (page URL, event property) maps to custom Task fields. Salesforce does not have a native behavioral tracking canvas; this mapping preserves audit history but requires post-migration configuration for behavioral reporting dashboards.

Encharge email engagements migrate to Salesforce EmailMessage records (the content body) and a paired Task record (the activity timeline entry). The WhoId on Task points to the related Contact; WhatId points to the related Account or Opportunity. Email status (sent, bounced, opened) migrates as a custom field on EmailMessage because Salesforce's standard EmailStatus field is not directly writable via Bulk API.

Encharge call engagements map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and any recording URL migrate as custom Task fields. ActivityDate preserves the original timestamp so the call appears in the correct position on the Contact's activity timeline.

Encharge meeting engagements map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendee relationships migrate as EventRelation records linking the Contact and any related User attendees. Subject and description fields carry the meeting title and notes.

Encharge notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, or custom object record. Note body migrates as plain text with image attachments preserved as ContentDocument records where Encharge stores them inline.

Encharge Email Templates are stored as HTML with subject line, sender name, and inline styles. We export each template as an HTML file and import it into Salesforce as a Document (Classic) or ContentVersion (Lightning) record. Dynamic personalization tokens (such as Encharge's first_name and company_name merge fields) require manual rebuild in Salesforce's merge field syntax because the token schemas differ between platforms.

Encharge Campaigns (groupings of email sends and automation steps) map to Salesforce Campaign with Campaign.Name and Campaign.Status preserved. The campaign-flow association does not export; we document which Encharge Flows enrolled which Campaigns so the customer can plan Salesforce Flow equivalents and Campaign member assignments post-migration.

Encharge Users (team members assigned as Flow owners and sending identities) are reconciled against Salesforce Users by email match. Any Encharge User without a matching Salesforce User enters a reconciliation queue for the customer's admin to provision before record import begins. Migration cannot proceed past Engagement import because OwnerId references on Task and Event require a valid Salesforce User.