Migrate from Core Practice to Odoo CRM

Core Practice patient records map directly to Odoo res.partner. Name fields split into partner name components; contact fields map to partner address and communication fields including email and phone. Insurance carrier data becomes custom fields on the partner record. Original patient ID is preserved in Source_System_ID__c for traceability during migration and future delta-sync operations.

Core Practice treatment plans and recall schedules merge into Odoo crm.lead records representing patient opportunities. Each planned treatment becomes a lead description entry with original provider assignment preserved as user_id lookup. Recall intervals and treatment stages translate to custom fields on the lead record for ongoing patient engagement tracking.

Core Practice appointments map to Odoo mail.activity records linked to the corresponding crm.lead or res.partner. Activity type, scheduled datetime, and assigned provider (user_id) are preserved through the migration; procedure codes map to activity type names. Original appointment outcomes and status values convert to mail.activity state values.

Core Practice treatment plan line items including procedure code, tooth number, and estimated cost are concatenated into the Odoo crm.lead description field as structured text entries. Planned treatment dates become activity scheduled_dates on the linked lead record for follow-up tracking and clinical workflow management.

Core Practice insurance carrier references have no direct Odoo equivalent in the standard res.partner model. We create an Insurance_Carrier__c custom Char field on res.partner and migrate the carrier name and policy reference as string values for insurance verification workflows and billing integrations.

Core Practice referral source exists as a contact within the patient record structure. We migrate referring dentist names as a custom Referring_Dentist__c Char field on res.partner. Full referral contact records can be created as separate res.partner entries if your practice requires complete referral network tracking and communication history.

Core Practice clinical notes map to Odoo mail.message records attached to the corresponding crm.lead for clinical context and audit trail purposes. Original create date and author user are preserved as mail.message date and author_id. Note body is stored as mail.message body text for practitioner review.

Core Practice billing records map to Odoo account.move entries if the Odoo Accounting app is installed and configured. Without Accounting installed, billing data exports as a structured reference file and is preserved as custom fields on the linked res.partner for future reconciliation when the Accounting module is activated.

Core Practice provider and dentist records map to Odoo res.users for activity assignment and team membership. Email addresses are matched for user resolution across systems; unmatched providers are flagged in a pre-migration report for team assignment before data loads commence.

Core Practice location or office identifier maps to Odoo crm.team records representing each physical practice location. Team members including dentists, hygienists, and administrative staff are assigned as team member_ids derived from res.users for multi-location pipeline management and reporting.

Core Practice recall intervals such as 6-month cleaning have no Odoo native equivalent in the standard CRM model. We create a custom Recall_Schedule__c field on crm.lead and schedule follow-up mail.activity records with the calculated recall date for patient retention and preventive care follow-up workflows.

Any custom intake fields in Core Practice including medical history, consent forms, and special notes require Odoo custom fields created via Settings > Technical > Models. We document every custom field definition including field type, validation rules, and display labels. A setup plan is created before data loads to ensure the destination schema accommodates all patient intake information.