Migrate from Membrain to Odoo CRM

Membrain Company records map to Odoo res.partner with is_company=True. Standard address, industry, and owner fields migrate directly. Company name becomes the partner display name. We deduplicate by company name and domain on import. The partner is created before any related Contact import so that the child_contact relationship is satisfied.

Membrain Contact records map to Odoo res.partner with is_company=False and parent_id set to the mapped Company partner. Email, phone, title, and custom fields migrate directly. Deduplication runs on email address with a fuzzy match fallback on name for records without email. The child-contact relationship in Odoo uses parent_id on res.partner rather than a separate contact object.

Membrain Prospects (from the Prospecting module) map to Odoo crm.lead with type=lead. Prospects carry their own lifecycle stages and custom fields which map to crm.lead stage and custom stage fields. If Odoo Enterprise is in use, the lead_source field captures the original prospect origin. Prospects without an assigned Company map as standalone leads.

Membrain Sales Projects map to Odoo crm.opportunity. Company links to the mapped res.partner, primary Contact to the mapped res.partner child contact, deal value to planned_revenue, expected close date to date_deadline, and owner to the mapped Odoo user. The Odoo opportunity is created after its Company and Contact parents so that partner_ids and partner_id lookups resolve correctly.

Membrain Account Growth Projects track expansion work at the Company level. We map these to Odoo crm.opportunity with type=opportunity and a custom field account_growth_source=True to distinguish them from Sales Projects. Custom fields specific to account growth (expansion targets, account plan status) migrate to custom opportunity fields created in Odoo before import.

Membrain's custom stage names and probabilities per Sales Project type map to Odoo crm.stage records within the appropriate sales team. Stage sequence and probability percentages transfer to stage_sequence and legend_priority. Odoo stages are global across teams by default; if the customer requires team-scoped stages, we configure sales.team stage_relace_ids during setup.

Membrain Appointment records map to Odoo calendar.event linked to the migrated crm.lead or crm.partner. Start datetime, duration, location, and description migrate directly. Attendees resolve via the mapped Contact and User records and are created as calendar.attendee entries.

Membrain Call records map to Odoo crm.phonecall (an optional Odoo module that must be installed before migration). Call duration, disposition, and notes migrate to phonecall fields. The call is linked to the mapped partner and opportunity via partner_id and opportunity_id. If crm.phonecall is not installed in the destination Odoo instance, calls migrate as crm.lead activities instead.

Membrain Notes map to Odoo mail.message records posted on the res.partner or crm.lead timeline. Rich text body migrates as HTML content. The message author resolves to the mapped Odoo user by email. Notes attached to a specific record carry that record's model and res_id in the mail.message link.

Membrain Email records (sent from within Membrain) map to Odoo mail.mail linked to the res.partner recipient. Email body, subject, and timestamp migrate. Emails sent outside Membrain (e.g., via Outlook) that were logged as engagements migrate as mail.message records rather than mail.mail since Odoo cannot receive external emails without IMAP sync configuration.

Membrain Tasks map to Odoo project.task linked to the migrated crm.lead or res.partner. Task name, description, due date, priority, and assigned user migrate. If the destination Odoo instance has the project module installed, tasks live in the project context; otherwise they migrate as CRM activities.

Membrain custom fields use CustomField{GUID} property names that contain no human-readable label in the data payload. We query Membrain's custom field definitions first to build a GUID-to-label lookup table, then create matching custom fields in Odoo via developer mode or the res.config.settings interface before data import. Field types map from Membrain's type (text, number, date, picklist) to Odoo's corresponding field type (char, float, datetime, selection). Custom fields on Activities (Appointments, Calls, Notes) require the relevant Odoo module to be installed and the custom field created on the correct model.