Migrate from e-shot to monday CRM

e-shot Contacts map directly to Monday.com CRM People. We export all standard fields (email, first name, last name, phone, address) and custom contact fields defined in e-shot Settings > Contacts field manager. Each e-shot custom field becomes a Monday.com CRM People column; the field type is inferred from the e-shot field type (text, number, date, dropdown) and recreated as the nearest Monday.com column type. Merge-tag fallback values extracted from the field manager are set as default values on the destination column to prevent empty field display in any Monday.com email integrations.

e-shot tags stored as field values or list memberships migrate to Monday.com CRM Labels on People. Tags are extracted from the contact export as a comma-separated or multi-select value, then created as Monday.com Label options and applied to the corresponding People records. If the customer uses tags as a taxonomy for segmentation, we document the full tag list during scoping so that labels are created in Monday.com before contact migration begins.

e-shot contact preferences (opt-in status, subscription interests, topic preferences) migrate to Monday.com CRM People custom columns. Each active e-shot preference becomes a column: subscription flags become checkbox or toggle columns, and interest-based preferences become multi-select columns. We export only active preferences within the customer's tier limit and flag any preferences exceeding the basic tier ceiling of 25 for admin review before migration.

e-shot Saved Filters define dynamic contact segments using field conditions. We export filter definitions as written segment rules (field, operator, value) and replicate them as Monday.com CRM Board filter views. Since Monday.com filter views are not a data object but a saved UI state, we document the filter logic in a written segment map so the customer's admin can recreate the exact segmentation in Monday.com's filter panel.

e-shot Campaigns hold email content, template body, subject line, sender details, and scheduling. We export campaign records and associated template HTML as a reference archive stored in a Monday.com Workdoc or external document link. The campaign name, status, send date, and subject line are logged as a board item in a Campaign reference board so the customer's team can cross-reference email campaign history with People records. HTML template assets are preserved as-is in a document archive; dynamic content blocks are flagged for manual rebuild if they rely on e-shot's merge-tag engine.

e-shot campaign analytics (opens, clicks, bounces, unsubscribes, delivery health) are pulled from the analytics dashboard and delivered as a CSV archive or a Monday.com Workdoc with a structured table. These metrics do not map to native Monday.com CRM objects because Monday.com does not have an email analytics layer. The archive preserves historical campaign performance for audit and reporting continuity.

e-shot Forms store field definitions, field types, and subscription preferences linked to contact records. The form data itself lives in the contact records (migrated to People in Monday.com CRM). Form field definitions are exported as a written configuration map that the customer's admin uses to set up equivalent form logic in a third-party form tool (Typeform, HubSpot Forms, or Monday.com's native form integrations) if form capture continues post-migration.

e-shot Automated Series are workflow-based email sequences triggered by contact behaviour or date conditions. Monday.com CRM has no equivalent campaign automation layer for email sequences. We export Series definitions (trigger, conditions, delay steps, email actions) as a written inventory document with a recommended Monday.com Automation equivalent for each step. The customer's admin rebuilds the sequences using Monday.com Automations scoped to board item triggers; this document is delivered at the end of migration scope.