Migrate from Cirrus CRM to Odoo CRM

Cirrus CRM Company records map to Odoo res.partner records with partner_type=company. Company credit information and geographic enrichment (latitude/longitude) from Cirrus CRM map to custom fields on the Partner record. We preserve the original Cirrus CRM company ID as an external identifier field to support future reconciliation. Odoo uses Partner for both companies and contacts; we set type=company on these records and contact records link to their parent company via parent_id.

Cirrus CRM Contact records map to Odoo res.partner records with type=contact and parent_id pointing to the corresponding company Partner. Email, phone, address, and custom field data transfer directly. The Contact-to-Company relationship resolves via the parent_id reference after the Company Partner is created. We validate email uniqueness in Odoo during import and flag duplicates for the customer admin to resolve before committing.

Cirrus CRM Deals map to Odoo crm.lead. We ask the customer during scoping whether they prefer Leads (unqualified prospects) or Opportunities (pipeline deals) as the destination type, as Odoo CRM treats these as stages on the same record with a Convert-to-Opportunity action. Deal monetary value maps to Odoo's planned_revenue field, and the Cirrus CRM deal stage label maps to an Odoo stage within the designated team pipeline.

Cirrus CRM pipeline definitions (stage names, order, win/loss criteria) do not export with deal records. We extract the stage labels from Cirrus CRM deal records during discovery and configure corresponding Odoo CRM stages and teams. If the customer wants pipeline automation triggers migrated, we document the current Cirrus CRM stage-change rules as Odoo Studio actions for the admin to rebuild.

Cirrus CRM Quotes map to Odoo sale.order records in quotation state. Quote line items map to sale.order.line with product reference, quantity, and unit price. Cirrus CRM product-line associations require explicit preservation; we map the Cirrus CRM product reference to Odoo product.product and validate product.active status before linking. If the Cirrus CRM Quote references a Deal, we link the Odoo quotation to the corresponding Odoo crm.lead via opportunity_id.

Cirrus CRM Orders map to Odoo sale.order records with state=done or state=sale (confirmed, pending delivery). The Quote-to-Order chain in Cirrus CRM must map to Odoo's sale.order and the source quotation reference preserved via origin field. Order-to-invoice relationships migrate to Odoo account.move records; we validate that the Odoo accounting module is active before mapping, as invoice records require the Invoicing app.

Cirrus CRM Activities (calls, emails, tasks, meetings) linked to Contact or Deal records map to Odoo mail.activity records. Activity type (call, email, meeting, task) maps to Odoo's activity_type_id, and the original timestamp preserves in activity_date. We link activities to the correct Odoo res.partner or crm.lead via res_id and res_model. Odoo's Activity model requires the CRM app to be installed; we confirm app availability during discovery.

Cirrus CRM Campaign records (objectives, campaign-level metrics) map to Odoo utm.campaign records if the Odoo Marketing app is installed. If only CRM is installed, we attach campaign context as a custom Char field on crm.lead. Individual campaign member associations require the customer to confirm scope during discovery; we do not create campaign member objects unless the Marketing app is in scope.

Cirrus CRM tenant-specific custom fields require field-by-field mapping and type inference validation. We request a screenshot or export of the Cirrus CRM field configuration before migration. Each custom field is pre-created in Odoo via XML or Studio with the correct field type (Char, Text, Integer, Float, Date, Selection, Many2one) validated in a test batch of 50 records before the full import. Multi-select or checkbox custom fields in Cirrus CRM map to Odoo many2many or selection fields depending on the data shape.

Cirrus CRM User records map to Odoo res.users by email address. Owner assignments on Deals, Quotes, and Orders resolve via user_id or user_ids fields in Odoo. We extract every distinct HubSpot Owner or Cirrus CRM assigned user referenced on records and match by email against the Odoo destination instance. Missing users go to a reconciliation queue for the customer admin to provision before record import continues.

Cirrus CRM attachments export as individual files per record (one file per attachment, not bundled). We batch-associate these to the correct Odoo ir.attachment records by filename parsing and provide a manifest mapping each file to its target res_model and res_id. Attachments exceeding 10 MB are flagged for manual handling to avoid Odoo attachment size limits. We link attachments to the correct partner or lead record based on the filename record reference.

Cirrus CRM Deal and Order records may carry live ERP financial data (invoice status, payment history, account balance) from the bidirectional sync layer. We check ERP sync health before extraction and flag any records with timestamps before the last confirmed sync. If sync is healthy, we migrate the financial field values as custom fields on the Odoo record. If sync is broken, we document the stale state and let the customer decide whether to remediate sync or accept the last-known values.