CRM migration
Field-level mapping, validation, and rollback between AeronaClinic and HubSpot. We move data and schema; workflows are rebuilt natively in HubSpot.
AeronaClinic
Source
HubSpot
Destination
Compatibility
12 of 12
objects map 1:1 between AeronaClinic and HubSpot.
Complexity
BStandard
Timeline
48–72 hours
Overview
AeronaClinic is a practice management system built for dental and health clinic operations — scheduling, clinical charting, patient portal, and payment collection via GoCardless and Stripe integration. HubSpot is a CRM platform that models contacts, companies, deals, and engagement activities. These are different product categories, so the migration is a data consolidation project rather than a feature-parity move. FlitStack AI extracts patient records, appointment history, treatment plans, practitioner assignments, and billing reference data from AeronaClinic. We map patients to HubSpot Contacts, companies/practices to HubSpot Companies, appointments to HubSpot Tasks and Meetings, and treatment plans to HubSpot Deals or custom properties. Insurance providers, referral doctor information, and procedure codes migrate as HubSpot custom contact properties since no native equivalent exists. Billing and payment records — transaction IDs, amounts, payment method — are stored as custom fields and Notes in HubSpot because HubSpot has no native invoice object. GoCardless and Stripe payment data cannot generate deal amounts automatically; those must be reconciled manually post-migration. What does not migrate: appointment reminder workflows, patient portal configurations, treatment-specific automation sequences, and GoCardless/Stripe payment integrations. Those must be rebuilt in HubSpot's workflow builder or handled as separate tooling decisions. We export AeronaClinic workflow definitions as a rebuild reference for your HubSpot admin. The migration runs via AeronaClinic's export tools and HubSpot's API and bulk import endpoints, sequenced so parent records (companies) exist before child records (contacts) and appointments attach to the correct contact and company after those resolve.
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 AeronaClinic object lands in HubSpot, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
AeronaClinic
Patient
HubSpot
Contact
1:1AeronaClinic patient records map directly to HubSpot Contacts. All standard fields (name, DOB, contact details, address) transfer. Medical notes, allergies, and health conditions migrate as HubSpot custom contact properties. hs_object_id stores the AeronaClinic patient ID for traceability and delta-run de-duplication.
AeronaClinic
Company / Practice
HubSpot
Company
1:1AeronaClinic may store referring practices or multi-clinic group parent entities as separate records. These map to HubSpot Companies. Primary contact gets the Company association in HubSpot; secondary contacts get the Company association as well if the clinic is a HubSpot Company. HubSpot supports N:1 associations so multiple patients can associate to one referring practice Company.
AeronaClinic
Appointment
HubSpot
Task / Meeting
1:1AeronaClinic appointment records become HubSpot Tasks (for calls and tasks) and Meetings (for scheduled appointments). Appointment status, practitioner, procedure code, and type migrate as custom task properties. Original appointment timestamps are preserved on the HubSpot engagement record. Appointments attach to the correct patient Contact and the relevant Company.
AeronaClinic
Treatment Plan
HubSpot
Deal
1:1AeronaClinic treatment plans with estimated or completed costs map to HubSpot Deals. Procedure description, treatment codes, and cost estimates become custom deal properties. HubSpot deal stages (Appointment Booked, Treatment In Progress, Case Completed) map from AeronaClinic treatment plan status. One deal per treatment plan, associated to the patient Contact.
AeronaClinic
Insurance Provider
HubSpot
Custom property on Contact
1:1HubSpot has no native insurance provider field. AeronaClinic insurance provider data migrates as a custom contact property (Insurance_Provider__c) using a text or pick-list field depending on the source value set. Insurance policy number and group number also migrate as separate custom properties.
AeronaClinic
Referral Doctor
HubSpot
Custom property on Contact
1:1AeronaClinic referral doctor name and referral source map to HubSpot custom contact properties (Referral_Doctor_Name__c as text, Referral_Source__c as pick-list or text). HubSpot has no native referral tracking — these custom fields preserve the referral context for reporting and outreach segmentation. The referral doctor name field enables you to track which physicians send the most patients, attribute revenue to specific referral partners, and build outreach sequences for referring doctor practices. The referral source field captures how the patient found your clinic, such as NHS recommendation, private referral, or marketing campaign, supporting attribution reporting and ROI analysis across patient acquisition channels.
AeronaClinic
Practitioner / Clinician
HubSpot
HubSpot User (Owner)
1:1AeronaClinic practitioner and clinician IDs resolve to HubSpot Users by email match. The practitioner name becomes a HubSpot User and that user is set as the Owner on migrated Contacts, Deals, and engagement records they were associated with in AeronaClinic. Unmatched practitioners are flagged for team assignment before migration.
AeronaClinic
Billing / Payment Record
HubSpot
Note / Custom Property
1:1AeronaClinic invoice and payment records (GoCardless/Stripe transaction IDs, amounts, payment status, method) have no native HubSpot equivalent. HubSpot has no invoice object. We store payment status, last transaction ID, and amount as custom fields on the Contact. Detailed payment history is preserved as a Note on the contact so the team has the full record for reference.
AeronaClinic
Patient Portal Login / Preferences
HubSpot
Not migrated
1:1AeronaClinic patient portal login records and patient preferences have no HubSpot equivalent. HubSpot's member-facing tools (forms, meeting links, portal features) require separate setup. We document the source portal configuration as a reference for rebuilding patient communication preferences in HubSpot or a dedicated portal tool.
AeronaClinic
Clinical Note / Charting
HubSpot
Note
1:1AeronaClinic clinical notes and charting records attach to HubSpot Contacts as Notes. The original note timestamp and practitioner association are preserved. Clinical notes are not structured data in AeronaClinic so they migrate as free-text Notes — your team decides whether to incorporate them into HubSpot's timeline or keep them as reference records.
AeronaClinic
Attachment / Document
HubSpot
HubSpot File / Attachment
1:1AeronaClinic file attachments (treatment plan PDFs, consent forms, insurance documents) are re-uploaded to HubSpot Files and linked to the patient Contact record. File size limits apply (HubSpot default 10MB per file for attachments; larger files require alternative storage with a link stored in HubSpot). Inline images in clinical notes are downloaded and rehosted.
AeronaClinic
System ID / Timestamps
HubSpot
Custom Property
1:1AeronaClinic patient ID stored as AeronaClinic_ID__c on the HubSpot Contact for traceability and delta-run de-duplication. Original create date and last modified date preserved as custom datetime properties (Original_Create_Date__c, Last_Synced_Date__c) since HubSpot's native createdate and lastmodifieddate reflect migration time rather than the source record's history.
| AeronaClinic | HubSpot | Compatibility | |
|---|---|---|---|
| Patient | Contact1:1 | Fully supported | |
| Company / Practice | Company1:1 | Fully supported | |
| Appointment | Task / Meeting1:1 | Fully supported | |
| Treatment Plan | Deal1:1 | Fully supported | |
| Insurance Provider | Custom property on Contact1:1 | Fully supported | |
| Referral Doctor | Custom property on Contact1:1 | Fully supported | |
| Practitioner / Clinician | HubSpot User (Owner)1:1 | Fully supported | |
| Billing / Payment Record | Note / Custom Property1:1 | Fully supported | |
| Patient Portal Login / Preferences | Not migrated1:1 | Fully supported | |
| Clinical Note / Charting | Note1:1 | Fully supported | |
| Attachment / Document | HubSpot File / Attachment1:1 | Fully supported | |
| System ID / Timestamps | Custom Property1: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.
AeronaClinic gotchas
Password-protected API limits export options
Large historical record volumes in dental practices
Payment plan instalment schedules require manual sign-off
HubSpot gotchas
Marketing Contacts billing model is migration-critical
Feature tier gating is not visible until onboarding
Mandatory onboarding fees inflate year-one cost
HubSpot CSV importer cannot migrate engagements or attachments
Custom objects require Enterprise and a pre-existing schema
Pair-specific challenges
Migration approach
Extract and profile AeronaClinic data
FlitStack AI pulls patient records, appointment history, treatment plans, practitioner assignments, and billing reference data from AeronaClinic using the platform's export tools or API endpoints. We profile the data to identify the full field inventory, value distributions for pick-list fields (appointment status, treatment status, insurance provider), and record volumes per object. The profiling output drives the HubSpot custom property setup plan and the field mapping specification.
Design HubSpot custom properties and pipeline structure
Based on the AeronaClinic field inventory, we design the HubSpot custom contact properties (allergies, medical conditions, insurance provider, referral source), custom deal properties (procedure code, treatment plan cost), and custom task properties (appointment type, procedure code, practitioner). We also design the HubSpot deal pipeline stages to mirror AeronaClinic treatment plan statuses. You create these properties in HubSpot (or grant us admin access to create them) before data migration begins.
Map fields and resolve practitioner-to-user ownership
Every AeronaClinic field maps to a HubSpot field — direct mappings for standard fields (firstname, lastname, email, phone), custom-property mappings for clinical and insurance data, and deal-property mappings for treatment plans. Practitioner and clinician IDs are matched to HubSpot Users by email address. Unmatched practitioners are flagged before migration so your team can invite them to HubSpot or assign their records to a fallback owner. This step produces the final migration specification reviewed and approved by your team.
Run sample migration with field-level diff
A representative slice of records — typically 100–500 covering a range of patient types, appointment statuses, and treatment plans — migrates first. We generate a field-level diff showing the source AeronaClinic value and the destination HubSpot value for every mapped field so you can verify clinical data accuracy, insurance field population, appointment timestamps, and deal amount mapping. You approve the sample before the full run commits. If issues surface, we adjust the mapping and re-run the sample.
Execute full migration with delta-pickup and cutover
The full dataset migrates to HubSpot with parent records (Companies) created first, then Contacts with their company associations, then Deals linked to contacts, then Tasks and Meetings for appointment history. A delta-pickup window (typically 24–48 hours after the main run) captures any records created or modified in AeronaClinic during the cutover period. Your team continues working in AeronaClinic throughout. Audit log captures every operation. One-click rollback is available if reconciliation fails. After delta-pickup, you point your team to HubSpot and decommission the AeronaClinic integration.
Platform deep dives
AeronaClinic
Source
Strengths
Weaknesses
HubSpot
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 AeronaClinic and HubSpot.
Object compatibility
1 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
AeronaClinic: Not publicly documented.
Data volume sensitivity
AeronaClinic 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 AeronaClinic to HubSpot migration scoping. Not seeing yours? Book a call.
Walk through your AeronaClinic to HubSpot migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave AeronaClinic
Other ways to arrive at HubSpot
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.