Migrate from Prospect CRM to Odoo CRM

Prospect CRM Contact records map directly to Odoo res.partner with partner_type = 'contact'. Standard fields (name, email, phone, street, city, postcode) migrate as their Odoo equivalents. Custom Contact properties from Prospect CRM (e.g., custom dropdowns, date fields, RFM segment assignment) migrate as custom res.partner fields defined in an Odoo custom module's Python class before import. We preserve any Prospect CRM contact UUID in a custom field x_prospect_id for deduplication on re-migration.

Prospect CRM Company records map to Odoo res.partner with partner_type = 'company' and the is_company flag set True. Company-level custom fields migrate as custom res.partner fields. We create the Company partner record before any linked Contact records to satisfy the child_ids dependency, using the Company name as the dedupe key.

Prospect CRM Deal records map to Odoo crm.lead with type = 'opportunity'. Deal value, stage name, owner, and close date migrate directly. The Prospect CRM pipeline name maps to an Odoo Sales Team (crm.team) which we configure before migration. Custom Deal properties migrate as custom fields on crm.lead via a custom module's Python field definition.

Prospect CRM's custom stage definitions — including non-standard names like 'Quoted', 'Awaiting Stock', or 'Order Placed' — map to Odoo crm.stage records within the designated Sales Team. Stage order, probability percentage, and fold-to-closed flags migrate from Prospect CRM's pipeline stage configuration. We configure these stages in Odoo via crm.stage records before Deals are imported.

Prospect CRM Product catalog records (SKU, name, description, list_price) map to Odoo product.template. The live inventory linkage flag and stock-aware quoting configuration do not migrate as a functional setting — Odoo's inventory module requires separate configuration of warehouse locations and replenishment rules. We document the stock-aware flag value for the customer's Odoo admin to re-establish in Odoo Inventory settings.

Prospect CRM engagement records (calls, emails, meetings, tasks, notes) migrate to Odoo's mail.activity and mail.message (chatter) models. Call engagements map to mail.activity with activity_type_id = 'call'. Emails map to mail.message records with message_type = 'email'. Notes map to mail.message records with message_type = 'comment' attached via a mail.thread relation to the parent crm.lead or res.partner. Each record is linked by the original Prospect CRM timestamp for chronological ordering.

Prospect CRM's Problem Pipelines object is non-standard and has no native Odoo equivalent. Problem records — with Status, Outcome, and linked Customer fields — map to Odoo helpdesk.ticket if the customer's Odoo instance includes the Helpdesk module, or to project.task if a project-based workflow is preferred. We flag this choice during scoping. The customer's admin configures the Ticket type, stage, and team after migration. This is the highest-friction object in this migration pair.

Prospect CRM's Recency, Frequency, Monetary segmentation data is stored as a platform-specific customer classification. We export each Contact's RFM segment assignment and map it to a custom Char field x_rfm_segment on res.partner. Post-migration, the customer's admin uses this property for filtered views and targeted sales campaigns within Odoo's native filtering and group-by capabilities.

Custom fields on Contacts, Companies, and Deals in Prospect CRM migrate as custom fields on Odoo's res.partner and crm.lead models. In Odoo v17+, custom fields require definition in a custom Python module (not a UI-based workflow) before data import can target them. We pre-create the destination custom module with the correct field types — Char, Date, Selection, Float, Integer — matching Prospect CRM's field definitions, then load data against it.

Prospect CRM User records (name, email, role assignment) map to Odoo res.users. We match by email address. Any Prospect CRM user referenced on a Deal, Activity, or Problem record without a matching Odoo user is flagged in a reconciliation queue. The customer's Odoo admin provisions missing users before record migration resumes, as OwnerId-style references in Odoo point to res.users.id.

File attachments on Deals, Contacts, and Problems in Prospect CRM migrate as ir.attachment records linked to the corresponding res.partner or crm.lead record. We flag any attachments exceeding Odoo's default attachment size limit (default 25 MB on Odoo Online; configurable on On-Premise) and document them separately for manual re-upload if required.

Prospect CRM's deep native integrations with back-office systems are connection-level configuration, not data. These links do not export or migrate. We document every active integration during scoping — including the integration type, connected entity, and any required API credentials — and provide a re-connection checklist for the customer's Odoo admin to re-establish each link in the Odoo Apps framework post-migration.