Migrate from ELAINE to Odoo CRM

ELAINE Contacts migrate to Odoo res.partner records with is_company=False. Standard fields (name, email, phone, address) map directly. Custom fields on ELAINE Contacts map to Odoo custom fields on res.partner created during schema setup. Any enrichment data added via ELAINE's API to custom fields transfers as field values. If the customer uses ELAINE's company association on contacts, we create the parent res.partner as a company record (is_company=True) and link the contact as a child partner.

ELAINE Target Groups are segment definitions that assign contacts to named groups. We migrate Target Group membership by creating corresponding Odoo Tags (via res.partner.category) and Odoo CRM Groups (via crm.team). Each ELAINE Target Group becomes either a Tag or a CRM Group depending on whether it represents a marketing segment (Tag) or a sales team assignment (CRM Group). Nested Target Group hierarchies are flattened: we preserve the full hierarchy path as a tag name (e.g., 'Tier 1 > Active > Re-engagement') and document it for manual reconstruction in Odoo if the customer needs the hierarchy enforced as a filter view.

ELAINE Email Campaigns are migrated as CRM activity records in Odoo: each campaign becomes a Note on the relevant partners (the campaign recipients), with the campaign name, send date, and subject recorded in the note body. Campaign-level metrics (send count, open rate, click rate) are preserved as custom fields on the note or as a linked custom CRM report model. Active campaigns in progress at migration time are flagged for the customer's admin to re-send from Odoo Email Marketing or an external tool post-migration.

ELAINE Mail Sequences (automated multi-step email cadences) are extracted as step-by-step inventories: trigger condition, delay, email content, and conditional branch. We do not migrate Mail Sequences as executable code because Odoo uses a different automation model (Automated Actions, CRM pipeline rules, and Studio workflows). We deliver a written Mail Sequence Map for each active sequence, listing trigger, steps, delays, conditions, and the recommended Odoo Automated Action or Studio workflow equivalent. The customer's Odoo admin or implementation partner rebuilds the sequences post-migration.

ELAINE A/B test configurations (subject line variants, content variants, send-time variants, and winning criteria) are migrated as documentation. We extract the test name, variant configurations, and performance results and record them as a Note on the CRM record. Odoo Email Marketing does not have a native A/B testing module in the core CRM; teams requiring A/B testing post-migration use Odoo Email Marketing's built-in campaign tools or a third-party app from the Odoo Marketplace.

Custom fields on ELAINE Contacts (text, choice, date, calculated fields) are pre-created in Odoo on the res.partner model before any contact data is imported. We match field types: ELAINE text maps to char or text in Odoo depending on length; choice/picklist maps to selection field; date maps to date; calculated fields map to readonly computed fields if Odoo technical access is available, otherwise to stored char for manual population. All custom field API names are preserved with the field name prefixed by the source system to avoid naming conflicts.

Custom fields defined on ELAINE Target Groups migrate as documentation unless the customer has a specific use case that justifies a custom res.partner.category extension model in Odoo. We flag this during scoping. In most cases, Tag-level metadata (e.g., priority, budget tier) is better represented as Tags with a naming convention or as custom fields on the CRM Group model if the customer licenses Odoo CRM Teams.

Files attached to ELAINE Contacts, Target Groups, or Campaigns are downloaded and stored in Odoo's ir.attachment table with the res_model set to res.partner (for contact attachments) or crm.lead (for campaign references). The original file name and MIME type are preserved. Attachments linked to contacts that are deleted before migration are flagged in the attachment inventory for the customer to review and optionally re-associate.

ELAINE Owners (users managing contacts and campaigns) are mapped to Odoo res.users by email match. We extract all distinct owner references on contacts, campaigns, and target groups and resolve them against the destination Odoo instance's user table. Any ELAINE Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before the contact import phase begins.

If ELAINE contacts were enriched via external API (e.g., GDPR-compliant subscriber enrichment), the enrichment data is already stored as field values on the contact record and migrates with the contact. Any third-party API connection configured in ELAINE needs to be re-established post-migration with updated webhook or API credentials in Odoo's Webhook or external API module.

ELAINE's GDPR-compliant subscriber consent records (opt-in, opt-out, consent date, consent source) migrate to Odoo's mail.mass_mailing.contact model if the customer uses Odoo Email Marketing, or to custom opt-in fields on res.partner if no mass mailing module is active. We flag which model is appropriate during scoping based on the customer's Odoo app inventory.

If ELAINE contacts are associated with subscription or recurring billing profiles (e.g., newsletter subscription tiers), we migrate the subscription status as a res.partner Tag and the subscription metadata as custom fields on the partner record. If the customer licenses Odoo Subscriptions, we map to sale.subscription and link the subscription to the partner record. We confirm the Odoo app inventory during discovery to determine which model applies.