Migrate from eMarketeer to Freshsales

eMarketeer Contacts map to Freshsales Lead by default. Contacts whose lifecycle stage indicates a qualified or customer status (e.g., sales qualified lead, customer, evangelist) map to Freshsales Contact attached to an Account. We determine the split rule during scoping using eMarketeer's lifecycle stage values, preserve the original stage in a custom field em_original_lifecycle__c on both Lead and Contact, and apply the rule as a computed field during the import transform.

eMarketeer campaigns that represent campaign sends (email, SMS) have no direct Freshsales equivalent; we map their contact response data (opens, clicks, conversions) as Freshsales Deal records with a custom campaign_source field pointing to the original eMarketeer campaign name. Campaigns that represent sales pipeline stages (if eMarketeer is used for deal tracking) map directly to Freshsales Deal (Opportunity) with pipeline stages configured as Deal stages in the destination account.

eMarketeer segments are rule-based and re-evaluate continuously. Freshsales evaluates contact filters against stored field values rather than live criteria, so we snapshot current segment membership as a static contact list at migration time and create Freshsales contact filters that approximate the original criteria using the closest available field types. The snapshot preserves the exact membership at cutover; ongoing list maintenance requires manual Freshsales segmentation or a recurring export workflow.

eMarketeer company records (if used) map to Freshsales Account. Company domain becomes the Account Website field and is used as the dedupe key. Account is created before any Contact import so that the Account lookup relationship is satisfied at Contact insert time.

eMarketeer event records with registration data, attendee counts, and attendance status map to Freshsales Event objects. We create custom fields on the Event record (or on a linked custom module) to hold eMarketeer-specific registration metadata such as attendee_limit, registration_count, and registration_source if those fields exist in the export.

eMarketeer flows with trigger-action sequences do not migrate as code. Freshsales Workflows use a different trigger model (record-triggered, time-based, or form-based) that does not accept eMarketeer's lifecycle-change or CRM-event triggers directly. We audit every active eMarketeer flow during discovery, document its trigger, conditions, steps, and delays, and deliver a written inventory with recommended Freshsales Workflow equivalents. The customer's admin rebuilds flows in Freshsales Workflows post-migration.

eMarketeer custom contact and campaign properties (industry vertical, product lines, lifecycle custom fields) map to Freshsales custom fields created during schema setup. Property types (text, number, date, dropdown) map to equivalent Freshsales field types. Dropdown enumerations require explicit value mapping because eMarketeer enumeration labels may differ from Freshsales picklist values. We derive the full schema from the export during discovery since eMarketeer has no documented field registry.

eMarketeer open, click, and unsubscribe events tracked per contact per campaign aggregate into a Freshsales contact activity log. We create custom fields on the Contact record (last_email_open_date, last_click_date, email_opt_out_date) and store a summary of total engagement in a notes field for each contact. Real-time engagement tracking resumes only when Freshsales receives new emails through its built-in email sync or Freshmarketer integration.