Migrate from Cliniko to Salesforce Sales Cloud

Cliniko patients map directly to Salesforce Contacts. Every Contact in Salesforce requires an AccountId lookup — FlitStack creates or matches a Salesforce Account for each Cliniko patient based on the business or clinic location the patient is associated with. Unassigned patients receive a default 'Unassigned' Account record.

Cliniko businesses and locations map to Salesforce Accounts. Cliniko's flat structure stores location address and business details without a parent-company hierarchy — FlitStack creates each Cliniko business as a separate Account using the business name and address fields. Parent-account hierarchies from Cliniko's multi-location setup map to Salesforce ParentId on Account.

Salesforce has no native appointment object — appointments from Cliniko migrate as a custom Appointment__c object. The custom object requires fields for appointment type, practitioner, status, start and end times, notes, and a ContactId lookup to the patient. A lookup to the Appointment_Type__c custom object links each appointment to its service definition. Original Cliniko create timestamps are preserved as a custom datetime field.

Cliniko appointment types are reusable service definitions (name, duration, colour, billing item). Salesforce has no native equivalent — these become a custom Appointment_Type__c object. Fields include name, duration_in_minutes__c, colour__c, and a billing item lookup. This custom object is referenced by every Appointment__c record so service definitions persist without duplication.

Cliniko practitioners are clinical staff with name, profession, qualifications, and business associations. Salesforce has no native practitioner entity. FlitStack creates a custom Practitioner__c object with name, profession__c, registration_number__c, qualifications__c, and an AccountId lookup to the primary clinic location. If the practitioner also uses Salesforce as a CRM user, FlitStack matches them by email and links Practitioner__c to the User record.

Cliniko invoices store line items, total amount, payment status, and tax with direct patient linkage. Salesforce standard objects do not include an invoice entity — invoices migrate as a custom Invoice__c object with ContactId and AccountId lookups, total_amount__c, payment_status__c, date_issued__c, and date_paid__c. Payment status pick-list values are mapped value-by-value from Cliniko.

Cliniko products (supplements, equipment, consumables) map to Salesforce Product2 standard objects. Product name, description, unit_cost, and stock_on_hand transfer directly. Active flag and product code map to Product2.IsActive and ProductCode respectively. Stock levels migrate as a custom field since Product2 does not natively track inventory.

Cliniko file attachments on patient records are downloaded, re-uploaded to Salesforce Files (ContentDocument), and linked to the target Contact via ContentDocumentLink. Salesforce Files attached to a Contact appear in the 'Files' related list. Inline images in Cliniko notes are extracted and hosted as Salesforce Files. File size limits of 25MB per file apply in Salesforce.

Cliniko insurance profiles store per-patient Medicare number, health fund details, and EPC (Enhanced Primary Care) plan information. Salesforce has no native insurance or EPC field — these are created as custom fields on the Contact object: Medicare_Number__c, Health_Fund__c, EPC_Expiry__c, and Insurance_Provider__c. Patients with multiple insurance providers are stored as semicolon-separated values or in a custom junction object.

Cliniko treatment notes migrate as Salesforce Notes (Note) or enhanced ContentNote objects attached to the Contact record. Original Cliniko note creation timestamps are preserved. Rich-text formatting in Cliniko notes is preserved where possible, though complex formatting may be simplified. The note body references the appointment and practitioner where available.