CRM migration
Field-level mapping, validation, and rollback between Cliniko and Pipedrive. We move data and schema; workflows are rebuilt natively in Pipedrive.
Cliniko
Source
Pipedrive
Destination
Compatibility
10 of 10
objects map 1:1 between Cliniko and Pipedrive.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
Pipedrive
Person
1:1FlitStack 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
Pipedrive
User
1:1Cliniko 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
Pipedrive
Activity
1:1Cliniko 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
Pipedrive
Note
1:1Cliniko 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
Pipedrive
Custom Field on Person
1:1Cliniko 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
Pipedrive
Custom Field on Person
1:1Cliniko 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
Pipedrive
Product
1:1Cliniko 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
Pipedrive
File Attachment
1:1Cliniko 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
Pipedrive
Custom Field on Activity
1:1Cliniko 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
Pipedrive
No Equivalent
1:1Cliniko 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.
| Cliniko | Pipedrive | Compatibility | |
|---|---|---|---|
| Patient | Person1:1 | Fully supported | |
| Practitioner | User1:1 | Fully supported | |
| Appointment | Activity1:1 | Fully supported | |
| Treatment Note | Note1:1 | Fully supported | |
| Invoice | Custom Field on Person1:1 | Fully supported | |
| Insurance Detail | Custom Field on Person1:1 | Fully supported | |
| Product / Service | Product1:1 | Fully supported | |
| Attachment / File | File Attachment1:1 | Fully supported | |
| Appointment Type | Custom Field on Activity1:1 | Fully supported | |
| SMS / Email Communication | No Equivalent1: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
Pipedrive gotchas
Custom field hash keys differ per account
Export access gated by visibility groups
Token-based API rate limits since December 2024
Sequences and Automations not exposed via REST API
Cost escalates via workflow caps and add-ons
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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
Cliniko
Source
Strengths
Weaknesses
Pipedrive
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Cliniko and Pipedrive.
Object compatibility
3 of 8 objects need a mapping; the rest are 1:1.
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 Pipedrive migration scoping. Not seeing yours? Book a call.
Walk through your Cliniko to Pipedrive 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 Pipedrive
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.