Migrate from tab32 to Odoo CRM

tab32 Patient maps 1:1 to Odoo res.partner. The patient name, email, phone, address, and date of birth translate directly without transformation. Clinical charting properties such as tooth charts, perio exam data, and CDT codes become custom fields on the res.partner record. These custom fields must be defined in Odoo before migration data loads to ensure all clinical properties are visible in the standard Odoo interface.

tab32 Appointment records map to Odoo mail.activity entries with activity_type_id set to 'scheduled', user_id matched to the assigned doctor, and date_deadline corresponding to the appointment date. Operatory identifier and chair data from tab32 migrate as custom fields on the mail.activity record since Odoo does not natively support operatory or treatment-room semantics in its activity model.

tab32 Treatment Plans map to Odoo crm.lead (opportunity) records. Treatment status values including Proposed, Scheduled, Completed, and Cancelled map to corresponding crm.lead stage_id values in Odoo. Procedure codes (CDT) and tooth identification numbers become custom char fields on the lead to preserve clinical reference data that has no native Odoo equivalent.

tab32 clinical notes including tooth chart entries, perio examination results, and oral condition observations merge into mail.message records attached to the res.partner patient record. The original examination date and provider information are preserved as message metadata, maintaining the audit trail for clinical documentation across the migration.

tab32 insurance carrier names and policy references map to Odoo res.partner records with partner_type set to 'company' to represent the insurer entity. Patient-to-insurer relationships utilize res.partner relation fields or a dedicated custom many2one field on the patient partner record. Each unique carrier must pre-exist as a partner before patient records migrate.

tab32 billing rows map to Odoo account.move (invoices) and account.payment records linked to the patient res.partner. Claim status information and insurance write-off amounts become custom fields on the account.move record. Payment reconciliation uses Odoo's native reconciliation tools after migration completes.

tab32 provider records map to Odoo res.users by matching email addresses. Doctor specialty designations and NPI numbers migrate as user-level custom fields on the res.users record. Provider users must exist in Odoo before patient and appointment records can reference them via the user_id field.

tab32 office and location data maps to res.company in multi-company Odoo configurations. Each distinct office becomes its own Odoo company so that records, users, and financial reporting are properly scoped by location. Location-specific operatory information and equipment identifiers become custom fields on the company record.

tab32 completed treatment history maps to closed crm.lead records with stage set to Completed, plus individual mail.activity entries for each treatment visit. Original treatment dates and provider assignments are preserved in the migrated records. Historical records are appended after current active treatment plans in the migration sequence.

tab32 imaging file references including X-rays, intraoral photographs, and panoramic images map as Odoo ir.attachment records linked to the corresponding res.partner patient record. Imaging metadata such as modality type, body region, and tooth region become custom fields on the attachment record. Image files are re-uploaded to Odoo's filestore during the migration process.