Migrate from Bp Premier to Odoo CRM

Clinical measurement and prescription data have no Odoo CRM equivalent

BP Premier stores blood pressure readings, pulse rates, BMI, medication lists, and prescription histories as clinical properties on patient records. Odoo CRM has no native clinical data model — there is no crm.lead-level vital-sign field, no prescription object, and no clinical measurement history table. FlitStack migrates the most recent blood pressure systolic and diastolic readings and a text summary of medications as custom fields on res.partner, but the full clinical measurement time-series and prescription detail require either a custom Odoo clinical module or a separate document export. Practices expecting a complete clinical record in Odoo CRM will be disappointed — this migration covers patient demographics and commercial relationships, not clinical care data. The scope must be agreed in writing before migration commits to avoid post-migration disputes over data completeness.

BP Premier healthcare identifiers (HPI-I, IHI) require custom field setup in Odoo before migration

Australian healthcare provider identifiers (HPI-I for practitioners, IHI for patients) stored in BP Premier have no native Odoo field. Odoo CRM does not include a healthcare identity model — the platform is built for commercial sales workflows, not the Australian health identifier scheme used by Medicare, My Health Record, and PRODA. FlitStack creates custom Char fields (HPI_I__c, IHI__c) on res.partner before data loads, but Odoo's developer mode or a custom module must be enabled to add fields with specific technical names. If the Odoo instance is on Odoo Online (SaaS), custom field creation may require partner assistance or an Odoo Studio license. This step is a pre-migration dependency that must be resolved before the field mapping runs.

BP Premier appointment books do not translate into Odoo calendar events without a scheduling module

BP Premier appointment records capture provider, date/time, appointment type, and clinical outcome for each patient visit. Odoo CRM has crm.lead for pipeline management and res.partner for contact data, but it has no native appointment book or scheduling calendar that maps directly from a BP Premier appointment record. Odoo's calendar module (calendar.event) exists but requires a separate integration to link events to res.partner records. FlitStack converts BP Premier appointment data into activity summaries on crm.lead and date-custom fields on res.partner, but the appointment book structure — with provider availability, room allocation, and recurring schedules — is not replicated. Practices that rely on BP Premier's appointment book for scheduling will need an Odoo scheduling module (Odoo Appointments or a third-party booking app) as a replacement.

Odoo res.partner and crm.lead ownership requires pre-existing res.users accounts

BP Premier user IDs and provider identifiers must be matched to Odoo res.users records for activity attribution and lead ownership. Odoo requires that every crm.lead has a user_id (owner) and that the res.users records already exist in the database before the migration script assigns them. If BP Premier has providers or staff members who do not yet have Odoo login accounts, FlitStack flags them as unmatched and assigns their records to a fallback Odoo user. The fallback approach preserves data ownership in the migration but may require post-migration re-assignment of leads to the correct owners. This is especially relevant for practices where BP Premier has more registered users than the planned Odoo CRM seat count.

Odoo accounting module requires chart-of-accounts configuration before billing migration

BP Premier billing records (invoices, payments, itemised accounts) map to Odoo's account.move and account.move.line objects. However, Odoo requires a configured chart of accounts, tax codes, and journal definitions before any accounting records can be created. If the Odoo instance has not run the initial accounting setup wizard (Settings > Accounting > Initialize Accounting), FlitStack defers billing data migration until accounting configuration is complete. Billing records that cannot be migrated on day one are exported as a CSV package for manual entry or post-configuration import, with the migration audit log noting the deferral reason for each record.