Migrate from Ploomes CRM to Odoo CRM

Ploomes Companies map to Odoo res.partner records with is_company=True. The Company Name maps to partner name, and the CNPJ/CPF field on Ploomes Company maps to the l10n_br CNPJ field (l10n_br.cnpj_cpf) on res.partner. State registration and municipal registration map to l10n_br.inscr_est and l10n_br.inscr_mun. Company address fields (street, city, state, zip) map to street, city, state_id, and zip on res.partner. We create parent partner records before importing child Contact records so that the parent_id reference is satisfied at insert time.

Ploomes Contacts map to Odoo res.partner records with is_company=False and parent_id pointing to the mapped Company partner. When multiple Ploomes Contacts share the same Company, they become child partner records under the same parent_id. Contact name maps to partner name, email to email, phone to phone, mobile to mobile, job_title to function, and any CNPJ/CPF on the individual contact maps to l10n_br.cnpj_cpf on the child partner. Tags from Ploomes map to res.partner.category_id (a many2many tag relationship).

Ploomes Deals map to Odoo crm.lead records. The deal title maps to name, deal value maps to planned_revenue, stage maps to stage_id (an Odoo crm.stage record we configure before migration), and owner maps to user_id. Ploomes Deal custom fields migrate to crm.lead custom fields (x_*) that we pre-create via Odoo XML-RPC before migration. Lost reason and Won reason from Ploomes custom fields map to lost_reason on crm.lead.

Each Ploomes Pipeline Stage maps to an Odoo crm.stage record within a sales team. Stage probability percentages from Ploomes migrate to Odoo stage probability (proba). Stage order and name are preserved. We configure the Odoo Sales Team (crm.team) to correspond to the Ploomes Pipeline before migration, so that stage_id values are scoped to the correct team.

Ploomes Product Groups map to Odoo product.category records. The group name maps to complete_name on product.category, preserving the hierarchical parent category structure if Ploomes has nested groups.

Ploomes Products map to Odoo product.product records linked to product.template. Product name maps to product.template name, SKU maps to product.product default_code, and unit price maps to list_price. If Ploomes has product variants (Parts under Groups), we create product.template with product.attribute and product.attribute.value lines in Odoo to represent the variant hierarchy. Product category from Ploomes maps to categ_id pointing to the mapped product.category.

Ploomes Quotes map to Odoo sale.order records. Quote status (draft, sent, approved) maps to state (draft, sent, sale). Quote line items with product references map to sale.order.line with product_id resolved from the product migration. Discount percentages and totals preserve. The Quote linked Deal in Ploomes maps to an Odoo crm.lead on the sale.order (x_studio_lead_id custom field we pre-create). Approval status from Ploomes Quote maps to a custom approval state field on sale.order.

Ploomes Orders map to Odoo sale.order (if the team uses Odoo Sales without inventory), stock.picking (if Odoo Inventory is activated), or account.move (if Odoo Accounting is activated and the order is billed). We determine the correct Odoo object during scoping based on which Odoo modules the customer activates. The mapping preserves order line items, totals, and the link to the originating Quote and Deal.

Ploomes Tasks linked to Deals map to Odoo crm.lead activity records (mail.message with calendar.event) if the team uses CRM-only in Odoo. Tasks linked to Projects map to project.task if the team activates Odoo Project. Task title, due date, owner, completion status, and task type migrate. Task type maps to activity_type_id in Odoo's activity system.

Ploomes Tags applied to Contacts and Companies map to res.partner.category (many2many). Ploomes Tags applied to Deals map to crm.tag. We pre-create all unique tag names as category or tag records in Odoo before importing associations. The customer chooses during scoping whether to consolidate to a single tag taxonomy or preserve the object-specific tag structure.

Ploomes custom fields created via POST /Fields migrate to Odoo custom fields on the corresponding model (crm.lead, res.partner, product.product, sale.order). We use Odoo XML-RPC to create x_ prefixed fields with matching field types (char, integer, float, boolean, selection, many2one, text). Multi-select and date custom fields map to Odoo selection and date field types respectively. Custom field definitions are created before any data import so that field values can be written during the data migration phase.

Ploomes Users map to Odoo res.users records. We resolve users by email match. Any Ploomes User without a matching Odoo user goes to a reconciliation queue for the customer's admin to provision before record import resumes. Odoo requires active users for Owner assignment on crm.lead; we flag any owner mapping that points to an inactive or missing Odoo user before migration.