CRM migration
Field-level mapping, validation, and rollback between Cliniko and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Cliniko
Source
monday CRM
Destination
Compatibility
10 of 10
objects map 1:1 between Cliniko and monday CRM.
Complexity
BStandard
Timeline
48–72 hours
Overview
Cliniko is a cloud-based practice management platform built for healthcare clinics and allied health practitioners. Its data model centers on Patients (clients), Practitioners, Appointments, Treatment Notes, Invoices, and Products — all structured around a per-practitioner pricing model. Monday CRM uses a board-based architecture where Contacts, Leads, and Deals are Items on customizable Boards, with column types replacing traditional CRM fields and no native concept of practitioners, clinical notes, or healthcare billing objects. FlitStack AI maps Cliniko Patients to Monday Contacts, Practitioners to Monday Users for appointment assignment purposes, and Cliniko Appointments to Items on a dedicated Appointments board. Treatment Notes migrate as Subitems or long-text columns with original timestamps preserved. Invoices and line items become Deals or Items on a billing board — Monday has no native invoice object. Healthcare-specific fields (insurance provider, referral source, practitioner notes) have no Monday CRM equivalent and are preserved as custom columns. Cliniko's automations (appointment reminders, patient intake confirmations, billing triggers) are not migratable — their trigger-action logic lives in Cliniko's automation builder and must be rebuilt in Monday's Automation Center. Connected apps (MailChimp, Xero) are third-party integrations that require fresh setup in Monday. We use Cliniko's built-in data export tool and the Monday API for the migration payload, sequencing objects so foreign keys resolve correctly: Patients before Appointments, Practitioners before Practitioner assignments.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Cliniko object lands in monday CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Cliniko
Patient
monday CRM
Contact (Monday CRM Contacts board — Item)
1:1Cliniko patients map 1:1 to Monday CRM Contacts. Monday's built-in contact columns (name, email, phone, address) cover the core fields. Healthcare-specific patient properties (date of birth, insurance provider, referral source) require custom columns in Monday since no native equivalent exists. We preserve the original Cliniko patient ID as Source_System_ID for delta-run de-duplication.
Cliniko
Practitioner
monday CRM
Monday User (appointment assignment) + optional Contact
1:1Cliniko practitioners have no direct Monday CRM equivalent — Monday has no native practitioner or practitioner-calendar object. We resolve practitioner records by email match to Monday Users so appointments can be assigned to the correct user in Monday. If a practitioner also receives care at their own clinic, they additionally appear as a Contact in the Monday Contacts board. Practitioner profiles (specialty, appointment types) migrate as custom columns on the Appointments board.
Cliniko
Appointment
monday CRM
Item on Monday CRM Appointments Board
1:1Cliniko appointments map to Items on a dedicated Monday CRM board. The appointment date becomes a Monday date column; start time and duration become time-tracking columns. Appointment status (confirmed, cancelled, no-show) requires value mapping to Monday status options. Location type (clinic, telehealth, home visit) and telehealth video link fields need custom columns since Monday has no native appointment scheduling or telehealth feature.
Cliniko
Treatment Note
monday CRM
Subitem or long-text column on Appointment Item
1:1Cliniko treatment notes have no native Monday CRM equivalent — Monday is a CRM and work-management platform with no concept of clinical documentation. We migrate treatment notes as Subitems on the corresponding Appointment Item or as a long-text column on the appointment record. Multi-visit treatment plans spanning several Cliniko appointments may need to be split across multiple Monday Items; we document this mapping in the pre-migration plan. Original timestamps and practitioner attribution are preserved.
Cliniko
Invoice
monday CRM
Deal or Item on Monday CRM Billing Board
1:1Cliniko invoices have no native Monday CRM equivalent — Monday has no built-in invoice object. We map invoices to Deals (if using Monday's CRM pipeline for accounts receivable) or to Items on a dedicated billing board. Invoice status (paid, overdue, cancelled) maps to Monday status options. Total amount and outstanding balance become monetary custom columns. Line items reference Products as related Items or Subitems.
Cliniko
Practitioner Billing Model
monday CRM
Monday CRM per-seat pricing
1:1Cliniko charges $45–$395/month by number of practitioners. Monday CRM charges $12–$28/seat/month for Basic to Pro CRM tiers. The pricing models are fundamentally different — one is clinical-capacity based, the other is user-seat based. We document this mapping during the planning phase so the clinic's finance team can model the cost impact. Non-practitioner staff (admin, front desk) count as Monday seats but were not billed by Cliniko.
Cliniko
Appointment Type
monday CRM
Custom column on Appointments board (dropdown or status)
1:1Cliniko appointment types (initial consultation, follow-up, telehealth, etc.) map to a custom dropdown or status column on the Monday Appointments board. The appointment type drives pricing in Cliniko via linked billable items — that relationship is preserved as a linked-item reference to the Product Item in Monday. Appointment type-specific notes (pre-appointment instructions, duration defaults) migrate as custom text columns.
Cliniko
Product / Billable Item
monday CRM
Item on Monday CRM Products Board
1:1Cliniko products and billable items map to Items on a dedicated Monday board. Unit price, billing type (per session, per unit, subscription), and stock levels become custom columns. Products linked to appointment types in Cliniko are preserved as linked Items referencing the Monday Appointments board. Monday has no native product catalog with inventory tracking — stock-level fields are informational only unless rebuilt as custom integrations.
Cliniko
Insurance Profile
monday CRM
Custom columns on Contact Item
1:1Cliniko patient insurance profiles (provider name, policy number, coverage type) have no native Monday CRM equivalent — Monday is a general CRM with no healthcare insurance concept. We migrate insurance data as custom columns on the Contact Item: Insurance_Provider__c (text), Policy_Number__c (text), Coverage_Type__c (dropdown). Monday's HIPAA compliance is available on Enterprise plans only; Standard and Pro plans require manual data-handling policies for any patient data containing PHI.
Cliniko
Referral Source
monday CRM
Custom column on Contact Item
1:1Cliniko's referral source field (how the patient found the clinic) has no Monday CRM equivalent. We migrate it as a custom dropdown column (Referral_Source__c) on the Contact Item. Original referral attribution is preserved as text for reporting. This field can be used in Monday automations to trigger onboarding or marketing workflows once rebuilt.
| Cliniko | monday CRM | Compatibility | |
|---|---|---|---|
| Patient | Contact (Monday CRM Contacts board — Item)1:1 | Fully supported | |
| Practitioner | Monday User (appointment assignment) + optional Contact1:1 | Fully supported | |
| Appointment | Item on Monday CRM Appointments Board1:1 | Fully supported | |
| Treatment Note | Subitem or long-text column on Appointment Item1:1 | Fully supported | |
| Invoice | Deal or Item on Monday CRM Billing Board1:1 | Fully supported | |
| Practitioner Billing Model | Monday CRM per-seat pricing1:1 | Fully supported | |
| Appointment Type | Custom column on Appointments board (dropdown or status)1:1 | Fully supported | |
| Product / Billable Item | Item on Monday CRM Products Board1:1 | Fully supported | |
| Insurance Profile | Custom columns on Contact Item1:1 | Fully supported | |
| Referral Source | Custom column on Contact Item1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Cliniko gotchas
Background export generation delays for large datasets
Charts export is separate from the main data panel
API key permissions gate record visibility
Form template configurations do not export
The old Appointments export has been deprecated
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Pre-migration audit and Monday schema setup
FlitStack conducts a structured audit of Cliniko's data inventory — counting patients, practitioners, appointment types, invoices, products, and treatment notes. We produce a Monday schema setup plan specifying which custom columns to create on each board (Contacts, Appointments, Billing, Products), which board types to use (Contacts board for patients, dedicated boards for appointments and billing), and which Monday column types map to each Cliniko field. Your Monday admin creates the boards and columns before the migration run; FlitStack validates the schema before data lands. This step typically takes 2–4 hours of Monday admin time plus 1 day of FlitStack planning.
Export Cliniko data and resolve practitioner-user mappings
Cliniko's built-in data export tool generates CSV/PDF exports for patients, appointments, invoices, and products. For large accounts, this export can take up to 24 hours to generate. We simultaneously resolve practitioner-to-Monday-User mappings by email — Cliniko practitioner records are matched to Monday Users so appointment Items can be assigned to the correct owner. Any practitioner without a Monday User account is flagged before migration so your team can create accounts or assign a fallback owner. We also resolve patient-to-practitioner foreign keys so appointment Items link to the correct Contact in Monday.
Sample migration with field-level diff
A representative slice migrates first — typically 100–500 records spanning patients, appointments, and invoices across multiple practitioners. We generate a field-level diff between the Cliniko source records and the Monday destination Items so you can verify that patient custom columns (insurance fields, referral source) populated correctly, appointment owner assignment resolved to the right Monday User, invoice status value mapping used the correct Monday status options, and treatment notes landed as Subitems on the correct parent appointment. You sign off on the sample before the full run commits.
Full migration with delta-pickup window
The full migration runs against Monday CRM using the Monday API (rate-limit-aware batching). Objects sequence so foreign keys resolve correctly: Patients → Contacts first, then Practitioners → Monday Users, then Appointments → Items with linked patient references and practitioner-owner assignment, then Invoices and Products. A delta-pickup window (typically 24–48 hours) captures any Cliniko records modified or created during the cutover window so Monday reflects Cliniko's final state at go-live. Audit logs capture every operation; if reconciliation fails, one-click rollback reverts the Monday account to its pre-migration state.
Post-migration reconciliation and automation rebuild reference
FlitStack delivers a reconciliation report comparing Cliniko record counts against Monday Item counts per board, flagging any gaps. We also export Cliniko's automation definitions as a structured reference document so your Monday admin can rebuild appointment reminders, patient intake sequences, and billing triggers in Monday's Automation Center. Connected apps (MailChimp, Xero) are documented as integration rebuild tasks — these require fresh OAuth setup in Monday's integrations marketplace. Your team retains full read access to Cliniko throughout the migration for reference purposes.
Platform deep dives
Cliniko
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Cliniko and monday CRM.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Cliniko and monday CRM.
Object compatibility
All 8 core objects map 1:1 between Cliniko and monday CRM.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Cliniko: Not publicly documented in the OpenAPI schema or public help docs.
Data volume sensitivity
Cliniko doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Cliniko to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Cliniko to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Cliniko
Other ways to arrive at monday CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.