Migrate from PipelinePRO to Odoo CRM

PipelinePRO Contact records export as CSV with name, email, phone, and custom field columns. We map these to Odoo res.partner records with partner_type set to 'contact'. Any PipelinePRO custom fields are pre-created in Odoo as custom fields on res.partner before import. Email address serves as the dedupe key; contacts without email are flagged for review before insertion.

PipelinePRO Company records map to Odoo res.partner with partner_type set to 'company'. Company records are imported first so that Contact imports can satisfy the parent_id foreign key at insertion time. PipelinePRO's inconsistent population of the company field on contacts (a common source of sparse records) is flagged in the scoping report for the customer to review before migration.

PipelinePRO Deals map to Odoo crm.lead records with type set to 'opportunity'. The PipelinePRO deal value maps to Odoo's expected_revenue field; the PipelinePRO pipeline and stage assignment maps to crm.lead.stage_id and the crm.team_id (sales team) which we pre-configure to match the PipelinePRO pipeline structure. Owner assignment migrates by resolving PipelinePRO owner email to Odoo res.users id.

PipelinePRO Lead records function as early-stage contacts with their own status field. We map these to Odoo crm.lead with type set to 'lead' and preserve the PipelinePRO lead status as a custom field or mapped to Odoo's lead_priority and tag_ids. Odoo does not have a separate Lead object; all prospects live in crm.lead with the type field distinguishing Leads from Opportunities.

PipelinePRO's customizable pipeline boards with drag-and-drop stage definitions map to Odoo's crm.team model. Each PipelinePRO pipeline becomes a separate Odoo sales team (crm.team), and the PipelinePRO stage list is applied to the crm.stage model within that team's scope. We extract the PipelinePRO pipeline name and stage count during scoping and recreate the structure in Odoo before any record migration.

PipelinePRO stage names and order are configurable per pipeline. We extract the full stage list (name and sequence) and create corresponding Odoo crm.stage records within each crm.team's pipeline. Stage probability percentages from PipelinePRO custom fields are preserved as stage_probability on crm.stage if the Odoo version supports it, or noted as a manual configuration step.

Tags on PipelinePRO contacts and deals export as comma-separated values in the CSV. We parse these into individual crm.tag records in Odoo and apply them via crm.lead.tag_ids (many2many relation). If the same tag appears on both contacts and deals in PipelinePRO, it creates a single Odoo tag record usable across both object types.

PipelinePRO user accounts with names and email addresses export as a simple list. We resolve each PipelinePRO owner email against the Odoo destination res.users table. Users without a matching Odoo account go to a reconciliation queue for the customer to provision before migration resumes. Reassignment of owned deals and contacts to the correct Odoo user id happens during the deal and contact import phases.

PipelinePRO custom fields exist per object but have no bulk schema export. We ask customers to provide a screenshot or list of custom field names and types during scoping. We pre-create matching Odoo custom fields on res.partner and crm.lead via Settings > Custom Fields or Odoo Studio before any data import. Field types (text, integer, date, selection) are matched to Odoo's field type system. Custom field values migrate as part of the contact and deal CSV import.

Uploaded files attached to PipelinePRO deals or contacts export via download links if accessible within the account. We map these to Odoo ir.attachment records linked via res_model='res.partner' or res_model='crm.lead' and res_id pointing to the migrated record. Any documents we cannot retrieve from PipelinePRO are flagged in the scoping report for manual handling.

PipelinePRO notes attached to contact or deal records (as opposed to activity timeline entries) are static text that we extract from the CSV export. These migrate to Odoo mail.message records with message_type='note' linked to the res.partner or crm.lead record. Full activity history (logged calls, emails, meetings, completed tasks) has no export path and is not migrated; we recommend the customer export a text backup of any critical activity notes before cutover.

Call logs, email history, meeting records, and completed task records in PipelinePRO do not appear in any export mechanism. We cannot migrate activity history. We recommend exporting any critical static notes or call summaries as a text backup before cutover. In Odoo, mail.activity is available post-migration for the team to rebuild task and meeting records manually.