Migrate from Dr.DENTES to Odoo CRM

Dr.DENTES patient records are the primary entity, storing name, date of birth, contact details, and address. These map directly to Odoo res.partner records with partner_type='contact'. Email addresses become the email field; phone and mobile map to phone and mobile fields respectively. Dr.DENTES patient IDs are preserved as a custom field (x_dr_dentes_patient_id) for reconciliation and delta-run de-duplication.

Dr.DENTES appointment records contain procedure codes, provider assignments, chair time, and appointment status (scheduled, completed, cancelled). Each appointment converts to an Odoo calendar.event for scheduled activities and a mail.message log entry on the patient contact's record. Original appointment dates and provider names are preserved as event fields and custom columns.

Dr.DENTES stores insurance carrier name and policy details against each patient. The carrier name maps to a separate res.partner record with partner_type='company' (so the insurance entity can be reused across multiple patient contacts). Policy number, group number, and coverage type become custom fields on the patient contact record. We create the carrier partner first, then link patient contacts via a custom insurance_carrier_id Many2one field.

Dr.DENTES treatment procedure codes and descriptions have no native equivalent in Odoo CRM's sales model. We store treatment history as mail.message records with a custom x_treatment_code and x_procedure_description field on each patient contact. For practices with high treatment volume, we evaluate whether a custom crm.treatment model is warranted on the Odoo side.

Dr.DENTES invoice amounts, payment status, and outstanding balances map to custom fields (x_last_invoice_date, x_outstanding_balance, x_payment_status) on the patient contact record. Odoo has no native billing object in the CRM module — if the practice uses Odoo Accounting alongside CRM, invoice data can be linked via the sale.order and account.move models instead.

Dr.DENTES staff and provider records include name, role (dentist, hygienist, admin), and credentials. Providers map to Odoo res.users by email match. Unmatched providers are flagged before migration — the practice either creates the Odoo user first or assigns their patient records to an existing fallback user.

Dr.DENTES practice location data (name, address, phone) maps to a res.partner record with partner_type='company' representing the dental practice itself. For multi-location practices, each location becomes its own company-type partner, and patient contacts are linked to their primary location via a custom location_id Many2one field.

Dr.DENTES treatment plan records store planned procedures, estimated dates, and treatment status. These map as mail.message logs with custom fields x_planned_procedure and x_treatment_plan_status on the patient contact. Completed plan items are logged as historical entries; pending items remain as scheduled future activities.

Dr.DENTES stores patient documents (X-rays, consent forms, insurance cards) as file attachments. These are downloaded and re-uploaded to Odoo as ir.attachment records linked to the corresponding res.partner. Odoo file size limits apply per attachment — large imaging files may need to be hosted externally with a link stored in Odoo.

Dr.DENTES appointment reminder automations, recall workflows, and billing-rule logic do not migrate. These are platform-specific automation constructs with no Odoo CRM equivalent. We export Dr.DENTES workflow definitions as a structured document so the practice admin can rebuild them using Odoo Studio automation, server actions, or base.automation rules post-migration.