Migrate from e-shot to Zoho CRM

e-shot's single Contact object maps to Zoho CRM as Lead (for unqualified prospects with no active deal) or Contact (for buyers and customers linked to an Account). We apply a role-based split during scoping: contacts with campaign engagement history but no deal value become Leads; contacts with subscription or purchase history become Contacts attached to an Account. Custom contact fields from e-shot replicate as Zoho CRM custom fields on the appropriate module. Merge-tag fields like *firstname* become text custom fields; checkbox fields become Zoho picklists or multi-select picklists.

e-shot's contact field manager defines every custom field with its type and merge-tag fallback syntax (*fieldname=fallback('text')). We extract all field definitions including fallback values, then create equivalent Zoho CRM custom fields on the appropriate module (Leads, Contacts, or Accounts) before loading data. Fallback values become default values on the Zoho field. e-shot field types map to Zoho field types: text fields to Single Line, dates to Date fields, numbers to Numeric fields, and multi-value tags to Multi-Select Picklist.

e-shot campaigns with template content, subject lines, and scheduling metadata map to Zoho CRM Campaigns. The campaign name, status, type, and start/end dates migrate directly. We store campaign content blocks as Notes attached to the Zoho Campaign record. If the customer used e-shot campaign tags for segment classification, we replicate these as Zoho Campaign Custom Fields or as tag values in a custom Multi-Select Picklist.

e-shot Automated Series are behaviour-triggered email sequences tier-gated at 3, 25, or 100 live series depending on plan. These do not execute in Zoho CRM because Zoho does not have a native sales engagement cadence feature in standard CRM. We export every active series with its trigger conditions, step sequence, timing delays, and email content as a written Blueprint document. The customer's Zoho admin uses this to rebuild using Zoho CRM Workflows, Functions, or Blueprint.

e-shot Forms store field inputs and subscription preferences linked to contacts. We export form definitions (field names, types, required flags) and replicate them as Zoho CRM Web Forms or as custom fields on the Lead module. Form submission data migrates as Lead records with custom field values populated from the form submission. Subscription preferences from e-shot become Zoho CRM multi-select picklist fields on the Contact record.

e-shot preference centres track opt-in status and subscription interests per contact, tier-gated at 25, 50, or unlimited active preferences. We export the preference centre structure and per-contact preference values, then replicate as Zoho CRM custom fields on the Contact module. Opt-in status maps to the Zoho Email Opt-out field (boolean). Interest categories become custom multi-select picklist fields.

e-shot landing pages are tier-gated (basic: 0, pro: 25, omni: 100) and hold published HTML content with form elements. Zoho CRM does not include a native landing page builder in its standard CRM tier. We export landing page content and form field definitions as a written handoff document, not as functional pages. Customers needing landing pages in the Zoho ecosystem typically deploy Zoho PageSense or a third-party tool.

e-shot tags label contacts and segments without a formal taxonomy; they are stored as field values or list memberships. We extract all distinct tag values, then replicate as Zoho CRM Multi-Select Picklist fields on the Contact module. If the customer used tags for segmentation, we also create matching Zoho CRM Tags on the Contact record. Tag assignment migrates as field values, not as a separate tag management object.

e-shot saved filters define dynamic contact segments using field conditions, tier-gated at 10, 25, or unlimited by plan. We export each saved filter's field conditions and replicate them as Zoho CRM Custom Views on the Contacts or Leads module. The filter logic (field, operator, value) translates directly to Zoho's filter builder syntax.

e-shot campaign analytics (opens, clicks, bounces, unsubscribes, delivery health) are exportable from the analytics dashboard. We pull historical report snapshots and store them as Notes attached to the migrated Zoho CRM Campaign record, along with summary metrics stored as custom number fields on the Campaign module. This preserves the campaign performance context without requiring a separate BI export.