Migrate from Composity CRM to Odoo CRM

Composity Accounts map to Odoo Contact records with the is_company=True flag set. The account name becomes the Contact's name (displayed as the company name), and billing and shipping addresses map to separate Address records on the Contact. Industry, status, and custom properties from Composity map to custom fields on the Odoo Contact. The account's Composity ID is preserved in a custom reference field for reconciliation.

Composity Contacts linked to Accounts map to Odoo individual Contact records with parent_id pointing to the mapped Account Contact. Name, email, phone, role, and custom contact fields transfer directly. Role data from Composity (e.g., decision-maker, influencer, technical buyer) maps to a custom field in Odoo since Odoo's base Contact does not have a native role property.

Composity Leads from the Campaign & Lead Management module map to Odoo CRM Lead records. Lead status, source, qualification score, and custom fields transfer. The Composity lead-to-opportunity conversion history is preserved as notes on the Lead record since Odoo does not natively store conversion event logs.

Composity Opportunities map to Odoo CRM Opportunity (crm.lead with type=pipeline). Deal name, value, expected close date, and stage migrate directly. Stage names from Composity (which are user-defined per organization) require explicit mapping to Odoo stage names; we extract the full Composity stage definition during discovery and configure Odoo stages to match the customer's pipeline before migration.

Composity's user-defined pipeline stages (name, order, win/loss flags, probability percentages) are exported as a stage definition table and recreated as Odoo CRM Stage records. Each stage gets its sequence order, name, and a probability percentage. Stages marked as won or lost in Composity map to Odoo's lost_reason or won_status fields if the customer has configured those in their Odoo instance.

Composity Quotes map to Odoo Sale Order records in draft/quotation state. Header fields (customer reference, date, validity, payment terms) transfer directly. Line items map to Sale Order Lines with product, quantity, unit price, taxes, and discounts preserved. Quote PDF attachments migrate as Odoo IrAttachment records linked to the Sale Order.

Confirmed Composity Sales Orders map to Odoo Sale Orders in confirmed (sales order) state. If Composity tracks order fulfillment status, those states map to Odoo's delivery status fields (picking_ids, move_ids) if the Inventory app is active. For CRM-only Odoo destinations without Inventory, delivery status fields are set to delivered.

Composity Invoices map to Odoo Account Invoice records. Invoice headers (number, date, partner, payment terms) and line items transfer directly. Tax codes map to Odoo tax accounts. Partially paid or overdue invoices carry their residual balance and payment state into Odoo; the customer reconciles open balances in Odoo's Accounting app post-migration.

Composity Product catalog entries map to Odoo Product records (product.product or product.template depending on variant structure). SKU, name, description, list price, and cost price transfer. If Composity has product categories, those map to Odoo Product Category records to preserve categorization hierarchy.

Composity Users map to Odoo ResUsers records resolved by email address match. Active status, name, and login email transfer. Role and permission structures in Composity (which are simplified compared to Odoo's access rights model) are documented as a written role matrix for the customer's Odoo admin to configure access groups post-migration.

Composity activity records (calls, emails, meetings, tasks, notes) linked to Contacts and Accounts map to Odoo Mail Activity records. Activity type, date, description, and the linked res_model/res_id reference transfer. Meeting and call details (duration, location, attendee list) map to Odoo activity fields or custom fields depending on the Odoo apps installed.

Composity Document Storage files are exported individually (Composity has no bulk download) and reattached to their corresponding Odoo records (Contact, Account, Opportunity, Sale Order) using filename and metadata matching. We build a file inventory during discovery, download files in parallel batches, and attach them to the matching Odoo record by traversing the Composity document-to-record linkage.

Composity Production module records (production orders, BOM references) have no native Odoo CRM equivalent. Odoo's Manufacturing app handles production but is a separate ERP-level module outside base CRM scope. We scope this during discovery: if the customer wants production data preserved, we design a custom object or use Odoo Project to store production records, BOM references, and status. This requires explicit schema design and is not a standard field-to-field migration.

Composity Custom Data module fields applied to any object are reverse-engineered during discovery. We generate Odoo custom fields (ir.model.fields with custom=True) of equivalent type (char, selection, float, date, many2one) and apply them to the target Odoo model before the relevant object migration phase runs.