Migrate from Pulse Digital Clinic to Odoo CRM

Pulse patients map directly to Odoo partners. The patient record fields (name, email, phone, address) become res.partner fields. The Pulse patient_id is preserved in a custom Char field (x_studio_patient_id) on the partner for traceability. Odoo partners can be marked as 'is_company'=False for individuals.

Odoo res.partner has no native date_of_birth field. We create x_studio_date_of_birth as a Date field on the partner model. The value transfers directly from Pulse. This field appears in Odoo's partner form view under the 'Personal Information' tab for medical-reference use.

Blood group has no Odoo standard equivalent. We create x_studio_blood_group as a Selection field with options A+, A-, B+, B-, AB+, AB-, O+, O-. The pick-list values map value-by-value from Pulse. This is required for clinic compliance and emergency reference. The field appears in the partner form view under the custom medical information section. If Pulse stores an unrecognized blood group value not in the standard pick-list, we flag it for manual review and store it in a free-text fallback field.

Allergy information stores as a Text field (x_studio_allergy_notes) on res.partner. Because Odoo has no medical schema, long-text fields hold the structured or free-text allergy data exported from Pulse. If Pulse stores structured JSON, we parse and flatten to newline-delimited text for Odoo's Text widget.

Pulse appointments (date, time, physician, type, status, notes) become Odoo crm.activity records. The activity_type_id maps from Pulse appointment type: 'Consultation' → Odoo's 'Call' type; 'Follow-up' → 'Meeting'; 'Procedure' → 'To Do'. The partner_id foreign key links the activity to the patient-turned-partner. The physician becomes the activity's user_id (matched by email against Odoo users).

Pulse appointment status values ('Scheduled', 'Completed', 'Cancelled', 'No-Show') map to Odoo crm.activity.stage_id pick-list values. We create a custom stage sequence in Odoo matching the Pulse lifecycle. Completed appointments set the activity as 'done' state; cancelled ones are marked accordingly. The mapping preserves the original Pulse status string in a custom Char field for audit reference. If Pulse adds a custom status value not in the standard set, we create a corresponding stage in Odoo before migration.

Pulse prescriptions have no Odoo CRM equivalent — Odoo has no native prescribing module. We export prescription PDFs or structured prescription data from Pulse and re-upload as ir.attachment records linked to the partner. The attachment name carries the prescription date and physician name for searchability.

Pulse EMR data (chief_complaint, diagnosis, treatment_plan) maps partly to custom Char/Text fields (x_studio_chief_complaint, x_studio_diagnosis) on res.partner for structured data, and to ir.attachment for scanned clinical note PDFs. The split is based on what Pulse exports as structured fields vs. file attachments.

If Odoo Accounting module is active, Pulse billing records become account.move entries (Invoices) with the partner linked. If only CRM is deployed, billing data stores in custom fields on res.partner: x_studio_billing_status, x_studio_last_bill_date, x_studio_outstanding_balance. The merge is driven by your Odoo edition selection before migration.

Pulse campaign management (patient outreach, health camp promotions) has no direct Odoo CRM campaign equivalent in the base CRM app. We map campaign records to crm.activity entries with a custom x_studio_campaign_name field, so each outreach touchpoint is linked to the patient partner and timestamped for reporting.

Pulse chat/messaging history stores in a platform-specific format. Odoo CRM has mail.message linked to res.partner, but Pulse message format may not be structurally compatible. We export message logs as ir.attachment text files linked to the partner, preserving the conversation thread for patient history access.

Physicians and staff from Pulse are matched to Odoo res.users by email address. Unmatched physicians are flagged pre-migration — your Odoo admin either creates a user record or assigns the patient/activity to an existing fallback user. The OwnerId on the res.partner record is set from the matched res.users id.