Migrate from e-shot to Freshsales

e-shot Contacts migrate to Freshsales Contact records. Where e-shot contacts represent a broad marketing audience that has not been qualified into a sales pipeline, we can provision them as Freshsales Leads first so that your sales team re-qualifies them through the standard Lead-to-Contact conversion workflow. Standard e-shot fields (email, first name, last name, phone, address) map directly to Freshsales Contact fields. Custom contact fields require pre-creation in Freshsales Admin Settings before import, with field types matched to e-shot data types. Merge-tag fallback values from e-shot become Freshsales default values on the corresponding custom fields.

e-shot custom contact fields defined in Settings > Contacts Field Manager must be pre-created in Freshsales Admin Settings before contact import begins. We extract every field definition including name, type, required flag, and any *_fieldname=fallback('text')_* fallback syntax. Each fallback becomes a Freshsales default value on the equivalent custom field. Field type mapping follows: e-shot text fields map to Freshsales Text, number fields to Number, date fields to Date, dropdown fields to Picklist. If a Freshsales custom field is not created first, the import CSV header will not match and records will fail validation.

e-shot Campaigns contain email content, subject lines, scheduling, and send history. Because Freshsales does not have a native Campaign object equivalent to HubSpot or Salesforce Marketing, campaign metadata (send date, send count, open rate, click rate) is loaded as a Freshsales Deal record with the campaign name as Deal name, send metrics stored in custom number fields, and a link to the primary contact as the WhatId. If the customer uses Freshmarketer alongside Freshsales, campaigns migrate as Freshmarketer Campaigns instead. HTML template body is preserved separately (see Templates mapping).

e-shot email templates store reusable HTML content blocks with embedded merge-tag markup. We export templates as raw HTML files preserving the *_fieldname_* syntax so that the customer can re-enable personalisation in Freshsales or a downstream email tool. Templates are not loaded into Freshsales as native objects because Freshsales does not have a standard template library for marketing emails. The HTML files are delivered alongside the migration with a field mapping reference indicating which custom fields each template references.

e-shot Automated Series are workflow-based email sequences with trigger conditions, delays, and action steps. Freshsales does not have an equivalent automation engine natively (Freshmarketer does, but it is a separate product). We extract every active Automated Series — including trigger type, conditions, step sequence, delay rules, and CRM action — into a written inventory document. The customer's admin rebuilds each series in Freshmarketer's Journey Builder or in Freshsales Workflows depending on the complexity. Series are not migratable as code because the trigger and action models differ fundamentally between platforms.

e-shot Landing Pages are tier-gated web pages with form elements and tracking. Freshsales does not have a native landing page builder (Freshmarketer does). We export published landing page URLs, form field definitions, and submission data linked to contacts so that the customer can recreate pages in Freshmarketer or a third-party landing page tool. Active landing page URLs are documented with a redirect plan to avoid broken links post-migration.

e-shot Forms and the Preference Centre store contact subscription choices, field inputs, and opt-in status. We export form definitions, field types, and per-contact preference data as a CSV. Opt-in and opt-out status migrates to Freshsales Contact fields (e.g., email_opt_out or a custom subscription field). Form builders and preference centre UI logic do not migrate; we document the configuration for rebuild in Freshmarketer or a CMS form plugin.

e-shot tags label contacts without a formal taxonomy and are stored as field values or list memberships. We extract tag assignments per contact and load them into Freshsales as a custom multi-select picklist field (e.g., contact_segmentation__c) or as Freshsales Tags on the Contact record. The customer chooses the target format during scoping. Tags used for segmentation logic in Automated Series are documented in the Series inventory for rebuild.

e-shot Saved Filters define dynamic contact segments using field conditions. We export filter definitions including field names, operators, and values. Freshsales does not have a Saved Filters equivalent in its native contact view — segments are managed through Freshsales Reports or through Freshmarketer's audience builder. We deliver a written segment inventory mapping each e-shot Saved Filter to a Freshsales Report or Freshmarketer audience definition.

e-shot Campaign Reports include opens, clicks, bounces, unsubscribes, and delivery health per campaign. We pull historical report snapshots from the analytics dashboard and load them as Contact Notes linked to each recipient (for high-value contacts) or as a campaign-level Deal record in Freshsales with metrics stored in custom fields. This preserves reporting context for customer-facing audits without requiring the customer to maintain access to the old e-shot account.