Migrate from Mothernode to Odoo CRM

Mothernode Customers map to Odoo res.partner records with partner_type set to 'company'. The customer_id becomes the partner_id for cross-referencing. Mothernode's department-level organization maps to Odoo's company structure (res.company) if the customer uses multi-company; otherwise department data is preserved in a custom field for segmentation. Customer billing and shipping addresses migrate as separate address records (partner addresses with type='invoice' and type='delivery').

Mothernode Contacts map to Odoo res.partner records with partner_type set to 'contact' and a partner_id pointing to the parent Company Partner record created from the associated Mothernode Customer. We resolve the parent linkage at migration time using the customer_id reference in the Mothernode Contact record. Contact role or title migrates to res.partner.function. Phone and email fields map directly.

Mothernode Leads (distinguished from Opportunities by the record type indicator in the API response) map to Odoo crm.lead with optional_type='lead'. The Lead's email, phone, company_name, and description fields migrate directly. We set crm.lead.priority based on any priority field in the Mothernode record. Lead source information from Mothernode migrates to the crm.lead.source_id lookup if Odoo's CRM is configured with stages; otherwise it is preserved in a custom field.

Mothernode Opportunities map to Odoo crm.lead with optional_type='opportunity'. The Mothernode deal stage maps to an Odoo stage_id within a configured Odoo CRM pipeline. Probability is computed from the stage mapping or carried from Mothernode's stage probability if available. Expected revenue, partner_id (linked to the Customer), and user_id (owner) migrate directly. Closed-won and closed-lost reasons migrate to Odoo's lost_reason_id field if configured.

Mothernode Opportunity stages are extracted from the source data and mapped to Odoo crm.stage records within the target pipeline. We create stages in Odoo matching the source stage names and assign probability weights matching the source. If Mothernode uses multiple pipelines, we create separate crm.team records in Odoo and assign the relevant stages per team. Stage order is preserved by setting sequence values matching the source order.

Mothernode Notes migrate to Odoo mail.message records with message_type='notification' linked to the parent crm.lead (for Opportunity Notes) or res.partner (for Contact Notes). Note body migrates as HTML content. Author attribution is resolved by matching the Mothernode author name or email to a res.users record; if no match is found, the note is attributed to the migration user. create_date and write_date timestamps are preserved from the source.

Mothernode Events migrate to Odoo calendar.event records. Start and end datetime, duration, location, and description fields migrate directly. Attendee links are resolved by matching the associated Contact or Opportunity to their migrated Odoo records, creating calendar.attendee entries for each. All-day event flags migrate to allday=True on the Odoo record. Recurrence data is not migrated; recurring events are imported as individual instances with a custom recurrence flag set.

Mothernode Invoices map to Odoo account.move records with move_type='out_invoice' for customer invoices. Line items, totals, tax amounts, and payment status migrate to the corresponding Odoo fields. The customer_id reference is resolved to the migrated res.partner record. Odoo requires the account.move records to belong to a specific company_id; if the customer uses Odoo multi-company, we assign the correct company during migration. Invoice PDF attachments migrate as ir.attachment records linked to the account.move.

Mothernode owner_id references on Leads, Opportunities, and Events map to Odoo res.users by email match. We extract every distinct owner referenced in the source data and match against the Odoo destination's User table. Any Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId (user_id on crm.lead) is a required lookup for Opportunity migration.

Mothernode custom fields are not explicitly documented in the API reference. We probe the API response schema during the extraction phase to identify non-standard field names and infer their data types from values. We pre-create Odoo custom fields (ir.model.fields with track_visibility set to 'onchange') in the destination database before the main migration phase so that custom field values are populated during the data load rather than lost. Custom field migration happens in a pre-migration schema phase.

Project Folders are a Mothernode Enterprise-tier feature with unconfirmed API availability. We probe the API during extraction; if endpoints return 403 or 404, we flag Project Folders as requiring manual UI export. For teams where Project Folders are critical, we map them to Odoo project.project records with the project type set to 'private' or 'task' as appropriate. Project-related data links to migrated Contacts and Opportunities via Odoo's project.task model with partner_id lookups.

Job Center Modules are not covered in the Mothernode public API reference. We flag Job records as requiring manual export from the Mothernode UI and document the mapping to either Odoo mrp.production (for manufacturing jobs) or project.task (for service jobs) during the scoping call. The customer's Odoo administrator determines which model is appropriate based on their operational use of Job Center.