Migrate from NinjaPipe to Odoo CRM

NinjaPipe Contacts map to Odoo CRM Lead (for unqualified prospects) or res.partner (for qualified contacts and companies). We apply a qualification filter during scoping: Contacts with no associated Deals and no recent engagement activity map to CRM.lead; Contacts with Deals or active pipeline history map to res.partner as a Customer. The original NinjaPipe contact fields (email, phone, company, tags, custom fields) migrate as typed fields on crm.lead or res.partner. res.partner inherits the address, category, and bank details fields that Odoo uses across Sales, Accounting, and Inventory.

NinjaPipe Pipelines map to Odoo CRM Pipelines defined as CRM Teams (crm.team) with stage records (crm.stage). Stage names, order, and colours migrate as CRM Stage configuration. Each Pipeline becomes a separate crm.team record in Odoo, enabling team-based pipeline visibility. If the customer uses only one pipeline in NinjaPipe, we map it to the default CRM team in Odoo. Pipeline assignments on Deals resolve to crm.team_id during import.

NinjaPipe Deals map directly to Odoo crm.lead records with type='opportunity'. Deal value, stage assignment, contact association, owner, and custom fields migrate. In Odoo, a crm.lead with type='opportunity' appears in the Pipeline kanban and can generate a Sale Order. Deals without a Pipeline assignment are imported as standalone Opportunities and flagged for manual pipeline assignment post-import. Closed-Lost and Closed-Won status maps to Odoo's Stage probability settings.

NinjaPipe Products (from the disconnected Sales module catalog) map to Odoo product.product records. We extract name, price, description, and SKU. Product records are imported before Sale Orders so that the product_id reference is satisfied. Note that product.pricelist items and product variants (if the customer uses Odoo Inventory) require separate configuration post-import. NinjaPipe's product import is subject to the documented 'execution failure' error in bulk mode; we batch products in groups of 20-50 and log failed batches for retry with sanitized field values.

NinjaPipe Orders (from the disconnected Sales module) are manually created records with no link to CRM Deals. We export Orders as standalone sale.order records in Odoo, optionally linking them to the res.partner customer created from the corresponding NinjaPipe Contact. The customer decides during scoping whether to merge Order data with related Opportunities (creating a sale.order from the crm.lead Opportunity record in Odoo) or to treat Orders as a separate import stream. Unlinked Orders import with a warning flag for manual review.

NinjaPipe Automation Workflows (CRM-scoped only; the Sales module has zero automations) export as rule definitions: trigger type, conditions, and action sequence. We document each workflow in a written handoff with its Odoo Automated Action equivalent. Odoo's Automated Actions (ir.actions.server) use a different model: they trigger on write, create, on-change, or scheduled events and execute Python code or built-in actions. We provide the mapping document; the customer's Odoo admin or Odoo partner rebuilds the triggers in Odoo Studio or via the Automations app. Workflows that reference fields not present in Odoo's crm.lead model require custom field creation before the automated action can be configured.

NinjaPipe Forms capture lead data and route submissions to Contacts or Pipelines. We migrate form definitions (field names, field types, routing configuration) as a documented form map. Submission history migrates as CRM.lead records enriched with form-field data mapped to crm.lead custom fields. The form builder UI itself (one question per page layout) cannot be reproduced in Odoo's Website Form builder; we document the equivalent Odoo form structure and recommend rebuilding the form in Odoo Website or using a third-party form tool integrated via webhook. Submission metadata (submission date, form identifier) is preserved in a custom field.

NinjaPipe Tasks assigned to Contacts or Deals map to Odoo project.task records if the customer uses the Project app, or to CRM Activity records (mail.activity) attached to crm.lead if Odoo Project is not active. Task title, description, due date, status, and owner migrate. Completed versus open status is preserved. Note that Odoo's Activity model (mail.activity) links to crm.lead and res.partner but not directly to project.task without the Project app enabled. We determine the correct target model during scoping based on the customer's Odoo app configuration.

Custom fields defined on NinjaPipe Contacts and Deals are enumerated during discovery and mapped to Odoo ir.model.fields records on crm.lead and res.partner. Field types translate: text to char or text, date to date, number to float or integer, dropdown to selection, checkbox to boolean. Custom fields are created in Odoo via the Settings > Technical > Custom Fields interface before record migration begins. Fields referencing picklist values require the selection options to be defined in Odoo before the field is created.

NinjaPipe Booking Pages (appointment scheduling scoped to contacts or deals) map to Odoo Appointments (calendar.booking) if the customer has the Appointments app enabled. Page settings, availability windows, and booking-to-contact associations migrate as booking slot definitions. If the customer does not license the Appointments app, we migrate the booking page settings as a documented configuration and recommend rebuilding the availability schedule in Odoo Website or a third-party booking tool.

NinjaPipe Invoice records (line items, totals, status, contact association) map to Odoo account.move with type='out_invoice'. Invoice metadata migrates; financial ledger entries (tax, reconciliation, payment state) are recreated in Odoo Accounting post-import. If the customer does not enable the Accounting app, Invoices migrate as sale.order records with a note indicating the original invoice status. We flag during scoping whether the customer has an active Accounting app in the destination Odoo instance.

NinjaPipe Owners (sales reps assigned to Contacts, Deals, and Tasks) map to Odoo res.users records by email match. We resolve each owner reference during import by querying res.users for a matching email address. Owners without a matching Odoo User are held in a reconciliation queue; the customer's admin provisions the missing users before record import resumes. Active versus inactive status on the NinjaPipe owner record is preserved as an active flag on the Odoo res.users record.