Migrate from AeronaClinic to Twenty CRM

AeronaClinic patient records map 1:1 to Twenty People. Every demographic field (name, DOB, contact details, address) translates directly. NHS number and SDS number migrate as custom fields on the People record — Twenty has no native healthcare identifier fields, so these are pre-created in Settings → Data Model before the import.

GDPR consent flags, opt-in dates, and e-signature timestamps stored in AeronaClinic's consent module have no native equivalent in Twenty. These map to custom select and datetime fields on the People object. Consent type (treatment, marketing, data retention) requires a separate custom pick-list created in Twenty Data Model before migration.

AeronaClinic stores structured medical history fields (allergies, conditions, medications, medical alerts) alongside free-text clinical notes. Structured fields migrate as custom fields on People. Free-text clinical notes attach as Twenty Notes linked to the People record. Tooth-charting data (quadrant, tooth number, surface condition) requires custom fields since Twenty Notes does not support structured dental charting notation.

AeronaClinic's clinic or practice entity maps directly to Twenty Companies. Practice name, address, phone, and website translate to Twenty's standard Company fields. Multi-location clinic groups (parent practice with satellite clinics) map to Twenty Company hierarchy using the parentId field. Each location must be exported as a separate Company record.

AeronaClinic appointments become Twenty Opportunities. The appointment date maps to the Opportunity closeDate field. Appointment status (Booked, Arrived, In Treatment, Completed, No Show, Cancelled) maps via value_mapping to a custom pick-list field (Appointment_Status__c) since Twenty Opportunity StageName is a sales-stage pick-list and not semantically aligned with clinical appointment states.

AeronaClinic treatment plans contain treatment type, prescribed procedures, estimated cost, and clinical notes. These map to a linked Opportunity record with custom fields: Treatment_Type__c (pick-list), Procedures__c (multi-select), Estimated_Cost__c (currency), Treatment_Notes__c (text), and Tooth_Number__c (text for charting notation). Treatment plan status (Proposed, Accepted, In Progress, Completed) maps to the Opportunity StageName with value_mapping.

AeronaClinic invoice records map to Opportunities with custom fields for billing details: Invoice_Number__c, Invoice_Amount__c, Amount_Paid__c, Payment_Method__c (card, cash, direct debit via GoCardless/Stripe), Payment_Status__c (Paid, Partial, Overdue), and Invoice_Date__c. The Opportunity Amount field holds the outstanding balance. Payment integrations must be rebuilt in Twenty.

AeronaClinic treatment records contain detailed clinical data (procedure performed, tooth number/surface, materials used, clinician, duration, clinical notes). This maps as a custom Treatment_Record object in Twenty linked to the parent Opportunity (appointment). Free-text clinical notes attach as Twenty Notes on the treatment record. Tooth-charting notation (FDI or Palmer) is stored in a custom Tooth_Chart__c field on the treatment record.

AeronaClinic staff and clinician accounts map to Twenty Workspace Members. Owner resolution happens by email match — each AeronaClinic owner email is matched against invited Twenty workspace members. Unmatched owners are flagged and assigned to a fallback Workspace Member before migration so no record lands without an owner.

AeronaClinic file attachments (consent forms, treatment plans, X-rays) re-upload as Twenty Notes with file attachments linked to the parent record (People, Opportunity, or custom Treatment_Record object). File size limits apply (Twenty default 25MB per file). Inline images in clinical notes are downloaded and rehosted.

AeronaClinic recall sequences and automated appointment reminders have no direct equivalent in Twenty. These automations must be rebuilt in Twenty Workflows (Settings → Workflows) after migration. FlitStack exports the recall rule definitions as a structured JSON reference document for your Twenty admin to use during the rebuild phase.

AeronaClinic's native GoCardless and Stripe integrations reconcile payments directly within the platform. Twenty has no native payment gateway — this must be rebuilt using a third-party integration (Stripe Connect, GoCardless API) after migration. Payment transaction history and reconciliation records do migrate as custom fields on the relevant Opportunity.