Migrate from Cliniko to Twenty CRM

Cliniko's patient maps directly to Twenty's People object. We map firstname, lastname, email, phone, date_of_birth, and address fields. Cliniko-created and Cliniko-updated timestamps are preserved as custom datetime fields since Twenty's native timestamps reflect migration time. Cliniko's patient ID is stored as Source_System_ID__c for delta-run de-duplication.

Cliniko stores addresses as a separate object linked to patients with address types (e.g., 'Street', 'Postal'). Twenty People has a single address field. We take the Cliniko address with type 'Street' (or the first address) and populate Twenty's address field as a single formatted string. Additional address types are stored as custom text fields (e.g., Mailing_Address_2__c) for reference.

Cliniko appointments do not map 1:1 to any Twenty object — Twenty has no appointment entity. We transform appointments to Tasks: the Cliniko appointment date and time become the Task due date and start datetime; the end time becomes the Task end datetime. The Cliniko appointment status ('Awaiting', 'Arrived', 'In Progress', 'Completed', 'No Show') is mapped to a custom Cliniko_Appointment_Status__c field since Twenty Task status has fewer values.

Cliniko appointment types (e.g., 'Initial Consultation', 'Follow-up', 'Massage 60min') have no equivalent in Twenty's standard objects. We create a custom object 'AppointmentType' in Twenty with name and duration fields, then link appointments to it via a relation field. If you prefer a flat structure, appointment types can also become a custom pick-list field on the Task.

Cliniko practitioners are staff members who create appointments and treatment notes. They map to Twenty WorkspaceMembers resolved by email match. We import practitioners first (before appointments and notes) so their Twenty IDs exist for relation resolution. Practitioners without a matching email in Twenty are flagged before migration and assigned to a fallback WorkspaceMember.

Cliniko treatment notes (customizable SOAP-format templates per clinic) migrate as Twenty Notes. The note body content maps to Note.body; the Cliniko treatment note ID is stored as Source_System_ID__c. Note.body is plain text — rich formatting from Cliniko templates is preserved as plain text, and template field labels are included in the body for context.

Cliniko invoices have no equivalent in Twenty's standard object model. We create a custom object 'Invoice' in Twenty with fields for invoice number, total amount, outstanding amount, status, and dates. Invoice status from Cliniko ('Draft', 'Sent', 'Paid', 'Void') maps to a custom pick-list; 'Paid' and 'Void' states are preserved as custom values.

Cliniko invoice line items link products or services to invoices. For simple cases, we store the product name and quantity as custom fields on the Invoice object. For complex invoices with multiple line items, we create a custom object 'InvoiceLineItem' linked to Invoice with product name, quantity, unit price, and total.

Cliniko payments received against invoices have no native equivalent in Twenty. We create a custom object 'Payment' with fields for payment ID, amount, date, and a relation to the corresponding Cliniko-generated Invoice (stored as Source_System_ID__c). Payment status (fully paid, partially paid, refunded) is preserved as a custom field.

Cliniko products and services (used in appointments and invoices) do not have a native equivalent in Twenty. We create a custom object 'Product' with name, description, and unit price fields. Products linked to appointments via the appointment type are also stored as a custom field on the AppointmentType object for traceability.

Cliniko stores insurance provider, member ID, policy number, and concession card details on patient records. Twenty has no native insurance fields. We map these as custom text fields on the People record: Insurance_Provider__c, Insurance_Member_ID__c, Policy_Number__c, Concession_Type__c. This data is preserved for reference but requires manual entry for new patients post-migration.

Cliniko clinics commonly add custom fields to patient records for clinic-specific data (e.g., 'Preferred Contact Method', 'Emergency Contact', 'Referral Source'). Each Cliniko custom field becomes a Twenty custom field with the same name and field type, created in Settings → Data Model before import. Field values are mapped value-by-value during the migration run.

Some Cliniko setups add custom fields to appointments (e.g., 'Room Number', 'Equipment Used'). These map to custom fields on the Task object in Twenty, created before import. Note that custom fields on appointments in Cliniko are stored in a separate export and must be joined to the main appointment export by record ID during mapping.

Cliniko bundles SMS credits and Telehealth session fees into its subscription billing. Twenty CRM has no equivalent billing or communications-credit model. These records do not migrate. If SMS appointment reminders are in use, they must be replaced with Twenty workflow-based reminders or a third-party SMS integration post-migration.