Migrate from Cirqll to Odoo CRM

Cirqll Customer records map directly to Odoo res.partner. The name, email, phone, and address fields transfer with type mapping: Cirqll's single address block maps to Odoo's street, street2, city, state_id, zip, and country_id multi-field address model, which requires address normalization during the transform step. Customer Create API endpoint (the only fully documented Cirqll endpoint) drives the initial field map, and we validate against probe reads for any undocumented fields present in actual data.

Cirqll Lead records map to Odoo crm.lead. The lead's qualification status, source attribution, and owner assignment transfer as crm.lead stage_id, source_id, and user_id respectively. Odoo CRM's crm.lead model serves both unqualified leads and qualified opportunities in the same record; we use stage_id values to represent the Cirqll Lead lifecycle. Lead-to-Customer conversion history is preserved as a linked note or activity on the crm.lead record.

Cirqll Task records map to Odoo project.task. Due date, assignee (resolved via res.users email match), priority flag, and completion status transfer directly. Open and completed task states carry forward; Odoo's project.task.stage_id maps from Cirqll's task status, and date_deadline maps from due date. If the customer's Odoo instance does not activate the Project module, we configure crm.lead activity_ids for lightweight task tracking instead.

Cirqll Activity records (calls, emails, meetings) map to Odoo crm.activity records attached to crm.lead. Activity type, timestamp, owner attribution, duration, and related Contact or Lead migrate with the parent crm.lead ID resolved before activity insert. Odoo's crm.activity model uses activity_type_id to categorize as call, meeting, email, or other, which we map from Cirqll's activity type field. ActivityDate ordering preserves the original Cirqll timestamp for timeline fidelity.

Cirqll Notes attached to Contacts or Leads migrate to Odoo note.note records. Creation timestamp and author attribution transfer. We link note.note to the corresponding crm.lead or res.partner using res_id and res_model so that the note remains contextually attached to the right record in Odoo's activity and note streams. Rich text formatting in Cirqll notes is preserved where present in the API response.

Cirqll Calendar Events map to Odoo calendar.event with date, time, title, and attendee list. All-day event flags and recurrence patterns require field-level mapping because Cirqll's single-field date representation differs from Odoo's allday boolean and recurring_event_id split. If Cirqll exports recurrence patterns as text strings, we parse them into Odoo's calendar.recurrence model during the transform phase. Attendee list maps to calendar.attendee records linked to the event.

Documents stored in Cirqll are binary blobs that do not export via the standard API endpoints. We handle document migration as a secondary pass: we download documents from Cirqll in a staged workflow, preserving original filenames and upload timestamps, then re-upload to Odoo ir.attachment records linked to the corresponding res.partner, crm.lead, or project.task. Version history does not transfer. Teams should verify their Odoo plan's attachment storage limit before assuming full parity.

Cirqll User accounts and their assignment to Leads, Tasks, and Activities migrate as owner mappings in Odoo. We resolve Cirqll owner records by email match against the Odoo res.users table. Any Cirqll User without a matching Odoo User goes to a reconciliation queue for the customer to provision before record import resumes. Active versus inactive status carries forward from Cirqll; role-based permissions do not transfer because Odoo's access control groups are destination-specific.

Cirqll Lead stages map to Odoo crm.stage records within the crm.lead model. Stage names and order transfer, and probability percentages map to Odoo's stage_probability field if present in Cirqll's export. We create the crm.stage records before importing any crm.lead data so that stage_id references resolve at insert time.

Cirqll Lead source attribution (campaign, referral, web form, etc.) maps to Odoo's utm.source model, which is the standard attribution taxonomy in Odoo CRM. We create the utm.source and utm.campaign records during the schema phase, then reference them by name during crm.lead import. If Cirqll uses a custom source taxonomy, we create matching utm.source records in Odoo before migration.

Cirqll does not expose a sales team object via its API, but team-based assignment can be inferred from owner groupings on Lead records. We map each distinct Cirqll owner group to an Odoo crm.team during schema design, then assign crm.lead records to the appropriate team based on the original owner's team association. Team members map to crm.team.member_ids from the res.users table.

Cirqll tags applied to Customers, Leads, or Tasks migrate to Odoo crm.tag records. Tags used for classification map to the crm.tag model and linked via crm.lead.tag_ids (many2many) on the opportunity record. If Cirqll stores tags as free-text labels not exposed in the API, we extract them from record-level text fields during the data audit phase and create matching Odoo tags before migration.