CRM migration

Migrate from Cliniko to Pipedrive

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

Cliniko logo

Cliniko

Source

Pipedrive

Destination

Pipedrive logo

Compatibility

100%

10 of 10

objects map 1:1 between Cliniko and Pipedrive.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Cliniko and Pipedrive serve fundamentally different operational domains — healthcare practice management versus sales CRM — which means this migration is a domain translation, not a simple field remap. Cliniko organizes around patients, practitioners, appointments, treatment notes, and invoices within a HIPAA-adjacent operational context. Pipedrive's core objects are People, Organizations, Deals, Activities, and Leads — optimized for pipeline management and sales tracking. FlitStack AI extracts Cliniko data via the Cliniko REST API: patients, practitioner assignments, appointment timelines, treatment notes, and file attachments. We map patients to Pipedrive People records, appointments to Pipedrive Activities with original start times and practitioner attribution, and treatment notes to Pipedrive Notes. Custom fields (insurance details, referral sources, treatment preferences) migrate to Pipedrive custom fields on the Person object. What does not migrate: Cliniko appointment reminders, clinical workflow templates, SMS/email communications, and billing logic — these require Pipedrive-native rebuild. We run a sample migration first with field-level diff before committing to the full dataset. Delta-pickup captures any Cliniko records modified during the cutover window.

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

Pipedrive logo

Pipedrive

What's pulling them in

  • Clean drag-and-drop pipeline interface with minimal learning curve, making it approachable for small sales teams without dedicated CRM admins.
  • Visual deal tracking keeps reps focused on next actions — activities, calls, and follow-up tasks surface directly in the pipeline view.
  • Strong integrations via Zapier and native marketplace apps let teams wire Pipedrive into Calendly, ActiveCampaign, and similar sales-stack tools.
  • Mobile apps for iOS and Android keep field reps connected to deals, contacts, and tasks without a desktop session.
  • Reputation and review volume — over 3,000 verified reviews across G2 and Capterra — signal reliability for teams evaluating CRM options.

Object mapping

How Cliniko objects map to Pipedrive

Each row shows how a Cliniko object lands in Pipedrive, 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

Pipedrive

Person

1:1
Fully supported

FlitStack AI extracts Cliniko patients via the API and creates Pipedrive People records. Standard contact fields (name, email, phone, address) map directly. Healthcare-specific fields (date of birth, referral source) migrate to custom fields on the Person object. Cliniko patient ID is preserved as a custom field for traceability.

Cliniko

Practitioner

maps to

Pipedrive

User

1:1
Fully supported

Cliniko practitioners with active Pipedrive user accounts are matched by email. Practitioners without Pipedrive logins are flagged for admin review — decide whether to create Pipedrive users or assign their records to a fallback user. Practitioner name and ID are preserved in a custom field for audit purposes.

Cliniko

Appointment

maps to

Pipedrive

Activity

1:1
Fully supported

Cliniko appointments map to Pipedrive Activities with the appointment type stored as a custom field. Activity subject carries the appointment type label. Start and end times map to Pipedrive's start and end timestamps. Appointment status (attended, no-show, cancelled) maps to Pipedrive Activity done flag. Practitioner attribution is preserved via the assigned Pipedrive user.

Cliniko

Treatment Note

maps to

Pipedrive

Note

1:1
Fully supported

Cliniko treatment notes (including SOAP notes, clinical observations, and plan details) map to Pipedrive Notes attached to the Person record. Original creation timestamps and practitioner authorship are preserved. Rich-text formatting is flattened to plain text since Pipedrive Notes does not support structured clinical templates natively.

Cliniko

Invoice

maps to

Pipedrive

Custom Field on Person

1:1
Fully supported

Cliniko invoices have no direct Pipedrive equivalent since Pipedrive lacks billing and accounting features. Invoice amounts, statuses, and payment dates migrate as custom fields on the Person record. Outstanding balance and last payment date are surfaced as separate custom fields for quick reference.

Cliniko

Insurance Detail

maps to

Pipedrive

Custom Field on Person

1:1
Fully supported

Cliniko insurance provider, policy number, coverage group, and coverage details migrate to Pipedrive custom text fields on the Person record (Insurance_Provider__c, Insurance_Policy_Number__c, Insurance_Group__c, Insurance_Coverage_Details__c). Insurance type (private, Medicare, Medicaid) maps to a Pipedrive custom pick‑list field (Insurance_Type__c) with the same values preserved from Cliniko. All custom fields must be created in Pipedrive before the migration job runs.

Cliniko

Product / Service

maps to

Pipedrive

Product

1:1
Fully supported

Cliniko products and services (billing items, appointment types, inventory) map to Pipedrive Products. Product name, price, and SKU are preserved. Products are linked to Deals in Pipedrive for quote generation. Cliniko appointment type pricing is carried over as Product prices in Pipedrive.

Cliniko

Attachment / File

maps to

Pipedrive

File Attachment

1:1
Fully supported

Cliniko patient attachments (consent forms, clinical documents, intake sheets) are downloaded and re-uploaded to Pipedrive as file attachments on the Person record. File size limits apply — Pipedrive supports uploads up to 50MB per file. We flag files exceeding this limit for manual handling.

Cliniko

Appointment Type

maps to

Pipedrive

Custom Field on Activity

1:1
Fully supported

Cliniko appointment type labels (Initial Consultation, Follow-up, Telehealth, etc.) have no native Pipedrive equivalent on Activities, so we create a Pipedrive custom pick‑list field called Appointment_Type__c on the Activity object. The migration populates this field with the exact Cliniko appointment type values, preserving the original category for reporting and filtering. The custom pick‑list must be defined in Pipedrive with the same options before the migration job runs.

Cliniko

SMS / Email Communication

maps to

Pipedrive

No Equivalent

1:1
Fully supported

Cliniko SMS and email communications stored within the patient record have no Pipedrive equivalent for inbound clinical messaging. We export communication logs as a CSV attachment on the Person record for reference. Pipedrive's email sync captures future outbound emails only; historical communications remain in the CSV export.

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

Pipedrive logo

Pipedrive gotchas

High

Custom field hash keys differ per account

High

Export access gated by visibility groups

Medium

Token-based API rate limits since December 2024

Medium

Sequences and Automations not exposed via REST API

Low

Cost escalates via workflow caps and add-ons

Pair-specific challenges

  • Bulk export pagination required for large Cliniko datasets

    Cliniko's API enforces rate limits per authentication token, and large appointment histories (50,000+ records) require paginated requests across multiple export cycles. We implement cursor-based pagination against Cliniko's API, pacing requests to avoid 429 errors. Large exports can take multiple hours; we schedule them during off-peak Cliniko usage to minimize impact. Validation after each pagination batch ensures no records are skipped or duplicated in the final Pipedrive load. The migration timeline accounts for pagination overhead explicitly rather than assuming a linear bulk export.

  • Pipedrive custom fields must be pre-created before import

    Pipedrive requires custom fields to exist in the account before they can receive data during import. Healthcare-specific custom fields (insurance provider, policy number, referral source, appointment type on activities) need to be created in Pipedrive first with the correct field types — text, pick-list, date, or currency. We deliver a pre-migration Pipedrive schema plan listing every custom field required, its type, and whether it belongs on Person or Activity. Pipedrive's 40-character hash for custom field keys means some Cliniko field names may be truncated; we communicate this during schema review before the migration runs.

  • Appointment timestamps cannot serve as future Pipedrive calendar reminders

    Pipedrive's calendar integration is forward-looking — it schedules future activities and reminders, not historical appointment data. Cliniko appointment timestamps carry over as Activity records in Pipedrive's timeline for historical reference, but they do not appear in Pipedrive's calendar view as upcoming reminders. This is a structural difference between clinical scheduling and CRM activity tracking. We document this limitation clearly and recommend using Pipedrive's built-in Activities and the Calendar sync for future appointment scheduling after go-live.

  • Practitioners without Pipedrive logins create orphaned activity records

    Cliniko practitioners may not have email logins in Pipedrive if they are part-time, administrative, or do not need CRM access. Without a Pipedrive user match, their appointment history and treatment notes cannot be attributed automatically. We resolve practitioners by email match during migration; any unmatched practitioners are flagged with their Cliniko ID preserved. You decide whether to create Pipedrive users for them, assign their records to a fallback user, or leave them unattributed. We surface this decision point before committing to the full migration.

  • Pipedrive Notes does not support clinical template structures

    Cliniko treatment notes often use structured templates — SOAP notes, clinical observation fields, treatment plans, goal tracking. Pipedrive Notes is a flat rich-text field without support for structured templates or custom sections. When migrating treatment notes, we flatten the content into Pipedrive's plain-text Note body, preserving the text but not the structural formatting. For SOAP notes, the Subjective, Objective, Assessment, and Plan sections appear as continuous text in Pipedrive. If structured template preservation is a hard requirement, we recommend extracting notes to PDF attachments rather than migrating as text.

Migration approach

Six steps for a successful Cliniko to Pipedrive data migration

  1. Discovery audit and schema mapping plan

    FlitStack AI connects to Cliniko via API and inventories your data: patient count, appointment volume, practitioner roster, custom field inventory, and attachment bucket size. We cross-reference with Pipedrive's existing schema and identify gaps. We deliver a Pipedrive schema setup plan listing every custom field to create (with type and pick-list values), user accounts to provision for practitioners, and pipeline stage configuration if Deals are in scope. Your Pipedrive admin creates the schema before migration validation runs.

  2. Practitioner-to-user resolution and record ownership plan

    During this step FlitStack AI resolves each Cliniko practitioner to a Pipedrive user by matching the email address stored in Cliniko. Practitioners that lack a Pipedrive login are listed with their Cliniko ID and status, allowing your admin to either create a new Pipedrive user, assign the records to a fallback user, or leave them unattributed. This email‑based resolution eliminates foreign‑key gaps, ensuring appointment history and treatment notes attach to the correct user when the migration job runs.

  3. Sample migration with field-level diff

    The first migration wave runs against a representative subset — generally 100–500 patients, 500–2,000 appointments, and a sample of treatment notes. FlitStack AI produces a field‑level diff that juxtaposes Cliniko source values with the corresponding Pipedrive field values for every mapped attribute. Your team reviews appointment‑type mapping, practitioner attribution, custom field population, and note content. This validation gate confirms data integrity before the full dataset is committed to Pipedrive.

  4. Full migration with delta-pickup and audit log

    Full migration runs against Pipedrive using parallelized API jobs against Cliniko's export endpoint. A delta-pickup window (typically 24–48 hours) captures any Cliniko records created or modified during the cutover. We generate an audit log listing every record migrated, its destination ID in Pipedrive, and any records that failed to migrate with error codes. One-click rollback is available if reconciliation fails.

  5. Post-migration support and workflow reference export

    After the migration completes, FlitStack AI exports Cliniko workflow definitions as a JSON reference file, documenting appointment‑reminder rules, patient‑follow‑up sequences, and any automated triggers. You receive a 30‑day post‑migration support window to address data discrepancies. Pipedrive automations—such as appointment reminders and patient follow‑up sequences—must be recreated in Pipedrive's native automation system; the exported JSON provides the logic blueprint to speed up rebuilding those workflows.

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.
Pipedrive logo

Pipedrive

Destination

Strengths

  • Intuitive drag-and-drop pipeline that sales reps actually use without resistance or training overhead.
  • Per-seat unlimited-deals model on all tiers — reps cannot be blocked from logging activity.
  • Active marketplace with 400+ integrations and a documented REST API with OpenAPI 3 specs.
  • Mobile apps with offline access, call logging, and calendar sync keep field teams operational.
  • Strong focus on sales activity tracking — next-action reminders and follow-up scheduling are first-class features.

Weaknesses

  • No custom objects — teams needing non-standard data structures must work around the four standard entity types.
  • Workflow automation limits by tier (30, 60, 90 active workflows) force upgrades as processes grow.
  • No free permanent plan — teams evaluating fit must commit to a trial without a freemium option.
  • Limited advanced reporting and custom dashboard capabilities compared to HubSpot or Salesforce.
  • Export permissions are gated by visibility groups, meaning data scoping must account for who can see what before migration.

Complexity grading

How hard is this migration?

Standard CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    3 of 8 objects need a mapping; the rest are 1:1.

  • 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 Pipedrive 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 Pipedrive data migrations

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

Can't find your answer?

Walk through your Cliniko to Pipedrive migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Cliniko-to-Pipedrive migrations complete in 48–72 hours for under 50,000 records. Larger setups with 500,000+ appointment history records or extensive healthcare custom fields extend to 5–7 days. Cliniko API pagination for large appointment exports is the longest single step; we pace requests to respect rate limits and validate each batch before proceeding. Pre-migration Pipedrive schema setup (custom field creation) typically runs 1–3 days in parallel.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Cliniko.
Land in Pipedrive, 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