Migrate from Pearl Dental Software to Odoo CRM

Pearl patient records contain the primary patient name, postal address, phone numbers, email, and date of birth. These map directly to Odoo res.partner fields: name, street/city/zip/country, phone, mobile, email, and date fields. Pearl custom dental properties (NHS number, medical alerts) become custom fields on res.partner.

Pearl treatment plans store procedure codes, tooth numbers, clinical notes, fees, and completion status linked to a patient. Odoo CRM has no native dental treatment model. Each treatment plan field (procedure, tooth number, clinical note, fee, status) requires a custom field on res.partner before migration. The treatment plan identifier links to the patient via x_treatment_plan_id custom char field.

Pearl appointments contain date, time, duration, operator, assistant, type, status, and notes linked to a patient. Odoo calendar.event stores start/datetime, duration, and description. contact_id on calendar.event links to res.partner. Operator and assistant resolve to res.users by name match; unresolved names are stored as x_operator_name and x_assistant_name char fields on the event.

Pearl clinical notes capture observations, diagnoses, and treatment details with a date and an associated operator. In Odoo, each note becomes a mail.message record attached to the patient’s res.partner (model='res.partner', res_id=partner_id). The note text is stored in the body field, the creating operator is saved via x_operator_name fallback, and the original timestamp is preserved in create_date, ensuring continuity for reporting and audit trails.

Pearl stores X-ray images, clinical forms, and consent documents linked to patient records. Odoo ir.attachment stores files with res_model='res.partner' and res_id pointing to the contact id. Binary files are re-uploaded to Odoo's filestore during migration. Inline images in clinical notes are extracted and stored as separate ir.attachment records.

Pearl supports custom properties beyond standard fields. Any Pearl custom property that has no Odoo equivalent (e.g. recall interval, referring practitioner, medical alert, insurance provider) is created as a custom field on res.partner with the appropriate type (char, text, date, float, selection) during the setup phase.

Pearl call logs and email records linked to patients map to Odoo mail.activity records on res.partner. Subject, description, date, and duration map as fields on the activity. The activity type_id resolves to 'Call' or 'Email' based on the Pearl engagement type. Unresolved users default to the Odoo system user.

Pearl tracks NHS recall intervals and re-care appointment dates as date fields on the patient record, often with system-generated reminders. Odoo CRM has no native recall model. The recall date migrates as x_recall_date custom date field on res.partner. Recalls for ongoing patient management must be rebuilt as Odoo automated activities or calendar alarms post-migration.

Pearl may record how a patient was referred (e.g. NHS referral, self-referred, dentist-to-dentist). Odoo CRM has a standard source_id field on crm.lead but not on res.partner. For patient-level referral tracking, a custom char field x_referral_source is created on res.partner and populated from Pearl's referral source field.

Pearl may store insurance provider names, policy numbers, and payment plan details linked to patients. Odoo accounting module (account.move, account.payment) handles invoicing and payments. Insurance details migrate as custom char fields on res.partner; payment records require separate mapping to Odoo account.move if payment history is needed.