Migrate from PracticeHub to Odoo CRM

PracticeHub patient maps to Odoo res.partner, which is the unified model for contacts and companies. Standard fields (name, email, phone, address) migrate directly. Healthcare-specific fields — date_of_birth, blood_type, allergies, emergency_contact — map to custom fields on res.partner that must be pre-created in Odoo before migration data loads.

Patient first_name, last_name, email, phone, mobilephone, address_line_1, address_line_2, city, state, zip, and country map directly to Odoo res.partner fields. The address stored as structured fields in PracticeHub maps to Odoo's street, street2, city, state_id, zip, and country_id fields — address components must be parsed if PracticeHub exports as a single string.

PracticeHub appointment records map to Odoo crm.lead entries with the patient linked via res.partner. Fields like visit_type, visit_status, and appointment_date become custom fields on the lead or are encoded in the lead name. The appointment_time field is preserved as a note or custom datetime field. Lead stages (New, In Progress, Completed, Cancelled) are mapped value-by-value to Odoo crm_stage entries.

The practitioner_id and practitioner_email on a PracticeHub appointment map to an Odoo res.users record matched by email. Unmatched practitioners are flagged before migration — the admin either invites them to Odoo or assigns their appointments to a fallback user. This ensures activity ownership resolves correctly in Odoo after migration.

Prescription records (medication_name, dosage, frequency, prescribing_doctor, prescription_date) do not have a native equivalent in Odoo CRM. FlitStack creates a prescription_summary custom field on res.partner and stores the structured prescription data as a JSON-serialized note or text field. If the source has PDF prescriptions, they are downloaded and re-uploaded as ir.attachment records linked to the patient partner.

PracticeHub documents (title, description, file_url) and files (file_name, file_url, file_type) map to Odoo ir.attachment. The ir_attachment record requires res_model set to res.partner and res_id set to the partner id so the file attaches to the correct patient record in Odoo. FlitStack downloads files from PracticeHub URLs and re-uploads them as binary content to ir_attachment — this step is required because PracticeHub stores files externally.

PracticeHub clinic_location stored as a value on patient records maps to a custom pick-list field (Clinic_Location__c) on res.partner in Odoo. If multiple clinic locations exist, a value-mapping table maps each PracticeHub location name to the corresponding Odoo clinic identifier. This prevents clinic data from being lost when patients have a location attribute in the source.

PracticeHub referring_doctor and referring_doctor_email fields have no Odoo CRM native equivalent. These migrate as custom fields on res.partner. If the referring doctor is an existing Odoo contact, the field can store the partner id; otherwise it stores the free-text name for manual reconciliation post-migration.

PracticeHub insurance_provider and policy_number map to custom text fields on res.partner in Odoo. If the insurance company exists as a company record in Odoo, the insurance_provider field can store a res.partner id linking to the insurer as a related company. This preserves the carrier relationship for billing workflows in Odoo.

PracticeHub medical_history is a free-text or structured field with no Odoo CRM native equivalent. It migrates as a long-text custom field on res.partner (medical_history__c) for searchability. If medical history is stored as a PDF or structured document in PracticeHub, it is downloaded and re-attached as an ir.attachment record linked to the patient partner, preserving the original document.

PracticeHub allows custom fields per patient object — any field not covered by the standard mappings above requires a corresponding custom field on res.partner in Odoo. FlitStack audits the full PracticeHub field list during pre-migration, generates a custom-field creation checklist for the Odoo admin, and maps each field with type-aware handling (text, date, pick-list, boolean, integer) before data loads.