Cliniko to Salesforce migration
Moving from Cliniko to Salesforce Sales Cloud is a model-divergence migration: Cliniko's flat patient-and-appointment schema maps to Salesforce's relational Account-Contact model with custom objects for appointments, practitioners, and invoices. FlitStack AI resolves every lookup dependency, creates Salesforce custom objects for Cliniko's appointment types and practitioners, and preserves original create dates on Contact records so your post-migration reports show accurate patient history from day one.
FlitStack AI migrates contacts, accounts, appointment__cs, appointment_type__cs and practitioner__c or salesforce users from Cliniko to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 Cliniko records.

What moves from Cliniko to Salesforce?
Cliniko is a cloud-based practice management platform designed for healthcare clinics, physiotherapists, and allied health practitioners.
Read the full summary
Its data model stores patients, practitioners, appointments, and financial transactions in a flat, application-centric schema without a relational hierarchy. Salesforce Sales Cloud uses an Account-Contact relationship model: every Contact must have an AccountId lookup, and concepts like practitioners, appointment types, and invoices have no native Salesforce equivalent — they require custom objects with __c suffix fields and lookup relationships. FlitStack AI maps Cliniko patients to Salesforce Contacts (creating or matching Accounts as parent records), converts Cliniko appointments and practitioners to custom Salesforce objects with lookup relationships to Contacts and Accounts, and preserves original Cliniko create timestamps as custom datetime fields. Appointment types become a custom object for re-use across appointments. Invoices migrate as a separate custom object. A delta-pickup window captures any Cliniko records modified between the migration run and go-live. FlitStack does not migrate Cliniko workflows because Cliniko does not offer a workflow or automation export — those must be defined natively in Salesforce.
Patient → Contact
Cliniko patients map directly to Salesforce Contacts.
How it maps
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.
Business / Location → Account
Cliniko businesses and locations map to Salesforce Accounts.
How it maps
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.
Appointment → Appointment__c (custom object)
Salesforce has no native appointment object — appointments from Cliniko migrate as a custom Appointment__c object.
How it maps
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.
Appointment Type → Appointment_Type__c (custom object)
Cliniko appointment types are reusable service definitions (name, duration, colour, billing item).
How it maps
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.
Practitioner → Practitioner__c (custom object) or Salesforce User
Cliniko practitioners are clinical staff with name, profession, qualifications, and business associations.
How it maps
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.
Invoice → Invoice__c (custom object)
Cliniko invoices store line items, total amount, payment status, and tax with direct patient linkage.
How it maps
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.
- PatientContact1:1
- BusinessAccount1:1
- AppointmentAppointment__ctransformed
- Appointment TypeAppointment_Type__ctransformed
- PractitionerPractitioner__c or Salesforce Usertransformed
- InvoiceInvoice__ctransformed
+ 4 more in the mapping below
How Cliniko and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Cliniko | Salesforce |
|---|---|---|
| Core data model | Cliniko uses a flat patient model — patients, practitioners, and appointments are stored as independent entities without a relational hierarchy. | Salesforce requires Contacts to have an AccountId lookup — every patient must be linked to an Account record (clinic or business entity). |
| Practitioners | Cliniko stores practitioner profiles as first-class records with name, profession, qualifications, and business associations. | Salesforce has no native practitioner object — practitioners must be created as Salesforce users, custom Contact records, or a custom Practitioner__c object with lookup fields. |
| Appointment types | Cliniko appointment types are configuration records that define service name, duration, colour, and billing item — reusable across appointments. | Salesforce has no native appointment-type concept — appointment types require a custom Appointment_Type__c object to preserve service definitions and duration. |
| Invoices and billing | Cliniko invoices store line items, amounts, 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 linked to Contact and Account. |
| Pricing model | Cliniko pricing is per-practitioner per month with unlimited patients, appointments, and storage on all plans. | Salesforce pricing is per-user per month with separate line items for products, Data Cloud credits, and storage overages — costs escalate with seat count. |
| File attachments | Cliniko stores file attachments on patient records directly, accessible via the patient profile. | Salesforce Files attach to records via ContentDocumentLink junctions — files must be downloaded from Cliniko and re-uploaded, then linked to the target Contact. |
Cliniko to Salesforce field mapping
The 30 most-used fields of 46 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
first_namePatientFirstNameContact -
last_namePatientLastNameContact -
emailPatientEmailContact -
phonePatientPhoneContact -
mobile_phonePatientMobilePhoneContact
| Cliniko field | Salesforce field | Mapping | Note |
|---|---|---|---|
Patient.first_name | Contact.FirstName | direct | |
Patient.last_name | Contact.LastName | direct | |
Patient.email | Contact.Email | direct | |
Patient.phone | Contact.Phone | direct | |
Patient.mobile_phone | Contact.MobilePhone | direct | |
Patient.home_phone | Contact.HomePhone | direct | |
Patient.address_line_1 | Contact.MailingStreet | direct | |
Patient.address_line_2 | Contact.MailingStreet | transformed | Appended to MailingStreet when both address_line_1 and address_line_2 are present. |
Patient.city | Contact.MailingCity | direct | |
Patient.state | Contact.MailingState | direct | |
Patient.postcode | Contact.MailingPostalCode | direct | |
Patient.country | Contact.MailingCountry | direct | |
Patient.date_of_birth | Contact.Birthdate | direct | |
Patient.sex | Contact.Gender__c | custom_field_required | Salesforce standard Contact has no gender field. A custom pick-list field Gender__c is created. |
Patient.occupation | Contact.Occupation__c | custom_field_required | No standard Salesforce equivalent. Custom text field Occupation__c is created on Contact. |
Patient.notes | Note.Body | direct | |
Patient.created_at | Contact.Original_Create_Date__c | custom_field_required | Salesforce CreatedDate reflects migration time. Original Cliniko create date preserved as custom datetime for reporting continuity. |
Patient.updated_at | Contact.LastModifiedDate | direct | Salesforce LastModifiedDate updated at migration time; original timestamp preserved as Cliniko_Last_Modified__c. |
Patient.cliniko_id | Contact.Source_System_ID__c | custom_field_required | Cliniko internal record ID stored on Contact for traceability and delta-run de-duplication. |
Business.name | Account.Name | direct | |
Business.address_line_1 | Account.BillingStreet | direct | |
Business.city | Account.BillingCity | direct | |
Business.state | Account.BillingState | direct | |
Business.postcode | Account.BillingPostalCode | direct | |
Business.country | Account.BillingCountry | direct | |
Business.phone | Account.Phone | direct | |
Appointment.status | Appointment__c.Status__c | value_mapping | Cliniko appointment statuses (Booked, Arrived, Did Not Arrive, Cancelled, No Charge) map to Salesforce custom pick-list values on Appointment__c.Status__c. |
Appointment.appointment_date | Appointment__c.Start_Time__c | direct | |
Appointment.appointment_end_time | Appointment__c.End_Time__c | direct | |
Appointment.notes | Appointment__c.Notes__c | direct |
What to watch for in a Cliniko to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Cliniko's flat patient model requires AccountId resolution for every Salesforce Contact
Cliniko stores patients as independent records without any business or entity hierarchy.
How we handle it
Salesforce requires every Contact to have an AccountId — a lookup field linking the patient to a parent Account record. For single-location clinics, FlitStack maps all patients to one Salesforce Account representing the clinic. For multi-location setups, each Cliniko business becomes a separate Account, and patients must be routed to the correct AccountId based on their associated Cliniko location. This routing step adds a de-normalisation pass to the migration plan and must be validated before Contacts load, because Salesforce validation rules will reject Contacts without an AccountId.
Appointment types and practitioners require Salesforce custom object creation before data can load
Salesforce has no native equivalent for Cliniko appointment types (reusable service definitions) or practitioners (clinical staff profiles).
How we handle it
These concepts must be modelled as Salesforce custom objects — Appointment_Type__c and Practitioner__c — with __c suffix fields, pick-list definitions, and lookup relationships back to Contact and Account. The Salesforce admin must pre-create these custom objects with the correct field types before FlitStack can load appointment and practitioner records. We deliver a schema setup plan specifying every custom object, field, and lookup relationship so the Salesforce side is schema-ready before validation runs.
Cliniko appointment timestamps use the clinic's configured timezone — Salesforce stores UTC
Cliniko appointment times are stored in the timezone configured for the clinic or practitioner.
How we handle it
Salesforce stores all datetime values in UTC. If a clinic operates in Australia/Melbourne (UTC+10) and appointment times are not timezone-converted at migration, appointments appear shifted by 10 hours in Salesforce reports and the Salesforce calendar. FlitStack reads the Cliniko timezone setting per business/practitioner, converts all appointment start and end times to UTC before inserting into Salesforce, and stores the original Cliniko timezone in a custom field (Appointment_Timezone__c) for audit purposes.
Cliniko treatment note attachments require manual re-upload to Salesforce Files after migration
Cliniko stores file attachments (referral letters, imaging results, intake forms) directly on patient records.
How we handle it
Salesforce Files attach to records via the ContentDocumentLink junction object, which requires a three-step process: download from Cliniko, upload to Salesforce as a ContentVersion/ContentDocument, then insert a ContentDocumentLink record linking the file to the target Contact. This cannot be fully automated across all file types because some Cliniko attachment formats require format validation before Salesforce accepts them. FlitStack migrates all text and PDF attachments automatically; unusual file types are flagged in the migration report for manual review and re-upload.
Cliniko does not support custom objects or workflow exports — no automation migrates
Cliniko's feature set does not include custom object creation or a workflow/automation engine with an exportable definition.
How we handle it
Unlike HubSpot (which has workflows exportable as JSON) or Salesforce (which has Flow XML), Cliniko has no automation layer to migrate. This means there is nothing to rebuild in Salesforce Flow — the practice's operational logic lives in how staff use Cliniko's appointment booking, patient intake forms, and billing screens, not in an exported automation definition. We document the current Cliniko workflows as a process description for the Salesforce admin to use as a rebuild brief.
How the migration runs
Extract Cliniko data and resolve Account-Contact relationships
FlitStack pulls patient records, practitioner profiles, appointment data, invoices, and attachments from Cliniko via the Cliniko API.
What this step covers
A data-quality audit flags missing email addresses, duplicate patients, and patients without a Cliniko business association. For each Cliniko patient, the migration plan assigns the correct Salesforce AccountId based on the Cliniko business the patient is associated with — single-location clinics map to one Account; multi-location setups route each patient to their clinic's Account. This step creates the mapping table that drives the Contact.AccountId lookup at load time.
Create Salesforce custom objects for appointment types, practitioners, and appointments
Before any data loads, FlitStack creates the Salesforce custom objects required by the Cliniko data model: Appointment_Type__c (fields: name, duration_in_minutes__c, colour__c, active__c), Practitioner__c (fields: first_name__c, last_name__c, email__c, profession__c, registration_number__c, qualifications__c, AccountId__c), and Appointment__c (fields: status__c, start_time__c, end_time__c, appointment_date__c, notes__c, ContactId__c lookup, Appointment_Type_Id__c lookup, Practitioner_Id__c lookup, original_create_date__c, source_system_id__c).
What this step covers
The Salesforce admin reviews and approves the custom object schema before data migration begins. FlitStack delivers a package.xml and field definition sheet for deployment.
Run a sample migration with field-level diff
A representative slice of Cliniko data — typically 100–500 records covering patients, practitioners, appointment types, appointments, and invoices — migrates into a Salesforce sandbox first.
What this step covers
FlitStack generates a field-level diff comparing source Cliniko values against the migrated Salesforce values for every mapped field. This diff is reviewed against the object and field mapping plan. Common checks include: AccountId resolution on Contacts is correct, practitioner Practitioner__c records are linked to the right Account, appointment type references resolve correctly, and timestamps are in UTC. No full migration commit occurs until the sample diff is signed off.
Execute full migration with delta-pickup and rollback readiness
The full Cliniko dataset migrates to the production Salesforce org in dependency order: Accounts first (Cliniko businesses), then Contacts (patients with resolved AccountId), then Practitioner__c records, Appointment_Type__c records, and finally Appointment__c records.
What this step covers
A delta-pickup window (24–48 hours) runs immediately after the full migration commits, capturing any Cliniko records created or modified during the cutover window. FlitStack maintains an audit log of every insert, update, and link operation. A rollback script is prepared but held in reserve — one-click rollback is triggered only if post-migration reconciliation identifies critical record-count discrepancies or broken lookup relationships. After go-live, a reconciliation report confirms record counts, null AccountId counts, and unmatched practitioner counts.
Cliniko - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
Cliniko to Salesforce Sales Cloud migrations sit in the lower-to-mid range because Cliniko has a simpler flat data model with fewer custom fields than enterprise CRMs. Pricing scales primarily with patient record count (Contact + Account creation), practitioner record volume (custom Practitioner__c objects), and appointment type complexity (how many custom objects need Salesforce schema setup and validation rules). Multi-location clinics with separate business accounts in Cliniko add mapping complexity since each location maps to a Salesforce Account and requires AccountId resolution on all associated Contacts. Custom appointment-type objects and invoice objects add scope because they require new __c field definitions, lookup relationships, and cross-object validation. Practices using Cliniko's full feature set — patients, appointments, practitioners, invoices, and attachments — fall in the upper range of the pricing band. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Cliniko to Salesforce →Why teams move from Cliniko to Salesforce
- Cliniko is built for solo and small clinic workflows, but its flat data model caps out at multi-location scalability. As the practice grows, Cliniko lacks the record-type, page-layout, and sharing-model controls that Salesforce provides for differentiated team access and reporting across locations.
- Cliniko's per-practitioner pricing model becomes expensive as the team expands. Salesforce's per-seat licensing often works out more cost-effective at scale, particularly when combining Sales Cloud with Service Cloud under a single enterprise contract that covers both front-desk operations and clinical reporting.
- Cliniko's API is functional but limited to basic data retrieval — it does not expose a workflow export, automation definition export, or custom object creation capability. Teams needing to integrate with enterprise BI tools, EHR systems, or custom reporting pipelines find Cliniko's integration surface too narrow for scale.
- Reporting depth in Cliniko caps out at its built-in dashboard — there is no native query builder, no cross-object reporting, and no way to surface pipeline-level analytics across multiple clinic locations in a single view. Salesforce reporting with standard objects and custom objects provides unlimited report types, joined reports, and cross-object filters.
Questions, answered
Cliniko to Salesforce migration questions
How long does a Cliniko to Salesforce Sales Cloud migration take?
A Cliniko to Salesforce migration typically completes in 48–72 hours of clock time for setups with fewer than 50,000 patient records. The longest planning step is creating the Salesforce custom objects for appointment types and practitioners — this schema setup must be done before any data loads. Multi-location clinics with 500,000+ records or complex practitioner-to-location routing extend to 5–7 days. The delta-pickup window (24–48 hours) runs after the full migration commits and adds roughly one day to the overall cutover window.
Will my Cliniko workflows or automations migrate to Salesforce Flow?
No. Cliniko does not have a workflow or automation export capability — it does not offer an automation engine with definable triggers and actions the way Salesforce Flow does. There is nothing to migrate because Cliniko stores operational logic in how staff use the booking and billing screens, not in exported automation rules. We document your current Cliniko operational patterns (appointment confirmation process, patient intake workflow, recall reminders) as a written brief your Salesforce admin can use to rebuild equivalent flows in Salesforce Flow.
What does a Cliniko patient record become in Salesforce?
Each Cliniko patient becomes a Salesforce Contact linked to a Salesforce Account (the clinic or business entity). Demographics (name, date of birth, address) map to standard Contact fields. Cliniko custom fields like Medicare number, health fund, EPC expiry, and patient tags map to custom fields on the Contact object (Medicare_Number__c, Health_Fund__c, EPC_Expiry__c, Tags__c). The original Cliniko create date is preserved as a custom datetime field (Original_Create_Date__c) since Salesforce CreatedDate reflects the migration timestamp, not the original patient creation date.
Can I migrate Cliniko appointment types and practitioners to Salesforce?
Yes, but they require Salesforce custom objects because no native equivalent exists. Cliniko appointment types (service name, duration, colour, billing item) become a custom Appointment_Type__c object. Cliniko practitioners (name, profession, registration number, qualifications) become a custom Practitioner__c object with a lookup to the clinic Account. FlitStack creates both custom objects with the correct __c field definitions and lookup relationships, then links appointment records to both the patient Contact and the practitioner Practitioner__c record.
How are Cliniko appointment records handled in Salesforce?
Cliniko appointments migrate as a custom Appointment__c object linked to the patient Contact (ContactId lookup) and the practitioner Practitioner__c record (Practitioner_Id__c lookup). The appointment type links to Appointment_Type__c. Status values (Booked, Arrived, Did Not Arrive, Cancelled) map to a custom pick-list on Appointment__c.Appointment_Status__c. All appointment times are converted from the Cliniko clinic timezone to UTC before inserting into Salesforce, and the original timezone is preserved in Appointment_Timezone__c. The original Cliniko appointment create date is stored in Original_Create_Date__c.
Does the migration affect my Cliniko account during cutover?
No. FlitStack pulls data from Cliniko using read-only API access — your team can continue scheduling appointments, updating patient records, and processing invoices in Cliniko throughout the migration. A delta-pickup window of 24–48 hours after the full migration commits captures any Cliniko records created or modified during the cutover. On go-live, your team switches to Salesforce. Cliniko remains in read-only mode for a brief period so staff can reference historical appointment records during the transition.
How are Cliniko invoices and financial records handled in Salesforce?
Cliniko invoices are migrated as a custom Invoice__c object with lookups to the patient Contact and the clinic Account. Fields include total_amount__c (custom currency field), payment_status__c (mapped value-by-value from Cliniko), date_issued__c, and date_paid__c. Cliniko's line-item invoice detail is stored in a custom text area field on Invoice__c for reference. Salesforce does not have a native invoice object — this is a pure custom-field build. FlitStack preserves the full invoice record history so the clinic retains financial visibility for reporting and audit purposes.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Klipy CRM to SalesforceMapping · history · rollbackChartMogul to SalesforceMapping · history · rollbackTekion to SalesforceMapping · history · rollbackAccelo to SalesforceMapping · history · rollbackBoomTown to SalesforceMapping · history · rollbackVendasta to SalesforceMapping · history · rollback Cliniko to HubSpotMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Cliniko to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote