Migrate from PipeRun CRM de Vendas to Odoo CRM

PipeRun Contacts map directly to Odoo CRM Contacts. Name, email, phone, and custom field values migrate 1:1. We extract Contacts first in the migration sequence so that the parent Company lookup is available at load time. Odoo requires an associated Company (partner) record to exist before a Contact can be linked; we handle this via a two-pass approach — Companies first, then Contacts with partner_id resolved to the newly created Company.

PipeRun Companies map to Odoo Partner records of company type. The Company name becomes the Partner name; website, address, and industry fields map from their PipeRun equivalents. Odoo uses a single Partner model for both individuals and organizations, so a Company in PipeRun becomes a Partner with is_company=True. We load Companies before Contacts to satisfy the partner_id foreign-key constraint on Contact.

PipeRun Deals map to Odoo CRM Opportunities. Deal name becomes Opportunity name; deal value (valor) becomes Expected Revenue; owner maps via email to Odoo User. Each Deal's Funnel assignment determines which Odoo Pipeline the Opportunity lands in. Closed-won and closed-lost status migrates with the original stage reason preserved in the Opportunity description or a custom chatter note. Historical stage transitions are logged as internal notes in Odoo chatter.

Each PipeRun Funnel maps to a separate Odoo CRM Pipeline. Odoo supports multiple pipelines within a single database; we configure each as an independent pipeline with its own stage sequence. The pipeline name and stage order come from the PipeRun Funnel definition extracted during discovery. If the customer used only one Funnel in PipeRun, it maps to the default Odoo CRM pipeline.

PipeRun stage names map to Odoo CRM stage names within the corresponding pipeline. Stage probability percentages from PipeRun are set on each stage in Odoo. We preserve the stage order as defined in the source Funnel so that the pipeline visual view in Odoo matches the sales rep's mental model. Stage loss/won flags in Odoo are set based on the destination stage being classified as terminal in PipeRun.

PipeRun Activities (calls, emails, meetings, tasks, notes) map to Odoo CRM Activities. We classify by activity type: call activities from PipeRun become mail.activity records with activity_type_id = Call; email activities become Note activities with email content; meeting activities become calendar.event records linked to the Opportunity or Contact. Activity date and assigned user migrate directly; long free-text notes may be truncated at 2,000 characters per Odoo's default body field limit.

PipeRun Proposals map to Odoo Sale Quotations. Line items become Sale Order Lines; proposal value maps to the order amount. ICP-Brazil e-signature metadata (timestamp, certificate info) migrates as a custom field or attachment. The signed PDF itself migrates as an ir.attachment linked to the Sale Order. Note that Odoo does not include native ICP-Brazil compliant e-signatures; if the customer requires this capability, they must configure a third-party e-sign integration post-migration.

PipeRun Users map to Odoo Users by email address match. We extract all distinct Owner IDs referenced on Deals, Contacts, and Activities and match them to Odoo User records. Any PipeRun Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Odoo Users can be used for historical owner attribution without giving active system access.

PipeRun custom fields on Contacts, Companies, Deals, and Activities map to Odoo custom fields. We create each field in Odoo via Settings > Technical > Custom Fields (or Odoo Studio) before migration, matching the field type: text to char, number to float or integer, dropdown to selection, date to date. Dropdown options must be entered manually in Odoo as selection tuples before data load, since Odoo does not auto-create picklist values from source data.

PipeRun tags on Deals and Contacts map to Odoo CRM tags (crm.tag). We create the tag records in Odoo before migration and assign them to the relevant Contacts, Companies, and Opportunities via tag_ids. If the customer used tags as the primary segmentation method, we recommend preserving them as tags rather than converting to a custom field.

Files and attachments linked to PipeRun Deals or Proposals are batch-downloaded from the web interface and re-associated to the corresponding Odoo records (Opportunity or Sale Order) via ir.attachment with res_model and res_id pointing to the destination record. File naming preserves the original PipeRun file name for traceability.

PipeRun automation rules (ações automáticas) are platform-internal and cannot be exported in a portable format. We do not migrate them. We deliver a written inventory of every active automation rule: its trigger object, conditions, and resulting actions. The customer's Odoo admin rebuilds equivalent logic using Odoo Automated Actions (settings > automation) or server actions in developer mode.