Migrate from NextCRM to Odoo CRM

NextCRM Contact records map directly to Odoo res.partner. Odoo distinguishes between contact type (contact vs company) and address type (invoice, delivery, other). We infer company vs individual from NextCRM's contact type field and set partner_type accordingly. Email, phone, and address fields map by field name. Custom field values on NextCRM contacts migrate to Odoo ir.model.fields custom columns on res.partner.

NextCRM tags map to Odoo res.partner.category records. Tag assignments on each contact migrate as res.partner.category.rel entries linked to the corresponding partner. We extract the full tag taxonomy from NextCRM and pre-create the category records in Odoo before importing partner-tag associations to avoid orphan references.

NextCRM list membership and Advanced Segmentation rules have two migration paths in Odoo. For static lists, we create res.partner records for all members and add them to a dedicated Odoo crm.tag group. For dynamic segments, we document the source segmentation logic and recommend Odoo Studio filters or a Python domain as the equivalent. Where segmentation logic cannot map 1:1, we note the source rule in the recreation guide.

NextCRM custom field definitions and their values migrate alongside contacts. We create matching Odoo custom fields on res.partner using the appropriate Odoo field type (char, selection, float, boolean, date, text). Field type mapping requires judgment: NextCRM multi-select properties map to Odoo many2many tags or selection picklists depending on cardinality; date fields map to Odoo date. We resolve type mapping during scoping before any data extraction begins.

NextCRM campaign records transfer as Odoo crm.lead records with a campaign tag. Active sends must be paused during migration. We preserve campaign name, audience size, and linked contacts so campaigns can be re-created in Odoo Marketing (if licensed) or documented for manual rebuild. Note that Odoo CRM has no native campaign sending capability; this is a feature gap that customers should evaluate before migration.

NextCRM Owners map to Odoo res.users. We resolve owners by email match against the Odoo user table. Any NextCRM Owner without a matching Odoo user is held in a reconciliation queue for the customer's admin to provision before record import resumes. Odoo requires active users for assignment; we flag any owner mismatch before migration begins.

The NextCRM open-source edition includes invoicing with Invoice, Credit Note, Proforma, and Receipt types. Invoice series, line items, tax amounts, and partner references map to Odoo account.move records. We use Odoo's XML data import format with account.account, res.partner, and product.product lookups resolved before insertion. Invoice state (draft, posted, cancelled) preserves during migration.

NextCRM project records migrate to Odoo project.project. Task assignments and status fields map to Odoo project.task. Project-user assignments map to Odoo res.users project share records. We resolve Odoo user IDs from NextCRM owner references before inserting task assignments.

Document metadata and file references migrate to Odoo ir.attachment records linked to the parent record (res.partner or project.task). Actual file storage depends on whether documents are hosted within the NextCRM open-source instance or linked externally. We migrate file metadata and URL references; the customer's admin configures document storage (local vs external) at the Odoo destination.

NextCRM Visual Automation Builder workflows do not export. We extract the trigger conditions, action steps, delay rules, and branch logic from each workflow and deliver a written recreation guide mapped to Odoo Studio automation or Python server action equivalents. The customer's admin rebuilds these in Odoo Studio post-migration. Active campaigns in NextCRM continue running during cutover to allow a parallel-run phase before decommissioning.

Email sequences and follow-up automations are tied to the NextCRM Visual Automation Builder and do not export. We document sequence logic (trigger, steps, delay, condition) for manual rebuild. If the customer licenses Odoo Marketing, the rebuild maps to mailing tracks and marketing automation flows. Without Odoo Marketing, the rebuild maps to Odoo Studio automation or a third-party sales engagement tool.

NextCRM engagement records split by type: email lands as Odoo mail.message linked to the res.partner record; call and task engagements land as project.task with subtype set; meeting engagements land as calendar.event. We preserve activity timestamps and owner assignments by resolving Odoo res.users IDs from NextCRM owner references. Engagement metadata (call duration, disposition, recording URL) migrates to custom fields on the target Odoo record.