Migrate your e-shot data

Contacts are the primary record type in e-shot. Every contact has system fields and custom contact fields defined in Settings > Contacts field manager. We export all standard and custom field values, including empty fields, and replicate them on the destination as matching properties.

e-shot's contact field schema is fully customisable. The field name, type, and merge-tag syntax (*_fieldname_*) must be mapped to the destination's equivalent property naming convention. We extract the field manager schema first and build the field map before importing contact records.

Campaigns hold the email content, template body, subject line, sender details, and scheduling. We export campaign records and associated content blocks. HTML template assets are preserved as-is; dynamic content blocks are flagged for manual review.

Automated Series are workflow-based email sequences triggered by contact behaviour or date conditions. Tier-gated limits (basic: 3, pro: 25, omni: 100) cap how many can run concurrently. We export series definitions and trigger logic but note that complex multi-branch workflows may require reconfiguration in the destination platform.

Landing pages are tier-gated (basic: 0, pro: 25, omni: 100). Additional pages can be created but not set live within limit. We export published landing page content and form elements; form field mappings must be recreated at the destination since e-shot stores forms and pages as separate objects.

Forms and the preference centre store contact choices, subscription preferences, and field inputs. We export form definitions, field types, and associated preference data linked to each contact record. Custom form fields are mapped like contact fields.

Contact preferences track opt-in status and subscription interests. Tier limits apply to active preferences (basic: 25, pro: 50, omni: unlimited). We export the preference centre structure and per-contact preference values, flagging records where the destination has fewer preference categories than e-shot.

Popups are campaign-triggered web overlays tied to contact identification. Tier limits cap live popups (basic: 0, pro: 25, omni: 100). We export popup configurations and trigger rules; display logic must be rebuilt in the destination's equivalent web personalisation tool.

Tags label contacts and segments without a formal taxonomy. e-shot does not expose a separate tag management API object — tags are stored as field values or list memberships. We extract tag assignments per contact and map them to the destination's equivalent labelling mechanism (properties, segments, or tags).

Saved filters define dynamic contact segments using field conditions. Tier limits on active filters apply (basic: 10, pro: 25, omni: unlimited). We export filter definitions as segment rules and replicate the condition logic in the destination CRM or marketing platform.

Analytics include opens, clicks, bounces, unsubscribes, and delivery health for each campaign. Data is exportable from the analytics dashboard. We pull historical report snapshots so campaign performance is preserved alongside contact records.

Email templates store reusable HTML content blocks and design elements. We export templates as HTML with embedded styles. Merge tags are preserved as source values so they can be re-enabled in the destination editor.