Migrate from MOGO to Odoo CRM

MOGO patient records map directly to Odoo res.partner. Partner type (patient vs. company) maps to the partner's is_company flag. Individual patients get is_company=False; clinic or insurance contacts get is_company=True. MOGO custom properties on the patient record migrate as Odoo custom fields on res.partner.

MOGO appointment records map to Odoo mail.activity entries with activity_type_id set to 'Appointment' or a custom type. The scheduled date maps to date_deadline, and the MOGO practitioner user maps to Odoo res.users by email. Completed visit notes map to mail.message on the partner record.

MOGO treatment records hold procedure codes, tooth numbers, and treatment dates that have no native Odoo equivalent. We create custom fields on crm.lead (Procedure_Code__c, Tooth_Number__c, Treatment_Date__c) and link each treatment record to the patient partner via res_id on the custom model. If Odoo Clinic/Medical modules are installed, these map to the corresponding medical object instead.

MOGO insurance carrier contacts map to separate res.partner records with partner_latitude for classification. The relationship to the patient (insured_by, guarantor) is stored as a custom field on the patient partner record. Odoo's accounting module uses these for vendor bills if invoices are generated in Odoo.

MOGO has no native pipeline object — treatment stage labels (Initial Exam, In Progress, Completed) are custom pick-list values on the patient record. We create an Odoo crm.stage record per unique stage label, assign it to the default sales team or a custom team per MOGO location, and map the MOGO stage value to stage_id on crm.lead. Stage sequence and probability are configurable in Odoo after migration.

MOGO clinical notes and general notes map to Odoo mail.message records with message_type='notification' attached to the patient res.partner. Original author and create date are preserved in message_id, author_id, and create_date. Rich-text formatting in MOGO notes is converted to Odoo's HTML-safe body field.

MOGO file attachments (X-rays, consent forms, claim PDFs) are downloaded and re-uploaded to Odoo ir.attachment. Each attachment is linked via res_model='res.partner' and res_id pointing to the patient partner record. Binary content and original filename are preserved. Odoo's 25MB per-file limit applies; files larger than this are split or flagged for manual handling.

MOGO practitioner and staff user records map to Odoo res.users. Resolution is by email address. Unmatched MOGO users are flagged before migration — your Odoo admin either creates the res.users record first or assigns their MOGO records to a fallback owner. Inactive MOGO users migrate as inactive Odoo users to preserve historical ownership.

MOGO multi-location setups map each office to an Odoo crm.team record with the office address stored on the team's partner_id. If MOGO locations are also company entities (multi-branch), each maps to a separate res.partner with is_company=True and child contacts per location.

Any MOGO custom objects not covered above are exported as structured JSON and mapped to Odoo custom fields on the closest native object (res.partner, crm.lead). We deliver a schema plan listing the Odoo field name, type, and required flag for each custom MOGO property so your Odoo admin pre-creates the fields before the migration run.