Migrate from Freshmarketer to Odoo CRM

Freshmarketer Contact maps to Odoo res.partner. The contact's individual fields (name, email, phone, address) transfer directly. The linked Freshmarketer Company is preserved in a custom field parent_partner_name__c and merged by looking up org_contact_id. Lifecycle Stage from Freshmarketer migrates as a custom char field lifecycle_stage__c on the partner record for audit continuity. Email address is the dedupe key; Odoo will merge on email match, which must be anticipated during scoping.

Freshmarketer Company maps to a separate res.partner record with partner_type set to company. The org_contact_id from Freshmarketer contacts links individual partner records to the organization partner via parent_id. We create organization partners first so that the parent_id lookup is satisfied at the time of individual partner import. Company domain, industry, size, and address fields map to equivalent res.partner fields.

Freshmarketer Deal maps to Odoo crm.lead. Pipeline name and stage name map to Odoo's crm.stage sequence; stage order must be configured in Odoo before Deals are imported. Deal amount maps to expected_revenue on the lead; close date maps to date_deadline. Owner from Freshmarketer resolves to Odoo user_id via email match. Custom deal fields migrate as custom_char, custom_date, or custom_selection fields on crm.lead.

Freshmarketer email engagement logs migrate to Odoo mail.message records linked via res.model = crm.lead and res_id = lead_id to the target lead. Email body, subject, timestamp, and sender-recipient details transfer to mail.message body, subject, date, and author_id. Odoo does not support a separate activity timeline object for emails the way Freshmarketer does; all email history consolidates into the lead's chatter thread via mail.message.

Freshmarketer call engagement logs migrate to Odoo crm.activity records with activity_type_id set to the Call activity type. Call duration, disposition notes, and timestamp transfer to crm.activity duration, note, and date fields. Activity is linked to the target crm.lead via res_id. We pre-create the Call activity type in Odoo if it does not exist in the target database.

Freshmarketer meeting engagements migrate to Odoo calendar.event records with linked crm.lead via calendar.event.res_id and res_model = crm.lead. Meeting title, start datetime, end datetime, location, and description transfer to equivalent calendar.event fields. Attendee mapping links to res.partner records via event.partner_ids.

Freshmarketer note engagements migrate to Odoo mail.message records with message_type = notification and subtype = note. Note body transfers to mail.message body. Notes are linked to the target res.partner (for individual contacts) or crm.lead (for deal-linked notes) via res_model and res_id. The original Freshmarketer engagement timestamp is preserved in a custom field original_date__c on the message.

Freshmarketer task engagements map to Odoo crm.activity records with activity_type_id = Task. Task title, description, due date, status, and priority transfer to crm.activity name, note, date_deadline, state, and priority. Owner assignment migrates by resolving the Freshmarketer owner email to an Odoo user_id. Completed tasks set state = done.

Freshmarketer tags migrate as crm.tag records in Odoo. Tags are applied to crm.lead records via the crm.lead.tag_ids many2many relationship. Tags stored as multi-checkbox custom properties on Freshmarketer contacts migrate as individual tag records and are re-applied via tag_ids on the mapped res.partner. No tag hierarchy exists in either platform, so no structural transformation is required.

Custom fields on Freshmarketer contacts, companies, and deals require explicit per-field mapping against Odoo custom field definitions. Field type differences (dropdown vs. text, date formats, multi-select arrays) must be resolved during the transform phase before import. We pre-create all custom fields in Odoo via XML data or the Settings UI before any data loads. Multi-select values from Freshmarketer arrays flatten to a comma-separated string in Odoo char fields unless a custom many2many field is configured.

Freshmarketer's Marketing Contacts billing concept has no Odoo equivalent. We flag every contact that was enrolled in an active email, SMS, or WhatsApp campaign at cutover time and write the enrollment state to a custom boolean field is_marketing_contact__c on the res.partner record. This preserves the billing-flag data for any downstream marketing re-implementation without incurring Odoo licensing costs. We do not migrate Marketing Contacts as a separate object because Odoo does not have a billing-tier concept for contacts.

Freshmarketer Segments (audience filtering rules) have no direct Odoo equivalent. We map segment criteria to Odoo static tag groups or create a custom many2many field segment_ids on res.partner to hold segment membership. Dynamic audience logic (segment rules that auto-update) cannot be reproduced in Odoo's standard CRM without custom development; we document the segment rules in a written reference and the customer decides whether to rebuild as tags, static lists, or a custom module.

Freshmarketer pipeline and stage names map to an ordered crm.stage sequence in Odoo CRM. Stages are created in the sequence matching Freshmarketer's stage order before any Deal data is imported. Each stage is assigned to the relevant crm.team. Stage probability percentages from Freshmarketer are stored in a custom float field stage_probability__c on crm.stage if the customer wants to preserve probability modeling. Pipeline-level reporting groups in Freshmarketer map to Odoo crm.team groupings.

Freshmarketer Users (owners assigned to contacts, companies, and deals) map to Odoo res.users by email address lookup. We extract all distinct owner emails from Freshmarketer records and match against the destination Odoo user directory. Any owner without a matching Odoo user is held in a reconciliation queue for the customer's admin to provision before the Deals import phase. Active vs. inactive status on the Freshmarketer owner does not block import; we map to an active Odoo user regardless of status source.

File attachments on Freshmarketer contacts, deals, and activities are exported to a file store (S3 or local) and loaded into Odoo ir.attachment records. Each ir.attachment is linked via res_model and res_id to the target res.partner or crm.lead record. Attachment filename, MIME type, and binary content transfer directly. Odoo stores attachments in the database by default; large attachment volumes may require Odoo file storage configuration to avoid database bloat.