Migrate from e-shot to Twenty CRM

e-shot Contacts map to Twenty Person records. Every standard system field (email, name, phone, address) maps directly. Custom contact fields defined in e-shot Settings > Contacts Field Manager must be pre-created in Twenty as custom fields on Person before import. We extract the full field schema including field type, required flag, and any picklist options. Tag assignments stored as list membership in e-shot are resolved and written to a tags__c multi-select field on Person.

e-shot's fully customisable contact field schema requires pre-creation in Twenty before any records load. We extract every field definition (name, type, merge-tag syntax *_fieldname_*) and replicate it in Twenty's Settings > Data Model as custom fields on Person. The mapping document is the critical dependency: without it, imports fail on undefined field references. Field type translation includes date fields, numeric fields, boolean checkboxes, and picklist values.

e-shot Campaigns do not have a native Twenty equivalent. We create a Campaign custom object in Twenty with fields for campaign name, subject line, send date, open rate, click rate, bounce rate, and unsubscribe rate pulled from campaign report data. Campaign content (HTML body, template assets) is preserved as Notes attached to the Campaign custom object record. This is a re-design decision: the customer chooses whether to migrate historical campaign metrics as audit records or to start fresh with new campaign tracking post-migration.

e-shot Automated Series are workflow-based email sequences with trigger conditions and delays. Twenty has no native equivalent to marketing automation sequences. We export the series name, trigger condition, step count, and step content as records in a Campaign Automation custom object for audit purposes. The customer receives a written rebuild guide that documents each series as a step-by-step workflow description with recommended Twenty or third-party automation alternatives (such as n8n, Make, or a custom GraphQL workflow) so the admin can rebuild sequences post-migration.

e-shot Forms store field definitions, form structure, and contact inputs. We export form field types and labels as a form definition record in a Form custom object in Twenty. Form submission data (actual contact responses) is written to the related Person record where the form field matches a custom field. Form configuration (redirect URLs, thank-you messages) is preserved in the notes field for manual rebuild.

e-shot contact preferences track opt-in status and subscription interests. These map to custom fields on the Twenty Person record — one custom field per preference topic. Tier limits on active preferences in e-shot (basic: 25, pro: 50, omni: unlimited) do not apply in Twenty; we create all preference fields within the customer's custom field budget. Preference values migrate as field values, not as a separate preference centre object.

e-shot tags are stored as field values or list memberships, not as a separate tag management object. We extract every distinct tag value across all contacts and create a multi-select picklist field tags__c on the Person object in Twenty. Tag assignments per contact are written as pipe-delimited values in the field. If more than 200 distinct tags exist, we recommend a separate Tags custom object with a many-to-many relationship to Person via a junction table.

e-shot Saved Filters define dynamic contact segments using field conditions. We export the filter name and full condition logic (field, operator, value) for each active saved filter as a written specification document. Twenty Views replicate saved filter functionality using field-based filtering. The customer's admin rebuilds each view in Twenty using the exported filter specification. Filter logic does not migrate as code.

e-shot campaign analytics (opens, clicks, bounces, unsubscribes, delivery health) are exportable from the analytics dashboard. We pull historical report snapshots per campaign and write them as custom fields on the Campaign custom object records created during migration. This preserves campaign performance data for historical reference and reporting in Twenty's analytics views.

e-shot email templates store reusable HTML content blocks with embedded styles and merge tags. We export templates as HTML files and attach them as Notes to the relevant Person or Campaign record in Twenty. Merge tag syntax (*_fieldname_*) is preserved as-is in the template body for manual reactivation in a template tool post-migration. If the customer uses Twenty's note-based template system, we provide a template mapping guide.

e-shot Landing Pages are tier-gated (basic: 0, pro: 25, omni: 100) and hold published content with form elements. Twenty has no native landing page builder. We export landing page content as HTML files and form field mappings as a written inventory. The customer's admin rebuilds landing pages in a dedicated landing page tool (Twenty compatible or standalone) and maps form submissions to Twenty Person records using the exported field mapping.

e-shot Website Popups are campaign-triggered web overlays tied to contact identification. Tier limits apply (basic: 0, pro: 25, omni: 100). Twenty has no native popup or website overlay feature. We export popup configurations, trigger rules, and display logic as a written inventory. The customer rebuilds popup functionality in a website overlay tool compatible with Twenty's tracking (e.g., OptinMonster, Privy) and maps new submissions to Twenty Person records.