Migrate from Nimble CRM to Odoo CRM

Nimble Contacts map directly to Odoo Contact records. Social enrichment fields (LinkedIn URL, Twitter handle, Facebook URL) migrate as custom Char fields since Odoo stores social links as a dedicated Social Networks page on each contact. Email address serves as the dedupe key. We export Contacts after Companies so that the company_id lookup resolves against the Odoo Partner created from the Nimble Company record.

Nimble Companies map to Odoo Partner records with the is_company flag set to True. Company name becomes the Partner name; domain becomes the website field. Address components (street, city, state, country, zip) map to Odoo's address fields (street, street2, city, state_id, country_id, zip). We export Companies first in all migrations so that subsequent Contact imports can satisfy the company_id foreign key in Odoo's ORM.

Nimble Deals map to Odoo CRM Opportunity records. The Nimble deal stage label maps to an Odoo Stage within the relevant Sales Team's pipeline. Deal value (amount), close date, and probability migrate directly. Loss reason custom fields on Nimble Deals map to Odoo's Lost Reason picklist. We configure Odoo Stages before migration to match the labels and probability percentages from the Nimble pipeline.

Nimble pipeline stages map to Odoo CRM Stage definitions within the target Sales Team. Stage sequence and probability percentages migrate from Nimble's stage configuration. Odoo requires Stages to be created per Sales Team, so if the Nimble account uses multiple pipelines, we create corresponding Sales Teams in Odoo and map stages into each team's kanban view.

Nimble Owners map to Odoo User records matched by email address. Any Nimble Owner without a matching Odoo User goes into a reconciliation queue; the customer's Odoo admin provisions missing Users before record import resumes. Inactive Nimble owners map to Odoo Users with the Active flag set to False to preserve historical assignment without granting login access.

Nimble logged calls map to Odoo CRM phonecall records. Call duration, disposition, and timestamp migrate to the corresponding Odoo fields. Odoo stores phone calls as crm.phonecall model records. If the customer has installed the VoIP module, call records link to the phonecall model. Activity ordering is preserved by setting the creation date to the original Nimble timestamp.

Nimble calendar events map to Odoo Calendar Event records. Start datetime, end datetime, location, and attendee list migrate. Odoo Event records link to the related Partner (Contact or Company) via the opporunity_id field or partner_ids many2many field. Recurring events require separate records per occurrence in Odoo since Odoo's native recurrence model is configured via the recurrence field on individual events.

Nimble Tasks export via CSV due to the API lacking Task CRUD. CSV exports are chunked at Nimble's 500-record ceiling per file. Tasks map to Odoo Project Task records if Project management is installed, or to CRM Activity (mail.activity) records otherwise. Task status, priority, due date, and description migrate. The chunking process requires deduplication across multiple export batches before Odoo import.

Nimble notes map to Odoo mail.message records with note subtype. Note body migrates as HTML content. Notes linked to a specific Contact or Deal in Nimble link to the corresponding Odoo Contact or Opportunity record via res_id and model fields. Timestamps are preserved for activity timeline ordering.

Nimble custom fields on Contacts and Companies export via CSV alongside their parent records. We pre-create the corresponding custom fields in Odoo using Odoo Studio (for simple field types) or the ORM for relational fields before migration. Field types (text, picklist, date, boolean) map to the closest Odoo field type. Picklist values require Odoo Selection field value lists to be defined before import.

Nimble Tags are flat labels associated with Contacts. They map to Odoo CRM Tags, which are stored in the crm.tag model and linked via a many2many field on Contact and Opportunity. Multi-value tag associations from Nimble map directly to Odoo's tag assignment. We export all tags per contact during the CSV export phase and create Odoo tags dynamically during import if they do not already exist.

Nimble Segments are saved dynamic filters, not standalone exportable objects. We export the constituent Contacts for each segment rather than the segment definition, and create corresponding Odoo static Groups (crm.group) containing those contacts. The customer's admin rebuilds the dynamic filter logic using Odoo's domain-based filters post-migration.

Nimble Workflow definitions (kanban-based trigger-action automations) have no API endpoint and no CSV export path. They cannot migrate. We conduct a Workflow audit during discovery, documenting each workflow's trigger conditions, filters, and action sequence, and deliver a written playbook mapping each Nimble Workflow to its recommended Odoo Studio action or server action equivalent for manual rebuild by the customer's admin.

Nimble outreach sequences (multi-step email cadences with delays and templates) exist only within the platform and have no export mechanism. We document the sequence structure including step order, delay lengths, email templates referenced, and enrollment criteria during the scoping call and deliver a written sequence inventory for manual rebuild in Odoo Email Marketing or a third-party sales engagement tool.