Migrate from e-shot to Mailchimp

e-shot Contacts map to Mailchimp Audience members. We extract every standard system field (email, first name, last name, opt-in date, unsubscribe date) and custom contact field, then map each to a Mailchimp merge field of the matching type. The audience is created in Mailchimp before contact import so that merge field definitions are in place before any subscriber records arrive. Bounced and unsubscribed contacts from e-shot are imported as suppressed members in Mailchimp rather than active subscribers, preserving suppression list hygiene.

e-shot's custom contact field definitions (name, type, merge-tag syntax *_fieldname_*) are extracted from Settings > Contacts field manager and replicated as Mailchimp merge fields in the Audience settings. Every fallback value defined with e-shot's fallback('text') syntax is set as the default value in the Mailchimp merge field. This prevents raw merge tags appearing in email content sent to contacts who lack that field value. Field type mapping converts e-shot text, date, number, and boolean types to Mailchimp TEXT, DATE, NUMBER, and PHONE merge field types respectively.

e-shot campaign records (subject line, sender details, HTML template body, scheduling) migrate to Mailchimp campaigns. HTML template content is preserved as-is and imported into Mailchimp's template or campaign builder. We identify all e-shot merge tags in the template body and ensure corresponding merge fields exist in the destination Audience before the campaign content is set. Dynamic content blocks are noted as requiring manual reconfiguration in Mailchimp's Dynamic Content feature if the destination is Standard or above.

e-shot Automated Series (tier-gated, up to 100 on omni) are exported as a written inventory rather than migrated as executable automation. We document each Series name, trigger condition, step sequence, delay durations, and conditional branching logic. The customer's admin rebuilds these in Mailchimp Customer Journeys, which uses a different trigger-and-action model. This inventory is delivered as part of the migration handoff package and is not part of the data migration scope.

e-shot form definitions (field types, field labels, subscription preference checkboxes) migrate as a documented form schema. Mailchimp signup forms use a different field definition model with embedded GDPR consent handling and double opt-in configuration. We extract form field types and labels from e-shot and map them to Mailchimp field equivalents, noting which forms had GDPR-compliant consent language that must be re-applied in the Mailchimp form builder. Actual form deployment and URL configuration are handled by the customer's admin post-migration.

e-shot contact preferences (subscription interests, topic opt-ins) map to Mailchimp Groups within the Audience. Active preference count is preserved; e-shot's tier limit (basic: 25 active, pro: 50, omni: unlimited) maps to Mailchimp Group categories and interest groups without a hard ceiling. Preference centre structure is documented so the customer can replicate the preference centre URL and topic groupings in Mailchimp's Groups section. Subscribe and unsubscribe status migrates as the member's Mailchimp status field.

e-shot tags are stored as field values or list membership labels without a separate tag management API object. We extract every distinct tag assigned to any contact and apply those tags as Mailchimp Tags during subscriber import. Tags used for segmentation in e-shot saved filters become Mailchimp Tags that the customer can use to build equivalent segments post-migration. Tags used purely for internal labelling (not segmentation) migrate as informational tags only.

e-shot campaign reports (opens, clicks, bounces, unsubscribes, delivery health) are exported as CSV snapshots and imported into Mailchimp as historical campaign performance data if the Mailchimp plan supports historical data import. Mailchimp's 90-day window for API-sourced historical data means we load the CSV-exported report data separately and note the reporting gap for the customer's analytics team. Campaign-level engagement metrics (open rate, click rate, bounce rate) are preserved in the CSV for reference even when the direct import into Mailchimp's reporting UI is not possible.

e-shot landing pages are tier-gated (basic: 0 live, pro: 25, omni: 100) and store form elements and published content. Mailchimp does not offer native landing pages in its core email plans; the Mailchimp Website Builder is a separate product. We export landing page content as HTML snapshots and deliver a written inventory of every live landing page URL, form field schema, and lead-capture destination for the customer to rebuild in Mailchimp's website builder or a third-party tool. This is not a data migration scope item.