Migrate from Nookal to Odoo CRM

Nookal patient records map directly to Odoo res.partner contacts. We set a custom is_patient__c boolean field to distinguish patient partners from supplier/company partners in Odoo. Address fields (street, city, state, zip, country) map field-for-field. Medicare number and date-of-birth fields migrate as custom columns on the partner record.

Each Nookal practitioner becomes an Odoo res.users account so appointments can be assigned to the correct staff member. Practitioner email, name, and active status map directly. If the Nookal practitioner is also a patient, we create both a user record and a partner record linked by partner_id.

Nookal appointments do not map to Odoo calendar events (crm.event) because Odoo's native calendar is tied to project/resource scheduling rather than patient appointment history. Instead, we create crm.lead records for each appointment with the appointment date as date_deadline, practitioner as user_id, patient as partner_id, and service type stored in a custom appointment_type__c field. The lead_type field is set to 'opportunity' to indicate a booked appointment rather than a sales prospect.

Nookal invoices migrate to Odoo account.move records with move_type='out_invoice'. Invoice number maps to name, total amount to amount_total, and status (draft/sent/paid/cancelled) maps to state. Line items (service descriptions, Medicare item numbers, quantities, unit prices) migrate to account.move.line records with the appropriate account_id for revenue recognition.

Nookal Medicare and DVA claiming data has no native equivalent in Odoo. We create custom fields on the account.move model to capture the full claim lifecycle: claim_status__c stores the submission state using a picklist of pending, submitted, approved, or rejected values. Provider number, Medicare item number, and bulk-bill indicator fields are added as provider_number__c, item_number__c, and bulk_bill__c respectively. The patient res.partner record receives separate custom fields for medicare_number__c and dva_number__c sourced from Nookal patient records.

Nookal insurance providers map to Odoo res.partner records with partner.role set to 'insurance_company' via a custom partner_type__c field. If the insurance provider is also a referring practitioner, we link it to the patient as a child partner via partner_id. Insurance policy numbers and provider IDs migrate as custom fields on the patient partner record.

Nookal records referral sources such as advertising channels, GP referrals, and word-of-mouth recommendations using a label stored on the patient or appointment record. These labels map to Odoo's crm.lead.source_id lookup field on the opportunity. We create corresponding crm.tracking.mixin.source records in Odoo when the referral label does not already exist in the system, using the exact Nookal referral label as the source name for consistent reporting across both platforms.

Nookal clinical notes attached to patient records have no direct Odoo equivalent. We create a custom clinical_note__c field (html type) on res.partner to store the most recent clinical note, and attach historical note content as mail.message records linked to the partner for full audit history. Treatment plans and appointment summaries migrate as structured text in these fields.

Nookal practices operating across multiple locations each correspond to a separate Odoo res.company record, enabling independent fiscal year configuration, chart of accounts setup, journal assignments, and practitioner team assignments per site. For locations requiring inventory capabilities, we generate matching stock.warehouse records linked to each company entity, providing complete operational separation while maintaining cross-company reporting options within Odoo's multi-company framework.

Nookal custom fields on patients (e.g., emergency contact, next of kin, NDIS plan number) map to Odoo custom fields on res.partner created during the Odoo schema setup phase. Field types are matched (text, date, boolean, selection) and validation rules are preserved as Odoo field constraints where supported.

Nookal SMS history and patient communications map to Odoo mail.message records linked to the res.partner. Message direction (inbound/outbound), timestamp, and content are preserved. Odoo's mail.channel integration can recreate a patient communication thread if the practice uses Odoo's Live Chat or Discuss module.

Nookal's Xero and QuickBooks sync configuration (chart of accounts mapping, tax settings, invoice numbering conventions) has no Odoo equivalent and must be rebuilt in Odoo's accounting app configuration. We export the source mapping as a reference document for the Odoo accountant.