Migrate from eMarketeer to Odoo CRM

eMarketeer Contacts map directly to Odoo CRM Contacts. Email, name, phone, and address fields migrate 1:1. We map lifecycle stage from eMarketeer's hs_persona or lifecycle property to a custom Contact selection field in Odoo. Any custom contact properties (e.g., industry vertical, product line) require pre-creation in Odoo as custom fields on res.partner before migration. Contact is inserted before Account to satisfy the parent lookup.

eMarketeer Company records map to Odoo Account (res.partner with company_type = 'company'). The company domain becomes the Account's website field. We use domain as the dedupe key during import to avoid creating duplicate Accounts when multiple eMarketeer Contacts share the same company domain. Account is created before Contact so that the Contact's parent_id (Account link) is resolved at insert time.

eMarketeer Campaigns (email and multi-channel sends) do not have a direct Odoo CRM equivalent because Odoo CRM lacks native campaign performance analytics in the base CRM module. We map campaigns with send history to Odoo CRM Leads or Opportunities, with campaign name as the Lead/Opportunity name and campaign metadata (send date, open rate, click rate) stored as custom fields on the lead. If the customer uses Odoo Marketing (Online/Enterprise), campaign records migrate as Odoo Campaign records.

eMarketeer Segments are criteria-based groups that re-evaluate continuously. When migrating to Odoo CRM, we snapshot the current membership of each segment and import those contact IDs as a static Mailing List in Odoo. The segment criteria rules themselves cannot be replicated as live-updating groups in Odoo without Odoo Marketing (dynamic Smart Views). We flag which segments use real-time criteria versus static membership and advise the customer on the difference in behavior.

eMarketeer Flows (trigger-action automation sequences) map to Odoo Server Actions and Automated Actions, but the trigger types and condition models differ significantly. eMarketeer supports lifecycle-change triggers, form-submission triggers, and external CRM event triggers that have no direct Odoo CRM equivalent. We audit each flow during discovery, document the trigger and each step in a written inventory, and provide a recommended Odoo Server Action or Automated Action equivalent. The customer rebuilds the actual automation in Odoo.

eMarketeer Events (registrations and attendance tracking) map to Odoo Calendar Events linked to the corresponding Contact records. Registration status (registered, attended, no-show) migrates as a custom selection field on the calendar event. For event types with attendee check-in tracking, we create Odoo Project Tasks under a dedicated project if the customer licenses the Project module.

eMarketeer custom contact properties (text, number, date, dropdown, multi-select) require pre-creation in Odoo as custom fields on res.partner before any contact data inserts. We derive the full property schema from the export during discovery because eMarketeer has no documented field registry. Property types map to Odoo field types: Char, Float, Date, Selection, or Many2many. Enumeration values from dropdown and multi-select properties become Odoo Selection options or Many2many relation records.

eMarketeer email templates export as HTML blobs. We provide the raw HTML for import into Odoo's email template system. Visual template editors with locked components may not reconstruct identically in Odoo's template editor, so we flag any unsupported blocks (e.g., dynamic content from proprietary eMarketeer syntax) and provide the raw HTML for manual reconstruction.

SMS sends tracked in eMarketeer flows migrate as Odoo SMS records linked to the recipient Contact. We import SMS content, send timestamp, and delivery status metadata. Delivery receipt details and opt-out states may require reconciliation against Odoo's SMS gateway if the customer uses a different SMS provider in Odoo.

Open, click, and unsubscribe events per contact per campaign aggregate into a contact activity log in Odoo as mail.message records linked to the Contact. Odoo CRM does not have a native real-time engagement tracking dashboard, so the historical activity log provides an audit trail without live sync. The customer can use Odoo Reporting to build custom activity reports if needed.

eMarketeer Owners (users who sent campaigns or managed contacts) map to Odoo User records by email match. We resolve each Owner email against the destination Odoo instance's res.users table. Any Owner without a matching User is placed in a reconciliation queue for the customer's admin to provision before record import resumes.

Form definitions and embedded layout configurations are not reliably exportable from eMarketeer. We do not migrate form records. We export the contact data submitted through forms as part of the contact migration, and provide a field-level reference map (which eMarketeer form field maps to which Odoo Contact field) so the customer's admin can rebuild forms in Odoo using Odoo's form builder or a third-party web form linked via Odoo's API.