---
title: "Cliniko to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate Cliniko to HubSpot with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/cliniko/to/hubspot"
---

# Cliniko to HubSpot migration

Moving from Cliniko to HubSpot lets healthcare practices add sales, marketing, and service automation to their patient data. FlitStack AI maps every patient, appointment, invoice, and custom property — preserving original timestamps and treatment history so your HubSpot CRM is patient-ready from day one.

Short answer

FlitStack AI migrates contacts, users, meetings, timeline event / notes and deals from Cliniko to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 5,000 patients.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/cliniko/to/hubspot#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Cliniko ![](https://flitstack.ai/platforms-trim/cliniko.webp)

Destination HubSpot ![](https://flitstack.ai/platforms-trim/hubspot.webp)

Contact User Meeting Timeline Event / Note Deal

Mapped field by field · sample run · one-click rollback

## What moves from Cliniko to HubSpot?

Cliniko is a healthcare practice-management system built around patients, practitioners, appointments, treatment notes, and invoices.

Read the full summary

HubSpot CRM models contacts, companies, deals, and activities for sales, marketing, and service teams. The two platforms share no common object schema — every Cliniko entity requires a deliberate translation decision rather than a simple rename. FlitStack AI extracts patient demographics and contact details as HubSpot Contacts, appointment history as HubSpot Meetings with duration and practitioner ownership, and invoices as HubSpot Deals with financial amounts and statuses. Healthcare-specific data — medical alerts, blood type, treatment notes, and patient groups — migrates as HubSpot custom properties or Timeline Events, since HubSpot has no native clinical equivalent. Practitioners are resolved to HubSpot users by email match and become record owners. The migration carries everything Cliniko stores natively through its API. What cannot migrate are Cliniko appointment-reminder workflows and patient-follow-up sequences — those are scheduling automations with no HubSpot equivalent and must be rebuilt using HubSpot Sequences, Tasks, or Workflows. We deliver a rebuild-reference export alongside the migration so your team has a step-by-step map of every automation to recreate.

direct

### Patient → Contact

Cliniko patients map to HubSpot Contacts.

How it maps

All standard demographics — name, email, phone, address, date of birth — move as direct property mappings. Medical-specific fields like alerts and blood type require HubSpot custom contact properties since HubSpot has no native clinical field equivalent.

direct

### Practitioner → User (Owner)

Cliniko practitioners are resolved to HubSpot users by email match and become record owners.

How it maps

A Cliniko practitioner record with email 'jane\@clinic.com' matches a HubSpot user with the same email address. Unmatched practitioners are flagged before migration so your team can invite them to HubSpot or assign a fallback owner.

direct

### Appointment → Meeting

Cliniko appointments map to HubSpot Meetings with original start and end times preserved.

How it maps

The HubSpot Meeting owner is set to the mapped practitioner user. Appointment status (arrived, completed, no-show) maps to HubSpot status properties. Appointment type, duration in minutes, and location are stored as custom meeting properties.

transformed

### Treatment Note → Timeline Event / Note

Cliniko treatment notes contain clinical documentation — SOAP notes, observations, prescriptions — with no HubSpot native equivalent.

How it maps

FlitStack AI maps treatment note text to HubSpot Timeline Events linked to the contact and practitioner, preserving the clinical context, date, and practitioner association. Long-form notes with structured sections may be flattened into a single rich-text Timeline Event for readability.

direct

### Invoice → Deal

Cliniko invoices map to HubSpot Deals capturing the total invoice amount, balance due, invoice date, due date, and payment status.

How it maps

Each Deal is associated to the patient Contact. Invoice status (paid, overdue, written off) maps to HubSpot Deal stage values via value mapping.

split

### Invoice Line Item → Product (associated to Deal)

Cliniko invoices contain line items with individual products, quantities, unit prices, and taxes.

How it maps

HubSpot Deals hold a single total amount field — itemised line items do not map natively. FlitStack splits each Cliniko invoice line item into a HubSpot Product record associated to the Deal via a Deal Line Item custom object, preserving the product name, quantity, and unit price.

******What moves 11 objects

Cliniko HubSpot

- Patient Contact 1:1
- Practitioner User 1:1
- Appointment Meeting 1:1
- Treatment Note Timeline Event transformed
- Invoice Deal 1:1
- Invoice Line Item Product split

\+ 5 more in the mapping below

## How Cliniko and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension                   | Cliniko                                                                                             | HubSpot                                                                                                                |
| --------------------------- | --------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Core object model           | Cliniko: Patients, Practitioners, Appointments, Treatment Notes, Invoices — all healthcare-specific | HubSpot: Contacts, Companies, Deals, Meetings, Tasks — general B2B sales/service                                       |
| Patient record depth        | Cliniko stores medical alerts, blood type, and patient notes as first-class properties              | HubSpot has no native clinical fields; healthcare properties become custom contact properties                          |
| Scheduling and appointments | Appointments are core Cliniko objects with practitioner, type, status, and location                 | HubSpot Meetings are activities linked to contacts; practitioner association requires owner mapping or custom property |
| Financial records           | Cliniko Invoices contain line items, taxes, discounts, and individual itemised products             | HubSpot Deals hold a single total amount; invoice line items must map to separate Products records                     |
| Automation model            | Cliniko has built-in appointment reminders, patient follow-up sequences, and recall triggers        | HubSpot Sequences, Workflows, and Tasks replace automation; no Cliniko automations transfer automatically              |
| Referrer tracking           | Cliniko Referrers are a standalone entity linked to patients and appointments                       | HubSpot has no referrer object; referrers map to Company records with a custom referral flag                           |

## Cliniko to HubSpot field mapping

The 30 most-used fields of 40 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/cliniko/to/hubspot.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Cliniko HubSpot

1. `first_name` Patient `firstname` Contact
2. `last_name` Patient `lastname` Contact
3. `email` Patient `email` Contact
4. `phone` Patient `phone` Contact
5. `mobile_phone` Patient `mobilephone` Contact

| Cliniko field                   | HubSpot field                            | Mapping                 | Note                                                                                                                                                 |
| ------------------------------- | ---------------------------------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Patient.first_name`            | `Contact.firstname`                      | direct                  |                                                                                                                                                      |
| `Patient.last_name`             | `Contact.lastname`                       | direct                  |                                                                                                                                                      |
| `Patient.email`                 | `Contact.email`                          | direct                  |                                                                                                                                                      |
| `Patient.phone`                 | `Contact.phone`                          | direct                  |                                                                                                                                                      |
| `Patient.mobile_phone`          | `Contact.mobilephone`                    | direct                  |                                                                                                                                                      |
| `Patient.address_line_1`        | `Contact.address`                        | direct                  |                                                                                                                                                      |
| `Patient.city`                  | `Contact.city`                           | direct                  |                                                                                                                                                      |
| `Patient.state`                 | `Contact.state`                          | direct                  |                                                                                                                                                      |
| `Patient.postcode`              | `Contact.zip`                            | direct                  |                                                                                                                                                      |
| `Patient.country`               | `Contact.country`                        | direct                  |                                                                                                                                                      |
| `Patient.date_of_birth`         | `Contact.date_of_birth`                  | direct                  |                                                                                                                                                      |
| `Patient.created_at`            | `Contact.createdate`                     | direct                  |                                                                                                                                                      |
| `Patient.updated_at`            | `Contact.hs_lastmodifieddate`            | direct                  |                                                                                                                                                      |
| `Patient.medical_alert`         | `Contact.cliniko_medical_alert__c`       | custom\_field\_required | HubSpot has no native medical-alert field. A custom text property is created to store the alert content from Cliniko.                                |
| `Patient.blood_type`            | `Contact.cliniko_blood_type__c`          | custom\_field\_required | Blood type in Cliniko maps to a custom pick-list property on HubSpot Contact. Value mapping is applied for Cliniko pick-list options.                |
| `Patient.id`                    | `Contact.cliniko_patient_id__c`          | custom\_field\_required | Cliniko's internal patient ID is stored as a custom string field for traceability and delta-run deduplication.                                       |
| `Patient.billing_email`         | `Contact.billing_email__c`               | custom\_field\_required | Cliniko billing email is a distinct field; HubSpot stores it as a custom property since HubSpot has one email field used for contact identification. |
| `Patient.referred_by`           | `Contact.hs_analytics_source_data_1`     | value\_mapping          | Cliniko referred\_by is matched to the Cliniko Referrer entity; mapped to HubSpot's original source-data field for attribution.                      |
| `Appointment.appointment_start` | `Meeting.hs_meeting_start_time`          | direct                  |                                                                                                                                                      |
| `Appointment.appointment_end`   | `Meeting.hs_meeting_end_time`            | direct                  |                                                                                                                                                      |
| `Appointment.duration`          | `Meeting.hs_meeting_duration_minutes__c` | custom\_field\_required | Cliniko appointment duration in minutes stored as a custom property on HubSpot Meeting.                                                              |
| `Appointment.status`            | `Meeting.hs_meeting_status`              | value\_mapping          | Cliniko appointment status values (arrived, completed, no-show, cancelled) map to HubSpot meeting status via value mapping.                          |
| `Appointment.appointment_type`  | `Meeting.cliniko_appointment_type__c`    | custom\_field\_required | Cliniko appointment types (initial consultation, follow-up, etc.) stored as a custom property on HubSpot Meeting.                                    |
| `Appointment.location`          | `Meeting.location`                       | direct                  |                                                                                                                                                      |
| `Appointment.practitioner_id`   | `Meeting.hs_user_id_of_owner`            | transformed             | Cliniko practitioner ID is resolved to a HubSpot user by email match. The resolved user becomes the Meeting owner.                                   |
| `Appointment.notes`             | `Meeting.hs_meeting_body`                | direct                  |                                                                                                                                                      |
| `Appointment.reminder_sent`     | `Contact.cliniko_reminder_sent__c`       | custom\_field\_required | Cliniko reminder-sent flags are preserved as custom contact properties; reminder automation must be rebuilt in HubSpot.                              |
| `Practitioner.first_name`       | `User.firstname`                         | direct                  |                                                                                                                                                      |
| `Practitioner.last_name`        | `User.lastname`                          | direct                  |                                                                                                                                                      |
| `Practitioner.email`            | `User.email`                             | direct                  |                                                                                                                                                      |

## What to watch for in a Cliniko to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### HubSpot has no native healthcare object model

Cliniko stores patient alerts, blood type, and clinical notes as first-class record properties.

How we handle it

HubSpot's standard Contact schema has no clinical fields — there is no native 'medical alert' property, no 'blood type' field, and no object equivalent to a Cliniko Treatment Note. FlitStack AI creates HubSpot custom contact properties (cliniko\_medical\_alert\_\_c, cliniko\_blood\_type\_\_c) and stores treatment note text as Timeline Events, but the data lives in custom fields rather than native objects. Your HubSpot admin will need to add these custom properties before migration data arrives, and your team will need to train staff on the custom property workflow.

high

### Appointment-reminder and patient-follow-up sequences do not transfer

Cliniko includes built-in appointment-reminder automations (SMS and email reminders at configurable intervals before appointments) and patient-follow-up sequences (recalls, re-booking prompts, progress-check messages).

How we handle it

HubSpot has no equivalent to Cliniko's internal scheduling-triggered reminders. These automations are not stored as data records — they are workflow configurations — so they cannot be exported and re-imported. FlitStack AI does not migrate Cliniko automations. We export the automation definitions as a structured rebuild reference and provide a step-by-step map of every Cliniko reminder and recall rule to its HubSpot Sequence or Workflow equivalent, so your team can rebuild them natively in HubSpot.

medium

### Cliniko Patient Groups require manual HubSpot list setup

Cliniko Patient Groups are used to segment patients by condition, program, or practitioner caseload.

How we handle it

HubSpot has no patient-grouping object — the closest analogues are Static Lists and HubSpot Workflow enrollment lists, neither of which carries the clinical classification semantics of Cliniko groups. FlitStack AI converts each Cliniko Patient Group into a HubSpot Static List of contact IDs at migration time, but dynamic group membership (patients automatically added or removed based on Cliniko rule criteria) cannot be replicated without rebuilding those rules as HubSpot Workflows. Multi-practitioner group ownership also requires a custom practitioner-association property on each list.

medium

### Invoice line items split across HubSpot Deals and Products

Cliniko invoices carry itemised line items — each treatment or product with its own quantity, unit price, tax, and discount.

How we handle it

HubSpot Deals hold a single total-amount field (Amount) and do not natively support multi-line item invoices. FlitStack AI maps the Cliniko invoice total to HubSpot Deal amount and creates separate Product records for each line item, associating them to the Deal via a custom Deal Line Item object. This preserves the product detail, but the native HubSpot Deals UI will not display line items inline — your team will need to open the associated Products sub-panel to see itemisation.

medium

### Cliniko API rate limits affect large clinic data extraction

Cliniko's API imposes per-account rate limits on bulk data reads.

How we handle it

Large clinics with extensive appointment history, treatment note archives, or high patient volumes may encounter pagination limits or throttling during extraction. FlitStack AI handles rate-limit backoff and retries automatically, but very large datasets may require incremental extraction runs over multiple days. The delta-pickup window captures records modified during the extraction phase, ensuring no data created mid-extraction is missed. Practices with over 50,000 appointment records should plan for a 48–72 hour extraction window in addition to the migration run.

## How the migration runs

1. ### Audit Cliniko data and present the object mapping plan

   FlitStack AI extracts a full data inventory from Cliniko — patient count, practitioner count, appointment volume, treatment note count, invoice count, and a list of all custom fields and patient groups.

   What this step covers

   We present an object-mapping plan that shows exactly which Cliniko entity becomes which HubSpot object, which custom fields are created, and which Cliniko features have no HubSpot equivalent and must be rebuilt. You approve the plan before any migration runs.

2. ### Resolve practitioners to HubSpot users by email

   Every Cliniko practitioner must resolve to a HubSpot user who can own records.

   What this step covers

   FlitStack AI matches practitioner email addresses against HubSpot user email addresses. Practitioners with no matching HubSpot user are flagged as 'unresolved' — your team either invites them to HubSpot before migration or assigns a fallback owner. No appointment or patient record lands in HubSpot without an assigned owner.

3. ### Set up HubSpot custom fields and Timeline Events

   Before data lands, FlitStack AI creates the HubSpot custom contact properties (cliniko\_medical\_alert\_\_c, cliniko\_blood\_type\_\_c, cliniko\_patient\_id\_\_c, etc.) and custom meeting properties (cliniko\_appointment\_type\_\_c, hs\_meeting\_duration\_minutes\_\_c) needed for healthcare data that has no native HubSpot field.

   What this step covers

   Treatment notes are configured as Timeline Events on the Contact record so practitioners can review clinical history inline in HubSpot. We deliver a schema setup checklist so your HubSpot admin can pre-create these fields if preferred.

4. ### Sequence the migration respecting foreign-key dependencies

   HubSpot requires Contacts to exist before Deals can associate to them, and Meetings to exist before they can link to Contacts.

   What this step covers

   FlitStack AI sequences the migration in dependency order: Companies (from Referrers), then Practitioners (resolved to users), then Patients (as Contacts with custom clinical properties), then Appointments (as Meetings with owner mapping), then Invoices (as Deals with line-item Products). This ordering ensures foreign keys resolve correctly on first pass without duplicate record creation.

5. ### Run a sample migration with field-level diff before full commit

   A representative sample — typically 200–500 records spanning patients, appointments, practitioners, and invoices — migrates first.

   What this step covers

   FlitStack AI generates a field-level diff showing every source value and its destination equivalent. You verify that medical alerts landed in cliniko\_medical\_alert\_\_c, that appointment owners resolved to the correct practitioner, and that invoice amounts mapped to Deal amount. You approve the diff before the full migration commits.

6. ### Execute full migration with delta pickup and audit log

   The full dataset migrates to HubSpot.

   What this step covers

   A delta-pickup window (typically 24–48 hours) captures any Cliniko records created or modified during the cutover period — new patient sign-ups, appointment bookings, or invoice payments made in Cliniko while migration runs. FlitStack AI maintains a full audit log of every record created, updated, or skipped. If reconciliation fails, one-click rollback reverts the HubSpot environment to its pre-migration state. We deliver a post-migration report showing record counts per object and any unresolved mappings requiring manual follow-up.

![](https://flitstack.ai/platforms/cliniko.png) Cliniko ![](https://flitstack.ai/platforms/hubspot.svg) HubSpot

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · HubSpot Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**48–72 hours for under 5,000 patients** Typical, smaller accounts

**5–10 days for over 20,000 patients or complex custom-property setups** Large or heavily customised accounts

A quote scales with record count, custom property count, and data-model divergence between Cliniko and HubSpot. The dominant cost drivers are the number of Cliniko custom properties needing HubSpot custom field creation, the volume of appointment history mapped to Meetings, and whether treatment notes require structured Timeline Event reconstruction versus bulk note migration. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Cliniko to HubSpot →](https://flitstack.ai/contact)

## Why teams move from Cliniko to HubSpot

- Cliniko covers scheduling and clinical notes but stops at patient outreach and marketing. Practices that want to run email campaigns, track referral pipelines, and manage inbound leads find HubSpot's marketing and sales hubs fill the gap Cliniko leaves. Reddit threads and G2 reviews of Cliniko frequently note that growth beyond clinical operations requires a second tool — HubSpot consolidates that stack.
- HubSpot's open API and integration marketplace connects to the broader sales and marketing tech stack in ways Cliniko's ecosystem does not. Practices that have expanded beyond clinical work — adding B2B referral programs, productised services, or event-based marketing — hit Cliniko's ceiling for tracking non-clinical relationships and need HubSpot's flexible association model.
- HubSpot's built-in reporting on deals, pipelines, and team performance provides RevOps visibility that Cliniko cannot match without third-party tools. Teams migrating report that HubSpot's dashboards make sales forecasting and lead-source attribution achievable without a data analyst on staff. The platform's visual pipeline stages, deal health metrics, and custom reporting also let non-technical staff monitor performance trends, adjust quotas, and align marketing spend with revenue outcomes.
- Cliniko's appointment and invoice data alone does not give practices a clear picture of revenue per practitioner, product, or service line over time. HubSpot's Deals + Products model lets practices see LTV, product-level margins, and referral attribution in a single dashboard — a reporting gap Cliniko reviews repeatedly flag as a pain point.

Questions, answered

## Cliniko to HubSpot migration questions

How long does a Cliniko to HubSpot migration take?

Most Cliniko-to-HubSpot migrations complete in 48–72 hours of clock time for small single-practitioner clinics with under 5,000 patients. Mid-size practices with multiple practitioners, patient groups, and 10–20 custom fields extend to 5–7 days. Large multi-location setups with appointment histories spanning years and treatment notes mapped to Timeline Events can require 8–10 days. The dominant timeline driver is the Cliniko API extraction phase for large appointment histories — HubSpot bulk import runs are typically faster.

Will my Cliniko appointment reminders and patient follow-up sequences migrate to HubSpot?

No. Cliniko's built-in appointment-reminder automations (SMS and email reminders before appointments) and patient-follow-up recall sequences are workflow configurations, not data records. They cannot be exported or transferred to HubSpot because HubSpot has no equivalent scheduling-triggered reminder system. FlitStack AI does not migrate automations. We export your Cliniko automation definitions as a structured rebuild reference that maps each Cliniko reminder rule and recall sequence to its HubSpot Sequence, Task, or Workflow equivalent, giving your team a step-by-step recipe for rebuilding them in HubSpot.

What happens to Cliniko medical alerts and blood type fields in HubSpot?

Cliniko medical alerts and blood type have no native HubSpot equivalent — HubSpot's standard Contact schema has no clinical fields. FlitStack AI creates custom contact properties (cliniko\_medical\_alert\_\_c and cliniko\_blood\_type\_\_c) and stores the original Cliniko values exactly as entered. Your HubSpot admin needs to add these custom properties before migration runs, or FlitStack AI creates them during the schema setup phase. Staff will find the data in the Contact record's custom properties panel.

Can I migrate Cliniko custom fields and patient groups to HubSpot?

Yes to custom fields. Cliniko custom patient fields (beyond the standard properties) map to HubSpot custom contact properties — FlitStack AI creates these during schema setup. Yes to Patient Groups with caveats: Cliniko Patient Groups convert to HubSpot Static Lists of contact IDs, preserving the segment membership at migration time. However, dynamic Patient Groups (rules-based membership that changes over time) cannot be replicated in HubSpot without rebuilding those rules as HubSpot Workflow enrollment criteria — this is a manual rebuild step.

What happens to Cliniko invoices and financial data in HubSpot?

Cliniko invoices become HubSpot Deals. The invoice total maps to Deal amount, the invoice status (paid, overdue, written off) maps to Deal stage via value mapping, and the Cliniko invoice ID is stored as cliniko\_invoice\_id\_\_c. Invoice line items are split: each Cliniko line item becomes a HubSpot Product associated to the Deal via a custom Deal Line Item object. HubSpot's native Deals UI shows the total amount — itemised product detail requires opening the associated Products sub-panel.

Does the migration affect my Cliniko account during the cutover?

No. FlitStack AI uses scoped read access on Cliniko via API — your team continues working in Cliniko throughout the migration. New patients, appointments, and invoices created during the cutover are captured by the delta-pickup window, typically 24–48 hours after the initial extraction. Any appointment reminders or follow-up sequences configured in Cliniko continue to fire normally since Cliniko is not affected by the read-only migration connection.

What does a Cliniko Treatment Note become in HubSpot?

Cliniko Treatment Notes are clinical records containing SOAP notes, observations, prescriptions, and other clinical text. HubSpot has no native clinical documentation object. FlitStack AI maps treatment note text to HubSpot Timeline Events linked to the patient Contact and dated with the original note timestamp. The practitioner who created the note becomes the Timeline Event owner. Long-form structured notes with multiple SOAP sections may be flattened into a single rich-text Timeline Event for readability in HubSpot's interface. A custom meeting property preserves the Cliniko appointment type context for each note.

## Related migrations

[![](https://flitstack.ai/platforms-trim/hubspot.webp) Migrate to **HubSpot** Every source we move into HubSpot, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/hubspot)

### [HubSpot implementation](https://flitstack.ai/services/hubspot-implementation)

[Set up HubSpot and migrate into it as one engagement.](https://flitstack.ai/services/hubspot-implementation)

[See the service →](https://flitstack.ai/services/hubspot-implementation) [**BoomTown to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/boomtown/to/hubspot) [**Listrak to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/listrak/to/hubspot) [**Sage CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sage-crm/to/hubspot) [**Monica CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/monica-crm/to/hubspot) [**Entrata to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/entrata/to/hubspot) [**Brivity to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/brivity/to/hubspot) [**Cliniko to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/cliniko/to/salesforce-sales-cloud)

## Sources: official documentation

1. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
2. [Create and edit custom objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/object-settings/create-custom-objects)
3. [Import objects programmatically — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/import-objects)
4. [Understand property field types in HubSpot](https://knowledge.hubspot.com/properties/property-field-types-in-hubspot)
5. [Associate records on CRM objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/records/associate-records)
6. [Integration throughput and limits — HubSpot Knowledge Base](https://knowledge.hubspot.com/integrations/integration-throughput-and-limits)
7. [HubSpot Cloud Infrastructure and Data Hosting FAQ](https://knowledge.hubspot.com/account-security/hubspot-cloud-infrastructure-and-data-hosting-frequently-asked-questions)

Get a quote

## Moving from Cliniko to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
