Migrate from Zedmed to Odoo CRM

Zedmed patient records map to Odoo res.partner contacts. Patient name, date of birth, Medicare number, DVA number, address, and phone are migrated as standard contact fields. Each patient's primary practitioner in Zedmed resolves to an Odoo user by email match.

Medicare number, concession card type, HICAPS fund, and bulk-billing flag have no native Odoo CRM equivalents. We create x_medicare_number, x_concession_type, x_hicaps_fund, and x_bulk_billing_flag custom fields on res.partner to preserve this billing context for downstream accounting reconciliation. These fields are populated during the migration run and remain editable in Odoo after go-live.

Zedmed appointments with practitioner, start time, duration, appointment type (standard, long, procedural), and status map to Odoo calendar.event records linked to the patient res.partner. DNA (did not attend) status is stored as a custom field on the calendar event for reporting purposes.

Zedmed appointment type categories (standard, long, procedural, telehealth) map to Odoo mail.activity.type records. Each activity type carries the default Odoo duration and responsible-user setting. Original appointment type names are preserved as the activity type description. This preserves the original scheduling context for future reporting and workflow triggers in Odoo.

Zedmed payers are not native Odoo CRM contacts — they are billing entities. We map them to custom res.partner records of type 'payer' with x_payer_type (Medicare, DVA, WorkCover, TAC, Private, HICAPS) so that Odoo invoices can reference the correct payer. Medicare and DVA are modelled as government payers; WorkCover and TAC as third-party liability payers.

Zedmed MBS item codes (e.g. 23, 36, 44) and associated fees per payer are mapped to Odoo product.product records with the item code stored as x_mbs_item_code on the product. Invoice lines reference these products so billing history is queryable in Odoo reporting. Fee schedule tier values (P1/P2/P3, bulk-billing rates) are stored as custom fields on the product.

Zedmed billing invoices with status (paid, unpaid, claimed, rejected) map to Odoo account.move records. Claimed-to-Medicare status is stored as a custom field on the invoice. Original invoice number from Zedmed is preserved as x_source_invoice_ref for audit traceability. This ensures full traceability of billing records across systems after go-live.

Zedmed clinical encounter notes contain sensitive health information and cannot be migrated to a CRM platform without explicit patient consent and clinical governance review. We flag these as not migratable in the migration plan. Practices should retain clinical notes in Zedmed or a dedicated clinical records system and link patients via the x_source_zedmed_id field for cross-referencing.

Zedmed practitioner records (name, provider number, specialty) map to Odoo res.users by email match where an email exists, or by name lookup where email is absent. Zedmed provider numbers are stored as x_provider_number on the Odoo user record for Medicare claiming traceability.

Zedmed referral information (referring doctor name, referral date, expiry date) maps to a custom field set on the patient res.partner: x_referral_doctor_name, x_referral_date, x_referral_expiry. The referring practitioner is stored as a separate res.partner contact of type 'referrer' to allow Odoo to track referral source analytics.

Zedmed recall rules (e.g. 6-month diabetes check, annual health assessment) become Odoo scheduled activities with a custom x_recall_type field and custom x_recall_interval field. The activity is linked to the patient res.partner and queued to the responsible practitioner user on the recall due date.

Zedmed file attachments (referral letters, consent forms, pathology results) that are stored outside of clinical notes are re-uploaded to Odoo's ir.attachment model and linked to the corresponding res.partner record. File size limits per Odoo configuration apply (default 25MB per file).