Migrate from AeronaClinic to Odoo CRM

AeronaClinic patient demographics (name, date of birth, contact details) map directly to Odoo res.partner fields. The partner_id becomes the anchor record for all other linked objects in the migration. Patient type (NHS or Private) is preserved as a custom.selection field on the res.partner record. Original AeronaClinic create dates are stored in a custom datetime field for audit traceability.

Street, city, postcode, and country fields map field-for-field to Odoo res.partner address components. Where AeronaClinic stores multiple addresses per patient, the primary address becomes the main res.partner address, while any secondary addresses are created as separate contact records linked via type='contact' to the primary partner.

AeronaClinic appointments are transformed into Odoo crm.lead records for pipeline visibility (treatment plans, upsell opportunities). The appointment date maps to crm.lead.create_date; appointment status maps to stage_id. For pure appointment scheduling needs, Odoo Calendar app installation alongside CRM is recommended post-migration.

AeronaClinic treatment plan items (procedure codes, estimated costs, clinical notes) have no native Odoo equivalent. Custom.char and custom.text fields are created on res.partner to store treatment history as structured values. If AeronaClinic exports treatment plan PDFs, Odoo Documents app provides a native repository for full plan attachment.

Free-text clinical notes from AeronaClinic are transformed into Odoo mail.message records attached to the res.partner. Original timestamps and author information are preserved during migration. For structured clinical notes in SOAP format, each section maps into corresponding custom fields on the partner record for searchable clinical data.

AeronaClinic payment transactions map to Odoo account.move records when the Odoo Accounting app is active. Amount, date, payment method, and patient reference are all preserved. If only the CRM app is active, payment data is stored as custom monetary fields on res.partner until Accounting is enabled.

Referring dentist or doctor details are stored as a separate res.partner contact record linked to the patient partner via the 'contact' relation type. This directly mirrors AeronaClinic's referral link model. The referring practitioner's name, practice, and contact details map to corresponding fields on the contact partner record.

AeronaClinic recall reminders (6-month checkup, annual review) transform into Odoo mail.activity records with activity_type='Reminder' and deadline set to the recall date. The Odoo Activity Queue in CRM manages follow-up tasks without the clinical scheduling complexity of AeronaClinic's native calendar.

Any AeronaClinic custom fields unique to the clinic — such as preferred dentist, medical alert flags, membership tier, or referral source — are created as Odoo custom fields with x_ prefix on res.partner. The full custom field creation script is delivered as part of the migration plan for repeatable deployment.

Patient-uploaded documents, consent forms, and ID scans migrate as Odoo ir.attachment records linked to the res.partner via res_model='res.partner' and res_id=partner_id. Original filenames and create dates are preserved throughout the migration for document audit compliance.

AeronaClinic staff logins map to Odoo res.users entries. Owner resolution uses email address matching to ensure each user's records are assigned to the correct Odoo user account. Any unmatched practitioners are flagged in the migration report for manual Odoo user creation before migration proceeds.

NHS number, insurance provider, policy reference, and coverage details have no native Odoo field. These migrate as custom.char and custom.selection fields on res.partner. For high-volume insurance data, we recommend a separate insurance policy document object via Odoo Documents if the data volume warrants dedicated storage.