Migrate from e-shot to HighLevel

e-shot Contacts map directly to GoHighLevel Contacts when the contact has a known email address and company association. Contacts without a clear company association but with lead-capture intent (form fills, popup responses) can optionally map to GoHighLevel Leads for pipeline routing. We preserve all standard e-shot fields (email, first name, last name, phone, address) plus every custom contact field, including any with merge-tag fallback values which we replicate as GoHighLevel custom fields with default values set to the fallback text.

e-shot's Contact Field Manager stores field definitions with type and merge-tag syntax. We extract every custom field definition including *_fieldname=fallback('text')_* fallback values and recreate them as GoHighLevel Custom Fields. Field types map as follows: text to Short Text, long text to Long Text, date to Date, number to Number, dropdown to Dropdown, checkbox to Multi-Select Checkbox. Fallback values are set as default values on the GoHighLevel custom field so contacts without a value display the fallback rather than a blank or raw merge tag.

e-shot Campaigns hold email content, subject line, sender details, and scheduling. We export campaign records and associated HTML template bodies as-is. The HTML content migrates as GoHighLevel Email Templates with the original e-shot template name preserved. Subject lines and sender details are stored in the GoHighLevel template settings. Automated sends require workflow rebuild; we document every campaign with an active Automated Series attached so the customer knows which templates need automation re-connection.

e-shot Automated Series are email sequences triggered by contact behaviour or date conditions. GoHighLevel has no direct equivalent of Automated Series as a discrete object; each series becomes a GoHighLevel Workflow with the same trigger conditions and email actions. We export the series definition (trigger, conditions, step sequence, delays, email references) and deliver it as a written workflow map for the customer's admin to rebuild. We do not execute the rebuild as part of the migration scope. Series that reference e-shot-specific merge tags in their body text require template update before the workflow runs.

e-shot Preference Centre tracks subscription status and interest categories per contact. We export the preference structure (preference name, type, default state) and per-contact preference values. These map to GoHighLevel Contact Tags (for interest categories) and a custom field eshot_subscription_status__c (for overall opt-in state). We preserve the original e-shot preference names in the tag and field descriptions for audit traceability.

e-shot Forms collect contact data and subscription choices. GoHighLevel has a native Form builder with equivalent field types. We export form definitions including field names, field types, required settings, and the form's linked preference centre. Form field mapping is 1:1 for standard field types; custom field types require GoHighLevel Custom Field pre-creation before form field mapping. Form submissions (historical responses) migrate as Contact records with the form tag applied.

e-shot Saved Filters define dynamic contact segments using field conditions. Tier limits apply to active filters (basic: 10, pro: 25, omni: unlimited). We export each filter's condition set as a written rule definition. In GoHighLevel, equivalent segmentation uses Tags (applied manually or via Workflow) or Smart Lists (with field-condition rules). We document which contacts match each e-shot filter so the customer's admin can apply the equivalent segmentation in GoHighLevel.

e-shot Campaign Reports include opens, clicks, bounces, unsubscribes, and delivery health per campaign. We export historical report snapshots as CSV so the customer retains campaign performance data. GoHighLevel Campaign analytics serve as the ongoing reporting destination post-migration. We do not backfill GoHighLevel analytics with e-shot historical data; the historical report CSV is delivered alongside the migration for the customer's records.

e-shot Email Templates store reusable HTML content blocks with embedded styles. We export templates as HTML files with merge tags preserved as source values. In GoHighLevel, templates are recreated as Email Templates using the imported HTML. Any e-shot merge tags not yet mapped to GoHighLevel custom fields are flagged so the admin can update the template HTML before the next send.

e-shot does not expose a separate tag management API object; tags are stored as field values or list memberships. We extract every distinct tag string and map them to GoHighLevel Tags on the Contact record. Tags used for segment classification are preserved as written tag names so the customer's segmentation logic remains intact. Duplicate tag names from different sources are deduplicated during extraction.