Patient acquisition & engagement · Sales Hub

Cliniko to HubSpot

Cloud practice management and EHR for allied health clinics, covering patient records, appointments, online booking, treatment notes and invoicing.

In short

Cliniko data can move into HubSpot, landing mainly in Sales Hub. 2 of 8 mapped objects move directly (Patients (enquiry/contact details) and Custom patient fields); 3 items need manual work and 2 do not move. Plan roughly 2-3 weeks for a small move and 8-12 weeks for a large one.

Last reviewed 2026-10-29 · Also relevant to Marketing, Service, Data hubs · 6 sources

1 · Checklist

Migration checklist for Cliniko

Three phases, specific to this system. Tick steps off as you go.

0 of 15 steps doneTick steps off as you go. Your progress stays in this browser.

Before

0 of 5 done

During

0 of 5 done

After

0 of 5 done
2 · Cost

What will it take?

No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.

How many records?
Custom objects?
Automation to rebuild?
History to bring?

A planning aid built from the three scenarios below. It is not a quote.

The three scenarios

low complexity

Small migration

2-3 weeks

<5k patients

CSV-based with contacts and referral source only.

medium complexity

Mid migration

4-6 weeks

5k-30k patients

Adds appointments and preference mapping.

high complexity

Large migration

8-12 weeks

30k+ patients, multi-site

API-based sync with a formal privacy review.

What moves the number

Number of patients and appointmentsReferral and consent mapping complexityNumber of custom patient fieldsSensitive-data governance reviewNeed for an ongoing Cliniko-to-HubSpot sync

Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.

3 · Where to begin

Access, mapping and limits

Start with how data leaves Cliniko: what you need to get in, what lands in HubSpot, and what will not.

API

REST (JSON over HTTPS)

Credentials needed

A per-user API key, a shard-specific base URL (api.{shard}.cliniko.com) and a User-Agent header with a contact email.

Admin permission

The CSV Data exports page is administrator-only. An API key has the same permissions as the user who created it.

Rate limits

200 requests per minute per user. Excess requests get a 429 with an X-RateLimit-Reset header.

Choose your route

How will you move the data?

No native connector was found.

  • You need: A per-user API key, a shard-specific base URL (api.{shard}.cliniko.com) and a User-Agent header with a contact email.
  • Permission: The CSV Data exports page is administrator-only. An API key has the same permissions as the user who created it.

Native imports often bring over only some data, so check coverage per object in the mapping below.

Where each object lands

yes movespartialmanualno

In Cliniko

In HubSpot

Contacts
Meetings
Files
Deals
Select an object

Hover or tap anything on the left to see where it lands.

What to expect

Treatment notes and clinical records

Out of scope. Retain them in Cliniko or an EHR. HubSpot is not a clinical record system.

Cliniko automations, booking and reminder workflows

These are platform-native and must be rebuilt, not exported.

4 · Governance

Data governance and compliance

Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.

0 of 6 agreed
Method

How we researched this page

How much to trust each section, and where it comes from.

InsufficientPartialVerified

Access, auth, rate limits and patient/appointment exports are backed by Cliniko docs. HubSpot-side mapping, a native connector and certifications were not checked in HubSpot docs, so those parts rest on category-level knowledge.

Sources

Related migrations

Quick answers

Frequently asked questions

How do I migrate Cliniko to HubSpot?

1. Agree with the clinic which fields are permitted in HubSpot and exclude clinical content. 2. Have an admin run Settings > Data exports for patients and for the Attendees report. 3. Create HubSpot custom properties for the Cliniko patient ID, referral source and reminder preferences. 4. Create a dedicated Cliniko API key on a limited-role user and note its shard.

What data can move from Cliniko to HubSpot?

These objects move directly: Patients (enquiry/contact details) and Custom patient fields. Check the mapping table for partial and manual items.

What does not move from Cliniko to HubSpot?

Treatment notes and clinical records and Cliniko automations, booking and reminder workflows. Plan to rebuild or retire these.

How long does a Cliniko to HubSpot migration take?

Small (<5k patients): 2-3 weeks. Mid (5k-30k patients): 4-6 weeks. Large (30k+ patients, multi-site): 8-12 weeks. These are planning estimates, not a quote.

What access do I need to export from Cliniko?

A per-user API key, a shard-specific base URL (api.{shard}.cliniko.com) and a User-Agent header with a contact email. The CSV Data exports page is administrator-only. An API key has the same permissions as the user who created it.

What compliance issues apply when moving Cliniko data?

Check: Health data (e.g. HIPAA, GDPR special category, Australian Privacy Act) and Minors' records. Agree consent, retention and access rules before exporting.

Talk to a partner

Moving Cliniko into HubSpot?

A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.

Talk to a partner
Talk to a partner