Migrate from e-shot to Salesforce Sales Cloud

e-shot contacts are flat records with no Account affiliation. We create Salesforce Account records from the contact's company domain (extracted from email address) during import, then attach each Contact to the matching Account via AccountId. Contacts without a resolvable company are attached to a Default Account or held for manual Account assignment. The e-shot contact ID is stored in a custom field legacy_e-shot_id__c as an external ID for future sync.

e-shot's custom contact fields (defined in Settings > Contacts Field Manager) map to Salesforce custom fields on the Contact object. Field types are type-mapped: text to Text(255), number to Number, date to Date, checkbox to Checkbox, dropdown to Picklist. Merge-tag fallback values (*_fieldname=fallback('text')_*) are extracted and set as Salesforce Default Value on each custom field so contacts without a value display the fallback rather than a blank or raw merge tag.

e-shot campaigns (email content, subject line, sender details, schedule) map to Salesforce Campaign records with the Campaign Type set to Email. The HTML email body migrates as a Salesforce EmailTemplate record linked to the Campaign. Campaign status (Draft, Live, Ended) maps to Salesforce Campaign Status values. Historical send stats (opens, clicks, bounces, unsubscribes) migrate as CampaignMember records with corresponding Activity History.

Automated Series are workflow-based email sequences with trigger conditions and delay steps. e-shot tiers gate the number of live series (3 on basic, 25 on pro, 100 on omni). We export the series configuration (trigger, conditions, steps, delays, email references) as a written inventory document with a recommended Salesforce Flow equivalent for each series. The customer's admin rebuilds them in Flow Builder; we do not convert the automation logic as code.

Landing pages are tier-gated on e-shot (0 on basic, 25 on pro, 100 on omni). Additional pages can be created but not set live within the plan limit. We export the published page content and form field definitions as a written handoff document. Salesforce Experience Cloud Sites replace landing pages with Page Builder or Digital Experiences; we do not migrate the page as code.

e-shot forms store field inputs and subscription preferences linked to each contact record. We export form definitions (field types, required flags, layout) and map them to Salesforce Web-to-Lead form fields or Experience Cloud form builders. Form submissions migrate as Salesforce Leads or Contacts with the submitted field values mapped to the corresponding custom fields.

Contact preferences track opt-in status and subscription interests. Tier limits on active preferences apply (25 basic, 50 pro, unlimited omni). We map subscription preferences to a combination of Salesforce's standard HasOptedOutOfEmail field and custom multi-select picklist fields representing each e-shot preference topic. The preference centre structure migrates as a configuration map for rebuilding in Salesforce Preference Centre or Marketing Cloud Account Engagement.

Website Popups are campaign-triggered web overlays tied to contact identification. Tier limits cap live popups (0 basic, 25 pro, 100 omni). We export popup configurations, trigger rules, and display logic as a written inventory for rebuilding in Salesforce Flow with Screen components or Experience Cloud. The popup HTML and CSS do not migrate directly.

e-shot tags label contacts and segments without a formal taxonomy; they are stored as field values or list memberships rather than a separate tag object. We extract tag assignments and map them to Salesforce multi-select picklist fields on Contact, or to Campaign membership records if the tag functions as a static audience segment. The customer chooses the tag strategy during scoping.

Saved filters define dynamic contact segments using field conditions (basic: 10, pro: 25, omni: unlimited). We export filter definitions as segment rules and replicate them as Salesforce Reports with filter criteria, or as Campaign static Lists for marketing audience segmentation. The dynamic refresh behaviour of e-shot filters maps to Salesforce Report filters or Campaign smart lists.

e-shot campaign analytics (opens, clicks, bounces, unsubscribes, delivery health) export from the analytics dashboard. We pull historical report snapshots and import them as Salesforce CampaignMember records with corresponding activity dates. Open and click rates become custom numeric fields on Campaign; bounce and unsubscribe rates map to Salesforce tracking fields on CampaignMember.

Email templates store reusable HTML content blocks with embedded styles and merge tags. We export templates as HTML with embedded styles. Merge tags are preserved as source values (*_fieldname_*) so they can be re-enabled in Salesforce's email template syntax. Dynamic content blocks require manual reassembly in Salesforce's Lightning Email Builder or Content Builder.

e-shot has unlimited users across all tiers, and contacts may reference an owner or campaign manager. We resolve owners by email match against the Salesforce destination org's User table. Any e-shot owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes.