Migrate from coreplus to Odoo CRM

CorePlus clients map 1:1 to Odoo res.partner records. We set type='contact' for individuals and parse the business_name field to determine if a separate company partner should be created with the client as a child contact. All CorePlus client properties migrate as partner fields.

When a CorePlus client has a non-empty business_name value, FlitStack creates a parent res.partner with type='company' using the business name, then creates the individual client as a child contact under it. This replicates the CorePlus company contact relationship in Odoo's hierarchical partner model.

CorePlus practitioners are matched by email to Odoo res.users. Each practitioner with an active CorePlus status creates an active Odoo user. If a matching Odoo user does not exist, FlitStack creates the user with the practitioner email and flags it for your admin to set the password and assign security groups.

Practitioner contact details (email, phone, mobile) also migrate as res.partner records so the practitioner appears in Odoo's contact list for reporting and marketing purposes. This creates a parallel partner record alongside the res.users record, linked by matching email. The partner record inherits the practitioner's address and company affiliation from CorePlus if those fields are populated.

CorePlus appointment records map to Odoo calendar.event with start_datetime and stop_datetime preserved from the source. The practitioner_id resolves to a res.users many2one; client_id resolves to a res.partner many2one. Service type notes and appointment status migrate as event description text or custom event fields.

CorePlus appointment status values (scheduled, confirmed, completed, cancelled, no-show) map to Odoo calendar.event state values (open, cancelled, done). The mapping is defined during the migration plan phase and validated against Odoo's default state picklist. Any CorePlus statuses that don't have a direct Odoo equivalent are mapped to the closest available state, with a note recorded in the migration audit log for your admin to review post-migration.

CorePlus service types export as product.product records in Odoo with type='service'. The name, fee, and stock_level fields map to name, list_price, and qty_available respectively. If the service type has a category, we create a product.category in Odoo and assign it.

CorePlus invoice records migrate as Odoo account.move entries with move_type='out_invoice'. The client_id resolves to the res.partner commercial_partner_id, line items derive from service_type references, and total amount maps to amount_total. Payment state is set based on CorePlus invoice status. If a CorePlus invoice has multiple payments applied, FlitStack creates corresponding account.payment records linked to the invoice.

CorePlus referrer records (referring practitioners or sources) have no direct Odoo CRM equivalent. FlitStack migrates referrer names as res.partner tags using Odoo's tag system (res.partner.category). These tags are visible on the contact form and filterable in Odoo pipeline views. The original referrer type (practitioner vs. source) is preserved as a tag prefix so your team can distinguish between referral sources in reports.

Any CorePlus client custom fields not matching standard Odoo res.partner fields are created as custom fields via Odoo Studio before migration. FlitStack reads the field type from the CorePlus instant-data-backup CSV header and creates the matching Odoo field type (char, selection, float, boolean, date, etc.).

CorePlus appointment custom fields (e.g., intake notes, cancellation reason, room number) are created as custom fields on calendar.event in Odoo before data loads. Notes text longer than Odoo's default char limit is stored in the event description field or a custom text field.

The CorePlus instant-data-backup CSV is the primary extraction path when API rate limits are a concern. FlitStack parses each sheet (clients, practitioners, appointments, invoices, service_types) and routes rows to the appropriate Odoo model. The CSV is re-read as a structured data source, not a raw file dump — field headers are matched to Odoo field names during the mapping phase.