Migrate your AeronaClinic data
Cloud-based practice management software for dental and health clinics in the UK and Ireland, built around appointments, charting, billing, and patient self-service via a branded Patient Portal.
In its favor
Why people choose AeronaClinic
The signal that keeps AeronaClinic on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Clinics transitioning from legacy on-premise systems choose AeronaClinic for its fully cloud architecture, which removes the need for local server maintenance and enables access from any device with a browser connection.
Small to mid-sized dental practices in the UK and Ireland pick AeronaClinic for its integrated payment stack, combining GoCardless direct debit and Stripe card processing with automated reconciliation that reduces administrative workload.
The platform's Patient Portal is a draw for practices wanting to reduce front-desk phone traffic—patients complete medical history forms, sign consent documents via e-signature, and book appointments outside clinic hours without staff involvement.
Clinics moving from competitors cite the strong customer service reputation (5.0 on Capterra across 22 reviews) as a reason to commit, with reviewers noting dedicated support during onboarding and migration phases.
The built-in GDPR opt-in recording tools and consent management features make AeronaClinic attractive to UK and Irish practices that need to demonstrate regulatory compliance without third-party add-ons.
Some practices find the feature set narrower than larger platforms like Dentrix Ascend or CareStack, reporting that advanced clinical workflows or specialist modules require third-party workarounds.
The lack of a mobile application means practitioners who want to chart or check schedules from a phone or tablet report friction compared to mobile-first alternatives.
Clinics with multiple locations or complex multi-practitioner setups report that reporting and analytics tools, while functional, are less flexible than what spreadsheet-based analysis can deliver.
Users occasionally cite the learning curve for staff unfamiliar with cloud-based interfaces, particularly for features like KPI dashboards and automated reporting that replace legacy paper or spreadsheet workflows.
Reasons to switch
Why people leave AeronaClinic
The recurring reasons buyers give for replacing AeronaClinic. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where AeronaClinic fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
AeronaClinic pricing overview
AeronaClinic is priced from £45/month on a per-feature model. The single published starting tier includes the full core platform; custom pricing applies for multi-site deployments, dedicated migration support, or bespoke integrations. No public free tier exists, though Aerona markets a free trial period on third-party listing sites.
Standard
Tier 1 of 2
£45/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on AeronaClinic's schedule — see our quote-based pricing →
What gets migrated
AeronaClinic object support
Object-by-object support for AeronaClinic migrations. Per-pair details surface during scoping.
Patients
Fully supportedPatients are the central entity in AeronaClinic. Each Patient record holds demographics, contact details, medical history, GDPR consent status, and portal credentials. We migrate Patient records with full field fidelity, preserving consent flags as discrete boolean fields rather than relying on note text.
Appointments
Fully supportedAppointments are linked to Patients and Practitioners. The export includes appointment type, date/time, duration, status, and practitioner assignment. Cancelled or no-show appointments are included as historical records unless scoped out during discovery.
Treatment Plans
Mapping requiredTreatment Plans store proposed and completed procedures with associated fees. We map the plan structure and line items, but custom fee schedules and per-practitioner pricing variations may require post-migration review.
Clinical Charting
Mapping requiredCharting data includes per-tooth or per-surface clinical notes, conditions, and procedure codes. The schema varies between UK FGDP and international coding standards; we normalise to a common structure and flag any unsupported codes for manual review.
Billing Records
Mapping requiredInvoices, payments, and outstanding balances are stored separately from treatment plans. We migrate completed transactions and open receivables, but payment plan schedules with future-dated instalments may require customer sign-off on the schedule before import.
Consent Forms
Mapping requiredGDPR consent records and e-signature events are stored as metadata attached to Patients. We preserve the consent type, date granted, and method (paper, e-signature) as structured fields. Archived PDF copies are extracted as binary blobs and linked by reference.
Patient Portal Data
Mapping requiredThe Patient Portal holds patient-initiated bookings, completed intake forms, and payment transactions outside the core clinical record. These live in a separate data partition and require coordinated extraction from Aerona's migration team alongside our own API workarounds.
Practitioners / Users
Mapping requiredPractitioner records include name, role, qualifications, and scheduling preferences. User accounts with login credentials do not transfer 1:1 in a migration; we create practitioner profiles in the destination system and flag that credentials must be re-provisioned.
Clinical Documents
Mapping requiredUploaded documents such as X-ray references, referral letters, and images are stored as binary attachments. We extract documents by reference and attach them to the corresponding Patient record in the destination system. Very large imaging files may be scoped out if bandwidth constraints apply.
Payment Methods
Mapping requiredStored payment methods (card tokens, GoCardless mandates) cannot be migrated as they are tokenised and processor-bound. We flag these as needing manual re-enrolment by patients post-migration.
Reporting / KPI Data
Not in this platformKPI dashboards and aggregated reporting data are computed at query time and are not stored as discrete records. We do not migrate analytics snapshots; customers who need historical KPI data should export reports as PDFs before cutover.
| Object | Support | Notes |
|---|---|---|
| Patients | Fully supported | Patients are the central entity in AeronaClinic. Each Patient record holds demographics, contact details, medical history, GDPR consent status, and portal credentials. We migrate Patient records with full field fidelity, preserving consent flags as discrete boolean fields rather than relying on note text. |
| Appointments | Fully supported | Appointments are linked to Patients and Practitioners. The export includes appointment type, date/time, duration, status, and practitioner assignment. Cancelled or no-show appointments are included as historical records unless scoped out during discovery. |
| Treatment Plans | Mapping required | Treatment Plans store proposed and completed procedures with associated fees. We map the plan structure and line items, but custom fee schedules and per-practitioner pricing variations may require post-migration review. |
| Clinical Charting | Mapping required | Charting data includes per-tooth or per-surface clinical notes, conditions, and procedure codes. The schema varies between UK FGDP and international coding standards; we normalise to a common structure and flag any unsupported codes for manual review. |
| Billing Records | Mapping required | Invoices, payments, and outstanding balances are stored separately from treatment plans. We migrate completed transactions and open receivables, but payment plan schedules with future-dated instalments may require customer sign-off on the schedule before import. |
| Consent Forms | Mapping required | GDPR consent records and e-signature events are stored as metadata attached to Patients. We preserve the consent type, date granted, and method (paper, e-signature) as structured fields. Archived PDF copies are extracted as binary blobs and linked by reference. |
| Patient Portal Data | Mapping required | The Patient Portal holds patient-initiated bookings, completed intake forms, and payment transactions outside the core clinical record. These live in a separate data partition and require coordinated extraction from Aerona's migration team alongside our own API workarounds. |
| Practitioners / Users | Mapping required | Practitioner records include name, role, qualifications, and scheduling preferences. User accounts with login credentials do not transfer 1:1 in a migration; we create practitioner profiles in the destination system and flag that credentials must be re-provisioned. |
| Clinical Documents | Mapping required | Uploaded documents such as X-ray references, referral letters, and images are stored as binary attachments. We extract documents by reference and attach them to the corresponding Patient record in the destination system. Very large imaging files may be scoped out if bandwidth constraints apply. |
| Payment Methods | Mapping required | Stored payment methods (card tokens, GoCardless mandates) cannot be migrated as they are tokenised and processor-bound. We flag these as needing manual re-enrolment by patients post-migration. |
| Reporting / KPI Data | Not in this platform | KPI dashboards and aggregated reporting data are computed at query time and are not stored as discrete records. We do not migrate analytics snapshots; customers who need historical KPI data should export reports as PDFs before cutover. |
Gotchas
What to watch for in AeronaClinic migrations
Issues we've hit on past AeronaClinic migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Password-protected API limits export options
Large historical record volumes in dental practices
Payment plan instalment schedules require manual sign-off
| Severity | Issue |
|---|---|
| High | Password-protected API limits export options |
| Medium | Large historical record volumes in dental practices |
| Medium | Payment plan instalment schedules require manual sign-off |
Leaving AeronaClinic?
Where AeronaClinic customers move next
12 destinations AeronaClinic can migrate to.
How a AeronaClinic migration works
Four steps, AeronaClinic-specific
Connect
Not publicly documented into AeronaClinic. Scopes limited to read-only on the data we move.
Map
We translate AeronaClinic-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate AeronaClinic quirks before production.
Migrate
Full migration with AeronaClinic rate-limit handling. Rollback available throughout.
FAQ
AeronaClinic migration FAQ
Answers to the questions buyers ask most during AeronaClinic migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your AeronaClinic migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate AeronaClinic.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your AeronaClinic setup and destination — written quote back within a business day.