Migrate from Cliniko to Odoo CRM

Cliniko patients map to Odoo crm.lead records backed by res.partner contacts. Name, email, phone, and address map directly. Insurance profiles, patient forms, and practitioner assignments store as custom fields on the lead. Each patient in Cliniko may have multiple practitioners — all assignments preserved as a multi-line custom field on the lead record.

Individual Cliniko appointments map to crm.lead records. The appointment date becomes expected_revenue on the lead. Appointment type maps to a custom pick-list field (Appointment_Type__c) since Odoo pipeline stages are sales-oriented, not scheduling-oriented. Each appointment creates one lead — multiple appointments for the same patient create multiple leads unless your team specifies a merge rule.

Cliniko appointment types (Initial Consultation, Follow-up, etc.) do not have a native Odoo equivalent. We create a custom Appointment_Type__c pick-list field on crm.lead and optionally map the most common types to crm.stage names if your team wants Kanban view by appointment type. Stages must be created manually in Odoo Settings > CRM > Stages before migration.

Cliniko practitioners resolve to Odoo users by email match. Practitioner specialty, working hours, and appointment-type associations do not have Odoo equivalents — these store as custom fields on the user record or on the crm.lead as Practitioner__c. Unmatched practitioners are flagged before migration; your admin assigns them to an Odoo user or creates a placeholder user.

Cliniko treatment notes migrate as crm.activity records linked to the crm.lead, with the note body stored in the activity description field. Rich-text formatting is stripped — plain text transfers. Very long notes may need splitting across multiple activity records if they exceed Odoo's activity description character limit. A summary also stores in a custom field Lead_Treatment_Summary__c for quick reference.

Cliniko invoices store as custom fields on crm.lead (Invoice_Number__c, Total_Amount__c, Payment_Status__c) for reference. The actual invoice records require Odoo Accounting — if your clinic needs full billing in Odoo, install the Accounting app post-migration and reconcile Cliniko invoices as Odoo vendor bills manually or via a follow-on engagement. Odoo CRM alone does not handle invoicing.

Cliniko billable items (treatment types, products sold) map to Odoo product.template records. Product name, sale price, and cost map directly. Stock quantities in Cliniko require the Odoo Inventory app to be enabled — inventory tracking is handled separately post-migration if needed.

Cliniko SMS and communication logs stored per patient migrate as crm.activity records with Type=Other and the message content in the description field. Odoo's native SMS integration requires the Odoo Marketing SMS app — communications carry over as plain text records without native SMS reply tracking.

Cliniko insurance provider records are linked to patients but Odoo has no native insurance carrier object. We create Insurance_Provider__c and Insurance_Policy_Number__c custom fields on crm.lead. If the clinic manages many insurance carriers, we can optionally map them to res.partner records (company type = Insurance) and link via a many2one field, but this requires Odoo Enterprise for custom relationship fields.

Cliniko patient forms and intake documents have no Odoo native equivalent. Form data and completed intake answers migrate as crm.activity descriptions or as PDF attachments stored on the crm.lead's attachment list. The form structure itself must be rebuilt in Odoo Studio or via a third-party form integration if electronic intake is needed post-migration.