Migrate from Capsule CRM to Odoo CRM

Capsule Organisation Parties map to Odoo Company records (res.partner with company_type = company). Organisation name becomes the Company name field. Website, address, phone, industry, and any Organisation-level custom fields carry forward. We create Companies first so that the company_id lookup is satisfied when Contact records are inserted in the next phase.

Capsule Contact Parties map to Odoo Contact records (res.partner with company_type = individual) linked to a Company via the company_id field. We resolve the parent Organisation by matching on Organisation name or domain. Individual name, email, phone, title, tags, and custom fields carry forward. Any Capsule Contact without a parent Organisation creates a standalone Odoo Contact.

Capsule Opportunities map to Odoo crm.lead with type = opportunity. Pipeline name becomes the Odoo Pipeline name; stage name becomes the Stage value. Probability, expected close date, value, currency, and owner carry forward. Where Capsule Opportunities link to a Party, we carry the partner_id reference after the Company and Contact records are created.

Capsule pipeline stages map to Odoo CRM Stage records. We pre-create Odoo stages matching Capsule stage names and sequence order, and set the probability percentage on each stage to match Capsule. Stage is configured in the destination Odoo database before any Opportunity records are migrated.

Capsule Cases map to Odoo Helpdesk Tickets if the Helpdesk module is activated, or to CRM Tickets otherwise. Status, priority, assignee, description, and linked Party reference carry forward. Case conversation history migrates as mail.message records linked to the Ticket. Custom fields on Cases resolve via the field-definition endpoint before value casting.

Capsule Projects (available on Starter and above) map to Odoo Project. Project name, description, status, and linked Opportunity reference carry forward. We carry the Opportunity mapping via a custom Odoo field so relationship context is preserved after migration. Workflow Automations attached to Projects do not migrate and are documented for Odoo Studio rebuild.

Capsule Milestones within Projects map to Odoo Project Tasks with a milestone flag set. Due dates and completion status migrate. Milestone ordering is preserved via the Odoo Task sequence field. The parent Project is created first so the task hierarchy is satisfied. Project Milestones without a parent Project become standalone Odoo Tasks.

Capsule Tags are flat labels applied to Parties, Opportunities, and Cases. We translate tag names 1:1 into Odoo Tags (project.tags) or evaluate them for multi-select picklist migration. The customer confirms tag strategy during scoping: tag-as-tag versus tag-as-custom-field.

Capsule Users and Owners map to Odoo res.users by email address match. We flag any Capsule Owner without a matching Odoo User in a reconciliation queue. The customer's Odoo admin provisions missing Users before record import begins. Inactive Capsule Owners map to archived Odoo Users with records reassigned to the active Owner.

Capsule Activities (email, call, meeting, note) migrate to Odoo mail.message records linked to the parent Contact, Company, or Opportunity via the res_id and model fields. Activity type maps to the message_type field. Direction (inbound/outbound), timestamp, and body text carry forward. Activity count per record is preserved. Email attachments require separate file extraction and ir.attachment re-upload, scoped separately from the base migration.

Capsule Tasks migrate to Odoo Project Tasks linked to the relevant Contact, Company, or Opportunity via the project_id and partner_id fields. Due date, assignee (via User mapping), status, and description transfer. Completed status maps to the Odoo stage state. Tasks without a linked Party or Opportunity become standalone Odoo Tasks.

Capsule Custom Fields on Parties, Opportunities, and Cases are pre-created as Odoo custom fields via Settings > Technical > Custom Fields before any record migration begins. List-type Capsule fields become Odoo selection fields with options matching Capsule field options fetched from /fields/definitions. Text, date, and numeric fields map to char, date, or float respectively. Tag-based Capsule custom fields require separate field-definition resolution before type casting.