Migrate from The Clinic Place to Odoo CRM

The Clinic Place patient record maps directly to Odoo res.partner. Core demographics (name, date of birth, contact details, address) map field-by-field to res.partner columns. Medical properties that have no Odoo equivalent are stored as custom fields on res.partner using the x_ prefix convention. The Clinic Place patient ID is preserved as a custom field (x_source_patient_id) for traceability and delta-run de-duplication.

Any patient property in The Clinic Place that does not have a direct Odoo res.partner equivalent (insurance carrier, emergency contact, medical alert flags, referral source) is created as an Odoo custom field via ir.model.fields before migration. Each custom field uses the x_clinic_ prefix and the appropriate field type (char, selection, boolean, date). Custom field creation is delivered in the pre-migration schema setup step.

The Clinic Place stores clinical notes as structured text entries within the patient record. Since Odoo has no native clinical note object, we convert each clinical note entry into an Odoo ir.attachment record linked to the corresponding res.partner via res_model='res.partner' and res_id pointing to the partner ID. Notes are stored as UTF-8 text files with .txt extension and original create timestamps preserved in the attachment's create_date. Your Odoo admin can alternatively configure a mail.message thread on the partner for a conversational note structure.

Patient chart documents, signed forms, and diagnostic images attached to a patient record in The Clinic Place re-upload to Odoo ir.attachment with res_model='res.partner' and res_id set to the migrated partner ID. The original filename and file extension are preserved. Odoo's ir.attachment stores files in its filestore or on a linked storage backend (local, S3, or Odoo.sh cloud storage). Large chart files may require increasing the Odoo attachment size limit before migration.

The Clinic Place appointment records (date, time, practitioner, patient, appointment type, status, duration) map to Odoo calendar.event. The practitioner maps via email match to Odoo res.users (calendar.event's user_id). The patient maps to res.partner via the previously migrated partner ID stored as a custom field. Appointment status (confirmed, cancelled, completed) maps to calendar.event's state field (open, cancelled, done). All-day events and multi-day appointment series are supported.

The Clinic Place's digital queue management has no direct Odoo CRM equivalent. We preserve digital queue entries as Odoo crm.lead records with a custom stage named 'Queue' and a custom field (x_queue_position__c) storing the queue position. This gives your team a searchable, reportable record of each queue entry without rebuilding the queue UI. Queue entry timestamps map to crm.lead's create_date.

The Clinic Place invoices migrate to Odoo account.move with type='out_invoice' for patient-facing invoices. The partner_id links to the migrated res.partner. Invoice line items become account.move.line records with product_id, name, quantity, price_unit, and tax_ids mapped per line. Payment status from The Clinic Place (paid, partially paid, outstanding) maps to account.move's payment_state field. Invoice numbers are preserved in the name field and the x_source_invoice_id custom field.

Patient payments from The Clinic Place map to Odoo account.payment records linked to the corresponding account.move via the reconciled_entry_ids relation. Payment amount, payment date, and payment method from The Clinic Place map to account.payment fields (amount, date, journal_id). If The Clinic Place records partial payments against a single invoice, Odoo's partial reconciliation model handles multiple payment records per invoice.

The Clinic Place practitioner records map to Odoo res.users (for login and calendar access) and an associated res.partner record (for contact details and address). The practitioner name and email from The Clinic Place are used to match and resolve ownership on migrated records — appointments, clinical notes, and invoices are assigned to the matched res.users by email. Unmatched practitioners are flagged before migration so your Odoo admin can create the res.users account first.

The Clinic Place practice-level settings (clinic name, address, phone, logo, branding) map to Odoo res.company. During migration, we configure the primary res.company record with the clinic's name and address so that invoices, quotes, and documents generated in Odoo carry the correct clinic branding. Multi-location clinics map to additional res.company records, with patient records tagged to the appropriate company via res.company_id on res.partner.

Insurance carrier and payer records from The Clinic Place migrate as res.partner records tagged with the 'Insurance' partner category (ir.model.fields.category). Carrier-specific properties (payer ID, plan type, coverage details) store as custom fields on the res.partner record (x_insurance_payer_id, x_plan_type, x_coverage_level). Patient insurance assignments link to the carrier partner via a custom Many2one field on the patient res.partner.

The Clinic Place referral source records merge into two Odoo objects: the referring provider or entity becomes a res.partner with category 'Referral', and the referral source label (e.g., 'Physician Referral', 'Website Form') is mapped to the source_id field on crm.lead for patients who arrived as referrals. If The Clinic Place tracks referring practitioner details, those map to the referral partner's address and phone fields.