Migrate from Pipeliner CRM to Odoo CRM

Pipeliner Accounts map to Odoo res.partner records with is_company=True and customer_rank > 0. The Pipeliner Account name becomes partner name, website maps to the website field, and industry classification maps to Odoo's industry_id field via the res.partner.industry model. We create Partner records before any Contact import so that Contact-to-Account lookups resolve at insert time. Dedupe is by Account name and domain.

Pipeliner Contacts map to Odoo res.partner with is_company=False and parent_id pointing to the company-type Partner representing the associated Account. Email, phone, job_title, and department migrate directly. The Contact's Pipeliner Account association resolves to parent_id during the transform. If a Contact has no associated Account in Pipeliner, it is created as an individual Partner without a parent.

Pipeliner Leads map to Odoo crm.lead records with type='lead'. The lead_name, contact_name, email_from, phone, and street address fields migrate directly. We preserve the Pipeliner lead_status as a custom field (pipeliner_lead_status__c) since Odoo's default stage model differs. Any Pipeliner Lead linked to a converted Account or Contact is flagged for manual review of the Odoo conversion process post-migration.

Pipeliner Opportunities map to Odoo crm.lead with type='opportunity'. The Pipeliner opportunity value becomes Odoo's expected_revenue field. We map Pipeliner pipeline stages to Odoo stage_id within the relevant crm.team. The Pipeliner opportunity-to-account and opportunity-to-contact associations map to Odoo's partner_id (Contact) and partner_id.parent_id (Account) fields respectively, requiring the Contact/Account import to complete before Opportunity insert.

Pipeliner Quotes map to Odoo sale.order records in draft state. The quote linked opportunity becomes the order's opportunity_id (crm.lead reference). Line items map to sale.order.line with product_id resolved to Odoo product.product. We do not migrate Quote PDFs as Odoo stores these as ir.attachment records; the customer should manually reattach any critical PDF documents from Pipeliner after migration.

Pipeliner Products map to Odoo product.product with corresponding product.template. The Pipeliner SKU maps to product.default_code. Product pricing migrates to Odoo's seller_ids and list_price. If Pipeliner pricing includes quantity-based tiers, we create Odoo pricelist rules per tier. Product categories map to product.category.

Pipeliner Projects map to Odoo project.project if the customer licenses the Project module. Projects with sub-tasks map to project.task with parent_id resolved. If the customer does not license Odoo Project, we document the project data in a CSV deliverable and flag it for manual recreation. Project-linked Opportunities require opportunity import to complete before Project import to resolve the crm.lead reference.

Pipeliner Tasks and Appointments map to Odoo mail.activity records. Activity type maps to Odoo's activity_type_id; subject maps to summary; date fields map to date_deadline. The mail.activity model in Odoo links to res.partner (Contact/Account) via res_id and res_model. We resolve res_model and res_id by matching the Pipeliner parent entity type and ID to the migrated Odoo record.

Pipeliner Notes migrate to Odoo mail.message records attached to the parent record (crm.lead, res.partner, or project.task) via res_id and model. The note body migrates as mail.message body in HTML. Odoo's dedicated note.note model is an alternative if the customer prefers the Notes kanban view; the customer chooses during scoping.

Pipeliner Owner references on every record type resolve to Odoo res.users by email match. Owners without a matching Odoo user go to a reconciliation queue; the customer's Odoo admin provisions missing users before record import resumes. Inactive Odoo users receive imported records via OwnerId assignment but the admin must activate or reassign post-migration.

Pipeliner custom entity types require explicit scoping and per-migration mapping logic. We pre-create the destination schema using Odoo Studio (for custom fields on standard models) or a custom module (for new model creation). Custom entity records with lookups to standard entities (Account, Contact, Opportunity) require those standard records to import first. The customer provides a custom entity data model document during scoping.

Pipeliner pipeline stages map to Odoo crm.stage records within crm.team. Pipeliner allows per-user stage overrides; we normalise to the primary admin-defined pipeline schema and collapse per-user stage variations into the canonical stage set. Probability percentages map to Odoo stage probability fields. If the customer has multiple Pipeliner pipelines, each maps to a separate crm.team in Odoo with its own stage sequence.

Pipeliner Lead status values (New, Contacted, Qualified, Disqualified) map to Odoo crm.stage records with a custom field pipeliner_lead_status__c preserving the original value. Odoo's default lead stages differ from Pipeliner's; we create stage records that match the Pipeliner status labels during schema setup so that reporting continuity is maintained post-migration.

Pipeliner's Buying Center feature maps multi-stakeholder influence relationships within deals. Odoo has no native equivalent. We map Buying Center contacts to res.partner records and document the influence role (Champion, Influencer, Economic Buyer, Decision Maker) in a custom partner field. The customer rebuilds the Buying Center org chart view using Odoo Studio or a third-party org chart module post-migration.