Migrate from Onpipeline to Odoo CRM

Onpipeline Contacts map to Odoo res.partner records with partner_type=contact. Standard fields (name, email, phone, address) migrate directly. Custom fields on Contact are created in Odoo developer mode via XML data file before import. The Contact-to-Company linkage is preserved by creating the Company Partner first, then setting parent_id on the Contact Partner record to the Company Partner.

Onpipeline Company records map to Odoo res.partner with partner_type=company. The company domain from the website field is used as a deduplication key. Multi-contact organizations in Onpipeline all link to the same Company Partner via parent_id relationships. Odoo's commercial partner concept automatically rolls up activity to the company-level Partner for reporting.

Onpipeline Deals map to Odoo crm.lead records with type=opportunity. Deal value maps to Odoo's planned_revenue field. Deal stage maps to a corresponding Odoo stage in the configured sales team pipeline. The Onpipeline Deal probability is written to a custom float field probability_override__c since Odoo calculates stage probability automatically but allows override. The Deal's linked Contact resolves to a Partner record via email lookup, and the linked Company resolves to the parent_id Partner.

Each Onpipeline pipeline with its stages maps to an Odoo Sales Team (crm.team) with corresponding stages. Stage names, probabilities, and sequence order are recreated in Odoo via the CRM pipeline configuration. Onpipeline's pipeline-level stage customization maps to Odoo's team-specific stage sequences. We configure the stages before Deal import so that Deals land in the correct stage on insert.

Onpipeline Events, Tasks, and Notes merge into Odoo's mail.activity and mail.message model. Calendar events map to mail.activity with activity_type_id set to 'meeting' and activity_date_deadline set to the event datetime. Tasks map to mail.activity with activity_type_id='call' or 'to_do'. Notes migrate as mail.message records with message_type='notification' attached to the parent Opportunity or Partner. Owner attribution is preserved by resolving the Onpipeline user email to an Odoo res.users record.

Onpipeline Products map to Odoo product.product records with type=product (for inventory-tracked items) or type=consu (for consumables). SKU maps to default_code. List price, standard cost, and stock quantity migrate directly. If the destination Odoo instance includes Inventory, we write stock quant records to preserve the current inventory level from Onpipeline's product catalog.

Onpipeline Quotes migrate to Odoo sale.order records in state='draft'. Quote line items map to sale.order.line with product_id resolved from the Product mapping, quantity from Onpipeline quantity, and price_unit from the quoted price. The linked Contact resolves to a Partner record, and the linked Deal resolves to a crm.lead opportunity. E-signature status is noted in a custom field but the PDF attachment migrates as an IrAttachment linked to the sale.order.

Onpipeline Invoices migrate as Odoo account.move records with move_type='out_invoice'. Invoice headers, line items, and payment status transfer. Odoo's invoicing lives in the Accounting module, so this import requires the Accounting app to be installed in the destination Odoo instance. Recurring invoice configurations are noted but automated recurring generation requires manual setup in Odoo or an Odoo Studio automation rule.

Onpipeline custom fields on Contacts, Companies, Deals, and Products require Odoo developer mode to be enabled before migration. We create custom fields via Odoo's XML data file mechanism (ir.model.fields with the appropriate model and column characters), matching the Onpipeline field type (char, float, selection, boolean, date, etc.) before any data import runs. Custom field definitions are scoped per object to avoid field name collisions.

Onpipeline Tags migrate to Odoo crm.tag records. Multi-tag assignments per Contact, Company, or Deal are preserved via the crm.lead.res_partner_partner_category_rel many-to-many table. Tags used for deal classification map to crm.tag records linked to crm.lead via crm_lead_tag_rel. The customer selects tag-to-category mapping strategy during scoping.

Onpipeline Users are mapped to Odoo res.users by email. Owner assignments on Deals, Activities, and Notes are resolved by matching the Onpipeline user email to the Odoo user login. Any Onpipeline Owner without a matching Odoo user is flagged in the reconciliation queue and the customer's admin provisions the missing user before record import resumes.

Onpipeline recurring revenue schedules are documented as a written inventory during migration scoping. The subscription metadata (amount, frequency, linked Contact, linked Product) migrates as notes on the associated Partner and Opportunity records. Automated recurring invoice generation in Onpipeline is Advanced-plan-only and does not have a direct Odoo CRM migration path; the customer's admin must configure a recurring model in Odoo Accounting or Odoo Studio post-migration.

Onpipeline Web Form submissions migrate as crm.lead records with lead_type='lead' and the form name stored in a custom source field. The submitted field data maps to standard lead fields or to custom fields created for the form. Form definitions are documented as a written handoff for the customer to recreate in Odoo Website Forms or Odoo Studio.

Onpipeline Calendar Events migrate to Odoo calendar.event records. The event datetime, duration, and location map directly. Attendee assignment links to Partner records via calendar.attendee with partner_id resolved by email lookup. Owner attribution is preserved by setting res_users_id on the event to the matched Odoo user. Onpipeline's user-scoped calendar is consolidated into Odoo's shared calendar model while maintaining per-owner event ownership.