Migrate from Quanum Practice Management to Odoo CRM

Quanum patient records migrate to Odoo res.partner as contact-type records. Fields including first_name, last_name, date_of_birth, social_security_number, address, email, and phone map directly to Odoo's standard partner fields. We preserve the Quanum patient_id as external_identifier on res.partner for traceability and delta-run de-duplication. The Access database treats patient as the central entity with foreign-key links to appointments, insurance records, and providers.

Insurance records attach to a patient as a one-to-many relationship in Quanum. Each insurance carrier (Carrier Name, Member ID, Group Number, Plan Type, Subscriber Relationship) is stored as a custom field on the patient's res.partner record in Odoo. The carrier itself can optionally be created as a separate res.partner (company type) and linked via a many2one field if the practice wants to track carrier contact information separately.

Quanum appointments become Odoo CRM leads (opportunities). The appointment_id is stored as a custom field (x_quanum_appointment_id) on crm.lead. Appointment type (New Patient, Follow-up, Procedure, etc.) maps to a custom selection field. Scheduled datetime becomes the expected_closing_date on the lead or a custom scheduled_date field. Appointment status (Scheduled, Completed, No-Show, Cancelled) is mapped to Odoo pipeline stages — teams configure the stage names to match their workflow. Provider is assigned to the lead's user_id by email match against Odoo users.

Providers (physicians, nurse practitioners, referring doctors) migrate to res.partner as contact-type records. The provider's name maps to partner name, NPI number to a custom NPI field (x_npi), and specialty to a custom specialty field. Referring doctors are flagged with a custom is_referring_doctor boolean field so the practice can filter contacts by role. Provider-user assignments in Quanum map to Odoo user accounts by email match.

Insurance carriers appear as distinct objects in Quanum's billing module. We map them to res.partner (company type) in Odoo so the practice can maintain carrier contact information, addresses, and plan details separate from patient records. Carrier records can then be linked to patient insurance custom fields via a many2one relationship.

Clinical notes attached to an appointment in Quanum are stored as text in the appointment note field. We map these to crm.lead.description for short notes or attach them as ir.attachment records linked to the lead for longer structured content. Odoo does not have a native clinical note equivalent — this is a field-level migration choice the practice confirms before migration.

Quanum stores CPT and HCPCS procedure codes on appointments. Odoo CRM has no native procedure code field. We create a custom Char or Text field (x_procedure_codes) on crm.lead and populate it with the pipe-delimited list of codes from the Quanum appointment record. If the practice needs structured code tracking, a separate product or custom crm.tag can be configured post-migration.

ICD-10 diagnosis codes stored in Quanum appointments map to a custom field (x_diagnosis_codes) on crm.lead in Odoo. The field is created as Char type to accommodate multi-code entries. If the practice wants to filter leads by diagnosis category, a custom selection field with the most common ICD chapters can be added to crm.lead after migration.

Quanum patient records include structured allergy and condition fields. Odoo res.partner has no native equivalent. We create x_allergies (Text) and x_conditions (Text) custom fields on res.partner and populate them from the Quanum patient record. The practice may want to expand this to a one2many health_record model in Odoo if the data volume is high.

Documents attached to Quanum appointments (lab results, referral letters, imaging) are exported as files. We re-upload them to Odoo as ir.attachment records linked to the corresponding crm.lead. File size limits in Odoo's file store apply; large files may require Odoo configuration adjustment before migration.

Lab order results in Quanum are clinical documents with structured data. Odoo CRM has no native lab result object. We attach lab result PDFs to the corresponding crm.lead as ir.attachment and store key result metadata (order date, result status, ordering provider) in custom fields on the lead. Full lab result interpretation requires Odoo's optional Inventory or Manufacturing modules, which are separate from CRM and require additional configuration.

Quanum links each patient to a primary care provider via a foreign key. We store the linked provider's Quanum ID in a custom field (x_primary_care_provider_id) on the patient's res.partner. Once the provider records are also migrated to res.partner, this ID can be used to create a many2one link between the patient and their assigned provider in Odoo.