Migrate from Pro-Sales CRM to Odoo CRM

Pro-Sales CRM stores all people records as Contact with a lifecycle stage property (Lead, Qualified, Customer, etc.). Odoo splits these into Lead (unqualified) and Contact (qualified, attached to Company). We evaluate the lifecycle stage on each Contact during migration: early-stage contacts map to Odoo Lead; contacts attached to a company with a closed-won or active deal map to Odoo Contact under the corresponding Company (resPartner). The original lifecycle stage and Pro-Sales CRM contact ID are preserved in custom fields on both the Lead and Contact for reconciliation.

Pro-Sales CRM Company records map directly to Odoo res.partner records with company_type = company. The company name becomes the partner display name, street/city/ country map to address fields, and industry/size map to custom Char fields in Odoo. The Company record is migrated before any child Contacts so the Contact-to-Company partner_id lookup is satisfied at insert time.

Pro-Sales CRM Deals map to Odoo crm.lead records with type = opportunity. The deal name becomes the opportunity name, deal value maps to Odoo's planned_revenue field, and close date maps to date_deadline. We extract the Pro-Sales CRM stage probability percentage and write it to a custom probability field; Odoo's built-in stage_probability is set via the pipeline stage configuration before migration.

Pro-Sales CRM allows custom stage names and per-stage probability weights per pipeline. We extract the active stage configuration from the source account during discovery and create Odoo pipeline stages with matching names and probability percentages before any Opportunity records are imported. If Pro-Sales CRM has multiple pipelines, we create separate Odoo CRM pipelines (sales teams in Odoo) to isolate them.

Pro-Sales CRM custom fields on Contacts and Deals migrate to Odoo custom fields created via Odoo Studio or the fields API before migration. Field types are mapped: text to char, number fields to float or integer, dropdown-style fields to selection fields, and date fields to date. Lookup relationships to other objects in Pro-Sales CRM become Many2one fields in Odoo with a corresponding res.partner or crm.lead record created first.

Pro-Sales CRM activity records (call logs, notes, completed tasks) map to Odoo project.task records for task-type activities or to mail.message records for notes and log entries within the crm.lead discuss thread. We preserve the original timestamp, owner assignment, and activity type by writing to the appropriate Odoo model. Call duration and disposition from Pro-Sales CRM become custom fields on the Odoo task or message record.

Pro-Sales CRM tag assignments on Contact and Deal records map to Odoo crm.tag records with many2many relink via crm.lead.res_partner_all_tags_rel. We deduplicate tag strings during extraction and create the Odoo tag records before linking them to opportunities and leads. Tags used for lead scoring or routing in Pro-Sales CRM are preserved as tag names with the score value migrated to a custom field on the Odoo record.

Pro-Sales CRM assigns a single owner per Contact, Company, and Deal. We extract owner email addresses and match them against the destination Odoo User table. Owners without a matching Odoo User are placed in a reconciliation queue; the customer provisions missing Users before the migration phase begins. Unmapped owner references are reassigned to a designated fallback user nominated during scoping.

Active Pro-Sales CRM user records are migrated as Contacts in Odoo only if the customer does not require them as Odoo system Users. If Odoo system access is required for the migrated users, we provision the res.users records and map their Pro-Sales CRM login email as the Odoo login. Role and permission differences between CRMs mean we apply a closest-fit group assignment rather than a 1:1 permission copy.

Pro-Sales CRM's attachment export path is not documented in the available API references, and we have not confirmed a reliable extraction method for binary file data. We do not migrate attachments as part of standard scope. We flag this to customers during scoping and recommend they export attachments manually via Pro-Sales CRM's UI export function or that the customer requests a data export bundle from Pro-Sales CRM support before migration begins. If a confirmed export path becomes available during discovery, we reassess and migrate attachments as IrAttachment records in Odoo where feasible.

Pro-Sales CRM lifecycle stage values (Lead, Marketing Qualified, Sales Qualified, Customer, etc.) are preserved as a custom field on Odoo crm.lead (for Lead records) and res.partner (for Contact records). We create a selection field with the exact stage values from the source account, defaulting to the stage value currently assigned on each record. This field serves as an audit trail and is used for reporting continuity in Odoo.

Pro-Sales CRM workflow rules, automated assignments, and stage-triggered actions do not have a migratable representation. Odoo Studio offers automation rules and server actions as the equivalent capability, but we do not rebuild them during migration. We deliver a written inventory of every active Pro-Sales CRM automation with its trigger conditions, actions, and recommended Odoo Studio equivalent, and the customer's admin rebuilds them post-migration.