Migrate from axiUm Dental to Odoo CRM

axiUm patient demographics (name, date of birth, contact info, address) map directly to Odoo res.partner fields. The partner_type flag (patient vs. guarantor) is preserved as a custom selection field. Original axiUm patient ID stored as Source_System_ID__c for traceability and post-migration deduplication across the Odoo res.partner model.

When axiUm stores a separate guarantor record, we create a second res.partner and link it via parent_id on the patient partner record. This mirrors Odoo's company-contact hierarchy where a guarantor acts as the parent organization for billing purposes. The guarantor relationship is critical for insurance claim workflows in Odoo's accounting module, ensuring that billing addresses and payment responsibilities align correctly.

Each completed treatment entry in axiUm (ADA code + tooth surface + provider + date) becomes a crm.lead note line or a custom treatment history field on the res.partner. We create one lead per treatment visit so Odoo's activity timeline reflects clinical visits. Lead name uses the ADA procedure description.

axiUm medical alert flags have no Odoo CRM equivalent. We create a custom char field (Medical_Alert__c) on res.partner and populate it with the full alert text from axiUm. For multi-alert patients, we concatenate with semicolons. Odoo Studio can surface this as a red banner on the partner form.

axiUm Perio Chart stores probing depths per tooth site (six sites per tooth, full-mouth series). Odoo CRM has no perio model — we create a custom one2many or many2many field group capturing site, tooth number, measurement in mm, furcation class, and mobility grade. Institutions requiring CODA compliance reporting should request a dedicated Perio module from an Odoo developer.

axiUm's graphical tooth-chart odontogram has no Odoo CRM equivalent. We export the odontogram as a PDF image via axiUm's reporting engine and attach it to the res.partner record as an ir.attachment. A custom.char field (Odontogram_Ref__c) stores a URL or internal reference to the image file.

axiUm financial transactions (ADA codes, adjustments, insurance payments) map to Odoo account.move entries. We create invoices and payments under the patient's res.partner. ADA procedure codes are configured as Odoo products with the correct pricing. Provider production reports translate to Odoo analytic accounting entries.

axiUm stores insurance carrier name, group number, subscriber ID, and effective dates. We create custom.char fields (Insurance_Carrier__c, Group_Number__c, Subscriber_ID__c) on res.partner and map coverage type as a selection field. Odoo's Accounting app uses these for insurance billing workflows, enabling automated claim generation and coverage verification within the Odoo res.partner contact record.

axiUm appointment records (date, time, operator, operatory, procedure type) map to Odoo calendar.event records linked to the res.partner patient. We create one event per appointment. The appointment status (completed, no-show, cancelled) becomes the calendar.event state field, enabling Odoo's activity reporting to reflect actual patient visit outcomes for operational analytics.

axiUm recall reminders (6-month hygiene, annual exam) translate to recurring calendar.event records in Odoo. We calculate the next recall date from the last completed appointment and create a recurrent event series under the patient's partner record. This approach preserves the recall cadence for hygiene follow-ups and enables Odoo CRM automated reminders to trigger patient outreach through Odoo's mail.thread communication tools.

axiUm user accounts (faculty, student, staff) map to Odoo res.users. We resolve by email match and create users with the appropriate access rights group (Dental Faculty, Dental Student, Office Staff). axiUm CODA tracking fields become custom fields on the res.users record.

axiUm-scanned consent forms, ID documents, and clinical attachments are downloaded and re-uploaded to Odoo's ir.attachment store, linked to the corresponding res.partner record. File size limits are enforced per Odoo's attachment configuration. PDF format is preserved, and document metadata including original scan dates and document types are stored in the ir.attachment description field for regulatory compliance and audit trail purposes.

axiUm clinical note entries (Subjective, Objective, Assessment, Plan) have no Odoo CRM equivalent. We preserve them as mail.message records on the res.partner chatter or as custom text fields (Clinical_Note__c) for shorter entries. Institutions should configure Odoo's Discuss app to surface these on the partner timeline.