Migrate from Nurture to Odoo CRM

Nurture Contact records map to Odoo res.partner with partner_type set to 'contact'. The contact's email, phone, mobile, street, city, state, country, and postal code migrate directly to the equivalent Odoo address fields. Any Nurture contact custom fields (within the standard Contact model) map to Odoo custom fields created via Odoo Studio before migration. The contact's associated Nurture Company is resolved to the corresponding Odoo partner ID and written as parent_id on the Odoo contact to establish the company-contact hierarchy.

Nurture Company records map to Odoo res.partner with partner_type set to 'company'. Company name becomes the partner's name field, domain maps to the website field, and industry classification maps to a custom res.partner field or the industry_id reference. Companies are loaded first in every migration run because Contact foreign-key references require a parent_id lookup that cannot resolve until the Company exists in Odoo. The Nurture Company ID is preserved in a custom external_id field for traceability.

Nurture Deals map to Odoo crm.lead records with type 'opportunity'. The deal name becomes the opportunity name, amount maps to expected_revenue, and probability maps to probability. The deal stage from Nurture maps to a corresponding Odoo Sales Team pipeline stage defined during schema configuration. If Nurture deal records carry a Company or Contact reference, we resolve it to the Odoo partner_id before insert. Closed-won and closed-lost dates map to Odoo's date_closed field.

Each distinct Nurture deal stage becomes an Odoo stage record within a Sales Team pipeline. We configure the stage name, sequence, and probability percentage during schema setup. Odoo stages are scoped to a sales team (crm.team) via the team_id field; if the customer uses multiple Odoo Sales Teams, we assign each Nurture pipeline to its corresponding Odoo team during deal import.

Nurture call activities map to Odoo calendar.event with event_type set to 'call' and meeting_id pointing to the corresponding Odoo crm.lead or res.partner. Call duration in seconds maps to duration (converted to hours for Odoo's duration field), and call disposition notes migrate to the event's description field. The original Nurture activity timestamp becomes the event's start and stop datetime.

Nurture email activities map to Odoo mail.message records linked to the corresponding res.partner or crm.lead via model and res_id. Email subject becomes the message subject, body migrates as HTML content, and the sent timestamp maps to mail.message's date field. Thread tracking is preserved by setting the message relationship to the resolved partner or opportunity record.

Nurture meeting activities map to Odoo calendar.event with event_type set to 'meeting'. Start and end datetime migrate directly, location maps to location, and meeting title becomes the event name. Attendee relationships migrate as calendar.attendee records pointing to the resolved Odoo partner or user for each participant listed in the Nurture meeting activity.

Nurture Task activities map to Odoo project.task if the customer's Odoo instance has the Project app installed. Task title becomes the task name, description migrates to the task description, due date maps to date_deadline, and assigned user resolves via email match to the Odoo user. If Project is not installed, tasks migrate as internal notes on the related crm.lead using mail.message.

Nurture Notes (engagement type NOTE) migrate to Odoo mail.message with message_type set to 'notification' and subtype_xmlid set to 'note.mt_note'. The note body migrates as HTML content, and the relationship resolves to the corresponding Nurture record's mapped Odoo equivalent (partner, opportunity, or task). Priority and internal flag status from Nurture carry forward as custom fields on the mail.message record.

Nurture Owner records map to Odoo res.users by email address match. Every Contact, Company, Deal, and Activity record in Nurture carries an owner assignment. We extract the distinct owner list, resolve each by email to an existing Odoo user, and write the resolved user ID as the record's user_id (for leads) or write_uid (for audit fields). Any owner without a matching Odoo user is placed in a reconciliation queue for the customer's admin to provision before record import resumes.

Nurture custom fields on Contact, Company, and Deal migrate to Odoo custom fields created via Odoo Studio or as Python-defined fields in the data model. Field type mapping follows the destination schema: Nurture text and number fields map to Odoo char and float fields respectively; date fields map to Odoo date fields; multi-select values map to Odoo many2many or selection fields. Custom field creation happens in the schema design phase before any data migration begins. We preserve the original Nurture custom field name in a field label for traceability.

Nurture tags on Contact and Deal records map to Odoo crm.tag records. Tags are loaded into the tag master table first, then linked to the target crm.lead records via crm.lead.tag_rel during deal import. If a tag name in Nurture matches an existing Odoo tag, we reuse it rather than creating a duplicate. Multi-value tags on a single record become multiple rows in crm.lead.tag_rel.