Migrate from Odoo CRM to Mailchimp

Odoo res.partner holds both individual contacts and company records. Standard fields (name, email, phone, street, city, state, zip, country, company_name) map directly to Mailchimp's corresponding contact fields. We use email as the dedupe key to prevent duplicate members on re-import. company_id on res.partner maps to the company_name field in Mailchimp. Contacts without an email address are flagged during extraction and held in a separate CSV for the customer's admin to enrich before Mailchimp import.

Custom fields defined via Odoo Studio or custom addons on res.partner are stored as columns in the database. We export the field type (char, integer, float, selection, many2one, many2many, date, datetime) and create matching Mailchimp Merge Fields before contact import. Selection fields map to Mailchimp dropdown or radio merge fields; many2one references map to text fields containing the related record name; many2many fields map to text fields with pipe-separated values. Odoo field labels become Merge Field names; field definitions are preserved in the migration inventory.

Odoo CRM Tags applied to crm.lead records via the crm_tag_rel many2many table are linked to res.partner via the contact_id field when the tag is applied to a contact. We extract tag names and map them to Mailchimp Tags using email as the linking key. Tag names are preserved verbatim. If the same tag name exists in multiple Odoo contexts (Lead vs Opportunity), we consolidate to a single Mailchimp Tag. Tags without a corresponding email in the contact extract are held for manual review.

Odoo Lead records (crm.lead with type='lead') carry stage_id, source_id, and priority fields. Mailchimp has no Lead object, so we migrate the lead status and source as Merge Fields (F_LD_STATUS, F_LD_SOURCE) or as Tags prefixed with LStatus_ or LSource_ at the customer's election during scoping. Probability, expected revenue, and AI lead score fields are flagged as non-migratable and included in the CRM inventory CSV.

Odoo Sales Teams group Opportunities and assign Leads to team members. Mailchimp has no team concept, so crm.team.name maps to either a Mailchimp Segment (if the customer wants filterable team grouping) or a Tag on each contact (if simple labeling is sufficient). Team membership via crm_team_member_rel is not migratable; only the team name per contact record transfers. This mapping requires the customer to choose the representation during scoping.

Odoo Pipeline Stages define the position of a Lead or Opportunity in the sales funnel. Mailchimp has no pipeline or stage concept. Stage names are not migratable and are included in the CRM inventory export as a CSV column for manual reference. If the customer elects to tag contacts by their last associated opportunity stage, we map stage names to Tags at additional scoping cost, but the CRM context is lost.

Odoo Activities (calls, emails, meetings, tasks) linked to crm.lead records are stored in mail.activity with type, date_deadline, user_id, and note fields. Mailchimp tracks opens and clicks per email campaign, which is campaign-level activity data, not the per-contact CRM activity timeline. Activity history is not migratable. We export activity records as a CSV deliverable with contact email, activity type, date, user, and note for the customer's admin to review.

Odoo Quotations and Sale Orders (sale.order with sale.order.line) linked to Opportunities carry line items, pricing, and taxes. Mailchimp has no Quote or Order object. Sale order data is not migratable. We export sale.order and sale.order.line records as a CSV deliverable keyed by the contact email, with order number, date, line item description, quantity, unit price, and total for manual re-entry or third-party order management integration.