Migrate from e-shot to Nutshell

e-shot Contacts map directly to Nutshell People. Every standard field (name, email, phone, address) maps to the equivalent Nutshell Person field. Custom contact fields from e-shot (defined in Settings > Contacts field manager) are created as custom Person fields in Nutshell before import, preserving the original field label, type (text, number, date, picklist), and any required-setting. e-shot merge-tag field names (*_fieldname_*) are converted to Nutshell custom field API names. Merge-tag fallback values are extracted from the field manager and applied as Nutshell default-value rules on each custom field so contacts without data display cleanly.

e-shot's fully customisable contact field schema requires pre-creation in Nutshell before any contacts are loaded. We extract every field name, data type, and fallback definition from the contact field manager. Text fields become Nutshell text custom fields; number fields become number custom fields; date fields become date custom fields; picklist fields become Nutshell drop-down custom fields with the same option values. The migration cannot proceed until the destination schema matches the source field definitions, because each contact record carries field values that must land in correctly typed destination fields.

e-shot tags label contacts and segments but are stored as field values or list memberships rather than a distinct tag API object. We extract every distinct tag value and its contact assignments, then create the corresponding tags in Nutshell and link them to the migrated Person records. Tag spelling and casing are preserved exactly as they appear in e-shot.

e-shot campaigns contain email subject, body HTML, template content, and send history. We export the HTML body and subject line from each campaign. The HTML becomes a Nutshell email template with the same body content and subject line preserved. Nutshell's template editor accepts HTML import, so design elements, embedded styles, and images transfer as-is. Send history (send date, recipient count, open rate, click rate) is exported as a CSV report and delivered alongside the migration for the customer to reference in Nutshell's analytics. Campaign-level automation triggers do not transfer; they are documented separately.

e-shot Automated Series are trigger-based email sequences tied to contact behaviour or date conditions. They have no direct Nutshell equivalent as a migratable object. We export the Series name, step count, trigger condition, step timings, and email content as a written inventory document. The customer's admin rebuilds each Series as a Nutshell workflow rule using the exported step content as reference. Tier limits on Series (basic: 3, pro: 25, omni: 100) are noted for reference when planning the rebuild.

e-shot Landing Pages are tier-gated (basic: 0, pro: 25, omni: 100). Nutshell does not have a native landing page builder. We export published landing page URL, form field definitions, and any associated campaign links as a written inventory. The customer recreates landing pages using a third-party tool (Unbounce, Leadpages, or a website CMS) and connects forms to Nutshell via web-to-lead or a direct integration. We do not migrate landing page content as code or HTML.

e-shot forms store field definitions, field types, and subscription preference data. We export form field names, types, and preference settings as a written inventory. Contact responses already stored as field values on Contact records migrate as part of the Contact-to-Person migration. The customer's admin recreates web capture forms as Nutshell web-to-lead forms or through a third-party form builder integrated to Nutshell.

e-shot contact preferences track opt-in status and subscription interests with tier limits on active preferences (basic: 25, pro: 50, omni: unlimited). We export preference centre structure and per-contact preference values as tag assignments or custom picklist fields on the Nutshell Person record. The customer's admin determines whether preferences become Nutshell custom fields or contact tags based on reporting needs.

e-shot Saved Filters define dynamic contact segments using field conditions with tier limits (basic: 10, pro: 25, omni: unlimited). We export each filter's name, field conditions, and operator logic. The conditions are converted to Nutshell saved view filter criteria and the saved view is configured in Nutshell post-migration. Dynamic filter refresh behaviour is replicated where Nutshell's saved view supports equivalent operators.

e-shot campaign reports include opens, clicks, bounces, unsubscribes, and delivery health per campaign. We export historical report data as CSV files with campaign name, send date, recipient count, open rate, click rate, bounce rate, and unsubscribe rate. These reports are delivered as reference data alongside the migration. Nutshell's built-in email reporting tracks sends from within the platform; the exported CSV serves as the historical benchmark against Nutshell-sent campaigns going forward.