CRM migration

Migrate from Cliniko to monday CRM

Field-level mapping, validation, and rollback between Cliniko and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.

Cliniko logo

Cliniko

Source

monday CRM

Destination

monday CRM logo

Compatibility

100%

10 of 10

objects map 1:1 between Cliniko and monday CRM.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Cliniko logo

Cliniko

What's pushing teams away

  • API access is tied to individual user permissions, meaning API keys inherit role-based access controls — a practitioner-key may not expose all records a migration requires, complicating bulk export scoping.
  • Cliniko's automation capabilities (e.g. appointment reminders, form-triggered updates) do not export; they must be manually rebuilt in the destination platform, increasing migration effort for workflow-heavy practices.
  • Large data exports generate in the background and can take considerable time during busy hours, which may delay migration cutover timelines for practices with high appointment volumes.
  • The platform lacks a native HubSpot or Salesforce CRM-style pipeline view for tracking patient leads or referral sources — practices that outgrow Cliniko often cite the need for a dedicated CRM layer.

Choosing

monday CRM logo

monday CRM

What's pulling them in

  • Users praise the board-based visual interface for making pipeline stages immediately legible to non-technical team members without CRM training.
  • The no-code automation builder lets sales ops teams create lead routing, stage updates, and email triggers without developer involvement.
  • Integration ecosystem connects to Slack, Gmail, Outlook, and Zapier with minimal configuration, reducing friction for teams already using these tools.
  • The flexible column system lets teams build custom CRM views — deal value, close date, lead source — without needing a developer or pre-defined schema.
  • Teams already using monday Work Management can layer CRM features onto existing boards rather than starting from scratch.

Object mapping

How Cliniko objects map to monday CRM

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

maps to

monday CRM

Contact (Monday CRM Contacts board — Item)

1:1
Fully supported

Cliniko 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

maps to

monday CRM

Monday User (appointment assignment) + optional Contact

1:1
Fully supported

Cliniko 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

maps to

monday CRM

Item on Monday CRM Appointments Board

1:1
Fully supported

Cliniko 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

maps to

monday CRM

Subitem or long-text column on Appointment Item

1:1
Fully supported

Cliniko 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

maps to

monday CRM

Deal or Item on Monday CRM Billing Board

1:1
Fully supported

Cliniko 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

maps to

monday CRM

Monday CRM per-seat pricing

1:1
Fully supported

Cliniko 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

maps to

monday CRM

Custom column on Appointments board (dropdown or status)

1:1
Fully supported

Cliniko 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

maps to

monday CRM

Item on Monday CRM Products Board

1:1
Fully supported

Cliniko 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

maps to

monday CRM

Custom columns on Contact Item

1:1
Fully supported

Cliniko 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

maps to

monday CRM

Custom column on Contact Item

1:1
Fully supported

Cliniko'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.

Gotchas + challenges

What specifically takes care here

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 logo

Cliniko gotchas

Medium

Background export generation delays for large datasets

Medium

Charts export is separate from the main data panel

High

API key permissions gate record visibility

Medium

Form template configurations do not export

Low

The old Appointments export has been deprecated

monday CRM logo

monday CRM gotchas

High

Subitems are not included in bulk exports

High

Daily API call limits vary sharply by plan

Medium

Legacy automations (Sentence Builder) are being deprecated

Medium

Excel and account exports only include table views

Low

Enterprise admins can disable non-admin exports

Pair-specific challenges

  • Healthcare-specific fields have no Monday CRM native equivalent

    Cliniko stores insurance provider, policy number, coverage type, referral source, practitioner notes, and appointment location type as native fields. Monday CRM is a general-purpose CRM with no concept of healthcare data shapes. Insurance and referral fields require custom column creation on the Contact Item; appointment location type (clinic/telehealth/home visit) and practitioner notes require custom columns on the Appointments board. FlitStack surfaces these as custom field requirements in the pre-migration plan, but Monday's schema configuration must be completed before the full migration run commits — custom columns must exist before data can land in them. Teams should budget 2–4 hours of Monday admin time for column creation before the migration window.

  • Monday CRM API daily rate limits cap export throughput on large accounts

    Monday CRM enforces daily API call limits that vary by plan: Free/Trial accounts are capped at 200 calls/day, Basic/Standard at 1,000 calls/day, Pro at 10,000 calls/day (soft limit), and Enterprise at 25,000 calls/day (soft limit with the option to request an increase). For a clinic with 50,000+ patient records, appointment items, and invoice items, these limits can extend migration clock time significantly. FlitStack implements intelligent batching, pagination, and rate-limit-aware throttling — but the Monday destination plan tier is a hard constraint on throughput. Teams on Basic or Standard plans may need to upgrade to Pro or Enterprise for the migration window to avoid multi-day API queueing. Monday's own account export feature can take up to 24 hours to generate for large accounts, adding to the pre-migration timeline before FlitStack can begin the load.

  • Cliniko automations cannot migrate — Monday Automation Center uses different trigger-action logic

    Cliniko's automation builder creates appointment reminders, patient intake confirmation sequences, billing trigger rules, and practitioner notification workflows tied to Cliniko-specific events (appointment confirmed, form submitted, invoice issued). Monday CRM's Automation Center uses different triggers (status changed, date arrived, item created, column updated) and different action types. The trigger-action logic does not translate between platforms. FlitStack does not migrate automations — this is disclosed honestly per our policy. We export Cliniko's automation definitions as a structured reference document (PDF or JSON) so the Monday admin can rebuild each automation in Monday's Automation Center. Teams should allocate 1–3 days of admin time to rebuild automations post-migration depending on automation count.

  • Monday CRM has no native practitioner calendar or clinical scheduling feature

    Cliniko's core value proposition includes a practitioner calendar with appointment types, availability blocks, and scheduling rules specific to clinical workflows. Monday CRM's board-based model has no native practitioner calendar — appointments are Items on a board, not native scheduling records. The Appointments board Item approach provides visibility but lacks availability checking, double-booking prevention, and practitioner-specific scheduling constraints that Cliniko handles natively. FlitStack maps appointments to board Items with practitioner assignment (via the Owner column), but calendar-level availability rules must be reviewed manually post-migration. Teams relying heavily on Cliniko's scheduling engine should evaluate whether Monday's third-party integrations (Calendly, Acuity) or custom automations can approximate the scheduling workflow before committing to the migration.

  • Monday CRM's per-seat pricing diverges from Cliniko's per-practitioner model

    Cliniko charges $45–$395/month based on the number of practitioners at the clinic — a model that excludes non-clinical staff from billing. Monday CRM charges per seat regardless of role, meaning front-desk staff, admin users, and billing personnel count toward the seat count. A 10-practitioner clinic currently paying Cliniko's $195/month tier might find Monday CRM costing $170–$280/month depending on total user count, even before add-ons. For clinics with many non-practitioner users, Monday can be more expensive than Cliniko; for admin-light clinics, Monday may cost less. FlitStack includes a post-migration cost comparison as part of the migration plan deliverable so teams can validate the economic case before cutover.

Migration approach

Six steps for a successful Cliniko to monday CRM data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Cliniko logo

Cliniko

Source

Strengths

  • Single flat-rate plan with unlimited patients, users, locations, and storage — no per-seat or per-record throttling.
  • Built-in invoicing, appointment scheduling, treatment notes, and reporting in one cloud-hosted application.
  • Telehealth included at no extra cost, launched and maintained without a paywall.
  • Admin-accessible data export panel covering appointments, patients, invoices, transactions, and more.
  • REST API with HTTPS enforcement, JSON responses, and a published OpenAPI schema for programmatic access.

Weaknesses

  • API keys inherit the role-based permissions of the user they belong to, so a read-only or practitioner-level key may not expose all records needed for a full migration export.
  • Form template builders (the configuration for patient intake forms) are not exported via the data panel and must be recreated manually in the destination.
  • The old Appointments export is deprecated; the replacement Reports-based export has different column layouts that require mapping adjustments during migration scoping.
  • Background export generation for large datasets can be slow during busy hours, with no real-time progress API — only email notification on completion.
  • No native automation export; appointment reminders, form-triggered patient field updates, and similar rules must be manually rebuilt in the destination system.
monday CRM logo

monday CRM

Destination

Strengths

  • Board-based UI makes pipeline stages and deal progress visually obvious without training.
  • No-code automation builder requires no developer resources to create lead routing and stage-triggered actions.
  • Flexible column system supports custom CRM fields without schema changes or admin involvement.
  • Integrates natively with Slack, Gmail, Outlook, and Zapier with minimal configuration overhead.
  • Layered product means teams already on monday Work Management can add CRM without migrating existing data.

Weaknesses

  • No native Contacts object separate from Items — contacts are managed inside a CRM module's People feature.
  • Pipeline and deal relationships use a flat item model rather than a relational object model, making complex CRM associations awkward.
  • Automations are plan-gated (250 actions/month on Standard, 25,000 on Pro) and the legacy Recipe system is being deprecated.
  • Customization and advanced views (Chart, Formula, Dependency) are locked behind Pro and Enterprise tiers.
  • Per-seat pricing with non-refundable annual billing creates cost lock-in risk during migration.

Complexity grading

How hard is this migration?

Standard CRM migration. All 8 core objects map 1:1 between Cliniko and monday CRM.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Cliniko and monday CRM.

  • Object compatibility

    A

    All 8 core objects map 1:1 between Cliniko and monday CRM.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Cliniko: Not publicly documented in the OpenAPI schema or public help docs.

  • Data volume sensitivity

    B

    Cliniko doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Cliniko to monday CRM migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Cliniko to monday CRM data migrations

Answers to the questions buyers ask most during Cliniko to monday CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Cliniko-to-Monday CRM migrations complete in 48–72 hours of clock time for under 50,000 records. Larger setups with 500,000+ records, extensive treatment-note subitems, or multiple billing-board Items extend to 5–7 days. The longest planning step is Monday schema setup — creating boards and custom columns for healthcare-specific fields (insurance, referral source, practitioner notes) that have no native Monday equivalent. Cliniko's own built-in export can take up to 24 hours for large accounts before FlitStack begins the load.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Cliniko.
Land in monday CRM, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day