Migrate from Odoo Field Service to Mailchimp

Odoo partner records where is_company=False map directly to Mailchimp Audience members. Email address serves as the unique identifier; contacts without a valid email address are flagged for manual review before migration begins. The original Odoo partner ID is preserved in a custom merge field (ODOO_PARTNER_ID__c) for traceability back to the source system. This allows your team to cross-reference Mailchimp subscribers with Odoo records for reconciliation, audit purposes, and data governance requirements.

Odoo partners where is_company=True represent organizations. These migrate as individual Audience members with the company name populated in Mailchimp's built-in COMPANY merge field. Child contacts of that company are linked by having matching company_name in their merge field, creating a soft association that enables segmentation by company without native hierarchy support.

Odoo contact tags (category_id) map 1:1 to Mailchimp Tags. Each Odoo tag name becomes a Tag in Mailchimp applied to the corresponding subscriber. Tags with no contacts are excluded. Tag names are lowercased and spaces replaced with hyphens for Mailchimp compatibility.

Odoo's country_id (many2one relationship to res.country) stores the full country name. This maps to Mailchimp's COUNTRY merge field, which Mailchimp auto-creates when needed. Geographic segmentation works immediately on import, allowing you to create Mailchimp Segments filtering by country for regional campaigns, localized content, and compliance with regional email regulations such as GDPR for EU contacts.

Odoo stores address as street, street2, city, state_id, zip, country_id. Mailchimp has a single ADDRESS merge field with format 'city, state zip country'. We concatenate these into the standard Mailchimp format during migration. State names are resolved to abbreviations where Odoo state_id records exist.

Odoo's separate phone and mobile fields map to Mailchimp's single PHONE merge field. When both phone and mobile numbers exist in Odoo for a partner, the mobile number takes priority in the PHONE merge field since Mailchimp supports only one phone field per subscriber. Phone numbers are validated for format consistency during the migration to ensure deliverable contact information.

Any Odoo custom fields on res.partner (x_*, x_studio_*) are created as Merge Fields in Mailchimp with matching type (text, number, date, checkbox). Field labels become merge field names; field types are mapped: char/text to text, integer/float to number, boolean to checkbox, date/datetime to date.

Odoo partner titles (Mr., Ms., Dr.) map to Mailchimp's HONORIFIC merge field. If Odoo uses non-standard titles or professional designations not recognized by Mailchimp's standard options, they are preserved as-is and a custom merge field is created to hold the additional title variants. This ensures no title information is lost during the migration while maintaining compatibility with Mailchimp's built-in field for standard honorifics.

Odoo's function field on res.partner (representing the contact's job title at their company) maps to Mailchimp's JOBTITLE merge field for professional segmentation. This enables B2B marketing use cases such as filtering contacts by seniority level, targeting specific departments, or personalizing email content with the recipient's role. Job title data supports creating segments for industry-specific campaigns and account-based marketing workflows.

Mailchimp does not natively track record creation date. We create a DATE_CREATED merge field and populate it from Odoo's create_date so marketing teams can filter by how long a subscriber has been in the system. write_date is preserved as MODIFIED_DATE__c for reconciliation audits.

Odoo Field Service task and order records have no Mailchimp equivalent. These objects are excluded from the migration payload. If you need task-related context (e.g., service history) in Mailchimp, we can create a custom merge field summarizing recent task activity as text for reference purposes.

Odoo marks opted-out partners with a boolean flag. These contacts are migrated to Mailchimp with 'unsubscribed' status rather than 'subscribed', honoring the communication preference recorded in Odoo. Re-subscription requires explicit opt-in in Mailchimp through the platform's interface or API. If Odoo's opt-out flag represents temporary campaign suppression rather than a permanent unsubscribe preference, we recommend reviewing these records before migration to determine whether they should be migrated as subscribed contacts with a tag indicating their Odoo communication preference.