Migrate from e-shot to Odoo CRM

e-shot Contacts migrate to Odoo res.partner records. Standard fields (name, email, phone, address) map directly. Custom contact fields defined in e-shot Settings > Contacts field manager are extracted by API and replicated as custom fields on res.partner using Odoo Studio before migration. The merge-tag field name becomes the Odoo field technical name (e.g., *company_name* becomes x_eshot_company_name). We preserve the original merge-tag syntax as a field label so Odoo admins can verify personalisation during template testing.

e-shot's contact field schema is fully customisable. Every custom field definition (name, type, merge-tag syntax) is extracted from the e-shot field manager. Each field is created in Odoo before contact import begins. Picklist-type contact fields in e-shot map to Odoo selection fields; checkbox fields map to boolean; date fields map to date; text fields map to char or text depending on length. We flag any e-shot field type without an Odoo equivalent (e.g., complex multi-value arrays) for manual review during scoping.

e-shot personalisation uses *_fieldname=fallback('text')_* syntax for fields where some contacts lack values. We extract every fallback definition from the contact field manager and replicate them in Odoo's mail.mail_template model. Odoo's mail template system uses Jinja2-style {{partner.x_field}} with optional |default('fallback text') filters. We convert each e-shot fallback to an equivalent Odoo default value on the res.partner field, so contacts without a value render the fallback text without showing raw merge-tag syntax.

e-shot Campaigns have no direct Odoo equivalent. Each e-shot Campaign maps to a tag on crm.lead records, with the campaign name stored as a tag label (e.g., 'es_campaign_summer-promo'). The campaign audience (the contacts who received the campaign) is identified by tag membership. Campaign subject lines and sender details are not preserved as Odoo records; we document them in the handoff inventory. Campaign content (HTML body) migrates to mail.mail_template if the customer wants to reuse it in Odoo's email composer.

e-shot campaign analytics (opens, clicks, bounces, unsubscribes, delivery health) are pulled as CSV exports from the analytics dashboard and documented in the migration handoff inventory. Odoo CRM does not have native campaign analytics; the customer can import the CSV to Odoo's document management (ir.attachment) or a linked BI tool. We do not create Odoo analytics records from campaign report data because no equivalent schema exists.

e-shot email templates (HTML with embedded styles and merge tags) migrate as mail.mail.template records in Odoo. We extract template body as HTML content, replace e-shot merge-tag syntax with Odoo's Jinja2 {{partner.field}} equivalents, and set the template model to res.partner. Merge-tag personalisation is preserved as source values for re-enabling in the Odoo mail composer. Image assets embedded in templates are extracted as base64-encoded attachments or converted to Odoo-relative URLs depending on the template complexity.

e-shot Forms and the preference centre store subscription opt-in/out choices and contact field inputs. We export form definitions and per-contact preference data. Opt-in status migrates to the Odoo res.partner x_opted_in field (created during schema setup) and to the mail.mass_mailing.contact mailing list model if Odoo Marketing is installed. The form field structure and layout do not have a direct Odoo equivalent and are documented for the admin to rebuild in Odoo Forms or via Odoo Website builder.

e-shot Saved Filters define dynamic contact segments using field conditions. We export each filter definition as a set of domain conditions and replicate them as ir.filters records in Odoo scoped to res.partner. Tier limits from e-shot (basic: 10, pro: 25, omni: unlimited) do not apply in Odoo. Complex saved filters with multi-condition logic (AND/OR grouping) are translated to Odoo domain syntax and validated against the migrated field names.

e-shot Tags label contacts for segmentation without a formal taxonomy. Tags are stored as tag-name values on contact records and extracted during export. They map to res.partner.category records in Odoo. We deduplicate tag names (e.g., 'vip' and 'VIP' become one category) and preserve tag assignment on each contact during import. Tags used for campaign audience targeting become the tag-on-lead pattern described in the Campaign mapping.

e-shot Automated Series are workflow-based email sequences with trigger conditions, delays, and branching logic. Odoo CRM does not have a native cadence sequencer equivalent to Automated Series. We export the full Series definition (trigger type, conditions, steps, delays, email content) as a written inventory document. The customer's Odoo admin rebuilds them using Odoo CRM automation rules (server actions and automated actions on crm.lead) or the Odoo Marketing app if installed. We do not migrate Automated Series as functional records.

e-shot Landing Pages are tier-gated (basic: 0, pro: 25, omni: 100) and store published page content and form elements. Odoo does not have a direct landing page management module within CRM. If Odoo Website is installed, landing pages can be rebuilt there; otherwise we document the page URL, content structure, and form field mapping for the admin to rebuild. We export landing page content as HTML files and form field definitions in the handoff inventory.

e-shot Website Popups are campaign-triggered web overlays tied to contact identification. They have no equivalent in Odoo CRM. We export popup configurations (trigger conditions, display rules, content) as a written inventory document. If the customer uses Odoo Website, popups can be rebuilt using Odoo's website popup widget or a third-party integration. Popup data is not loaded into Odoo as records.