Migrate from PipelineManager to Odoo CRM

PipelineManager Pipelines map to Odoo Sales Teams (crm.team) for pipeline-level segmentation and to Stage configurations within the CRM Settings. Each PipelineManager Pipeline name becomes an Odoo Sales Team; the ordered Stages within each Pipeline become Odoo Stage records with sequence numbers preserved. Odoo's single-sales-pipeline constraint means multi-pipeline PipelineManager accounts require Sales Teams or stage prefixes to maintain visual separation. We flag this during discovery and configure before migration.

PipelineManager Deals map directly to Odoo crm.lead records. Deal name becomes crm.lead name; deal value maps to planned_revenue; deal stage maps to stage_id with the Odoo Stage resolved from the parent Pipeline mapping. Owner assignment (PipelineManager deal owner) resolves to Odoo res.users by email match. Closed-Lost and Closed-Won dates migrate as date_closed. Lost reason custom properties map to Odoo's lost_reason text field.

PipelineManager People records map to Odoo res.partner with type='contact'. Name, email, phone, mobile, and address fields migrate directly. Custom properties on People map to custom res.partner fields created in Odoo Studio before migration. Partner records are created before Deal import so that the partner_id lookup on crm.lead is satisfied at import time.

PipelineManager Company records map to Odoo res.partner with type='company' and is_company=True. Company name becomes the partner name; address fields map to street, city, state, zip, country. Any custom fields on the PipelineManager Company object migrate to custom res.partner fields. PipelineManager's People-Company association migrates as Odoo's child partner links (res.partner with parent_id pointing to the company partner).

PipelineManager Deals are associated with Companies (accounts). We resolve the PipelineManager Company ID at migration time to find the migrated res.partner record and set it as the crm.lead partner_id. If a Deal has no Company association in PipelineManager, the crm.lead partner_id is left null; the Odoo CRM kanban view shows these as unassigned leads.

PipelineManager Deals can have associated People (contacts) beyond the primary Company link. We resolve each PipelineManager Person ID to the migrated res.partner record and set it as crm.lead contact_id. Multiple contact associations beyond the primary are logged in crm.lead description or a dedicated notes field for the customer's admin to resolve post-migration.

PipelineManager call Activities migrate to Odoo crm.activity records linked to the parent crm.lead or res.partner. Call duration, disposition, and timestamp migrate to custom activity fields. Odoo's phone call activity subtype provides a call log structure; we set the activity type and preserve the original PipelineManager timestamp in the activity_date field.

PipelineManager email Activities migrate to Odoo mail.message records linked to the parent crm.lead or res.partner via mail.thread. Email body and subject migrate to mail.message body and subject fields; sender and recipient email addresses map to email_from and email_to. Odoo's mail.message provides the chatter thread on both leads and partner records.

PipelineManager Note Activities migrate to Odoo mail.message with subtype='comment' or a dedicated note subtype on the crm.lead. Note body migrates as HTML-formatted message content. Notes are linked to the parent crm.lead or res.partner via the mail.thread model and res_id references.

PipelineManager meeting Activities migrate to Odoo calendar.event records. Meeting title, start and end datetime, location, and attendee list migrate to the equivalent calendar.event fields. Attendees link to res.partner records via calendar.attendee. The calendar.event is linked to the parent crm.lead via a custom Many2one field or the event description for context.

PipelineManager task Activities migrate to Odoo crm.activity records with activity_type_id set to the Odoo standard Task type. Task title, due date, priority, and completion status migrate to the equivalent crm.activity fields. Owner assignment resolves via email match to res.users. Completed status sets the activity as done in Odoo.

PipelineManager file attachments migrate as Odoo ir.attachment records. Files transfer in their original format with filename and content preserved. Each attachment is linked to the corresponding crm.lead, res.partner, or calendar.event record via res_model and res_id. Odoo's document management stores attachments in the database (cloud) or filesystem (on-premise) depending on Odoo hosting configuration.

PipelineManager Users referenced as deal owners map to Odoo res.users by email address. We extract every distinct owner across Deals and Activities during discovery and match by email. Any PipelineManager User without a matching Odoo res.users record goes to a reconciliation queue for the customer's admin to provision before migration resumes. Inactive PipelineManager owners map to inactive Odoo users by default.

PipelineManager custom fields on Deals migrate to Odoo custom fields on crm.lead, created via Odoo Studio or direct field definition before migration. Field types are mapped: text to char or text, number to float or integer, date to date, checkbox to boolean, dropdown to selection. Custom field labels are preserved in the Odoo field string attribute.

PipelineManager custom fields on People migrate to Odoo custom fields on res.partner. Same type-mapping logic applies as for Deal custom fields. The customer's admin chooses whether custom fields appear on contact form views via Odoo Studio after migration.

PipelineManager custom fields on Companies migrate to Odoo custom fields on res.partner records where is_company=True. Type mapping follows the same rules as People custom properties. Fields are available on both company-type partner records and child contact records depending on Odoo view configuration.