Migrate from Bizstim Business Management Software to Odoo CRM

Bizstim Client records map to Odoo res.partner with contact_type set to contact. The client availability fields (minTime, maxTime, slotDuration, sessionLimit) transfer as structured custom fields on the partner record. Client status flags map to Odoo customer_rank values for segmentation. Address, phone, and email fields migrate directly using standard Odoo field names. We resolve practitioner_id links from the source so that any client-practitioner assignments can be stored as custom fields or notes in Odoo, since the native res.partner model does not have a direct practitioner assignment field outside the HR module.

Bizstim Practitioner records map to Odoo res.partner with is_company set to true and contact_type set to contact, since Odoo does not have a native practitioner object in the CRM module. The practitioner_id is preserved as the res.partner id. Practitioner wage settings (practitioner_wage) and payment rate configurations require a custom field (x_practitioner_wage or x_practitioner_rate) created in Odoo Settings > Technical > Custom Fields before migration. If the customer uses Odoo HR module, we alternatively map to hr.employee with res_partner_id linking; this is decided during scoping.

Bizstim Service records map to Odoo product.template with type set to service. The service cost maps to Odoo standard_price, and any session count (group_num) from the source becomes a custom field x_session_count on the product.template. Service status (active, archived) maps to Odoo active field. If the customer uses Odoo Sale app, we create product.product variants for service variations. The product.uom_id is set to unit(s) for services. We flag any services with practitioner-specific rates for custom field migration.

Bizstim Service_group_names table entries with group_id map to Odoo product.category. The group_id becomes category_id, and the hierarchy path is preserved as complete_name in Odoo's category tree. If nested service groups exist in Bizstim (group_id referencing a parent group), we reconstruct the full category parent_path in Odoo. We create product.category records before product.template import so that the category_id lookup is satisfied at insert time. This mapping is required before Services can be imported.

Bizstim Payment records map to Odoo account.move with move_type set to out_invoice (for invoices) or out_refund (for refunds). The payment amount and date transfer to amount_total and invoice_date respectively. Bizstim does not store a full accounting chart of accounts, so we create a default Receivable account on the customer res.partner and map all payment amounts against it. We import as draft invoices (state=draft) so that the customer's accountant can review and post them in Odoo Accounting before they affect financial reports. Currency field requires verification against Odoo's configured currencies list.

Bizstim Users endpoint records map to Odoo res.users by email match. We extract user login, name, and active status. Role and permission data from Bizstim (admin, practitioner, staff) maps to Odoo groups: practitioners become members of the Sales / User group, staff members map to internal user groups. If the Bizstim user has a linked practitioner_id, we create the corresponding res.partner record first and link via partner_id on res.users. Active status migrates directly. We do not migrate password hashes; users must complete an Odoo password reset flow post-migration.

Bizstim Staff records are queryable via GET and contain largely the same data as Practitioner records, differentiated by staff_id. We deduplicate Staff against Practitioner by matching staff_id to practitioner_id. The merged record maps to a single res.partner entry with is_company set to true and a custom field x_staff_role set to the original staff role string. If staff records contain billing rate information not present in the practitioner record, we preserve the higher value. This deduplication prevents duplicate partner records in Odoo.

Bizstim client availability windows (minTime, maxTime, slotDuration, sessionLimit) do not have a direct Odoo CRM equivalent since Odoo separates calendar scheduling from contact records. We map these to resource.calendar entries if the Odoo Calendar app is installed, or store them as structured custom fields on res.partner (x_availability_min_time, x_availability_max_time, x_slot_duration, x_session_limit) if only CRM is deployed. For service practitioner availability, we create resource.calendar.attendance records. This is a configuration migration, not a direct field copy, and requires the Odoo Calendar module to be active.

Bizstim Deal records map to Odoo crm.lead with type set to opportunity. The dealstage property maps to Odoo stage_id, which we configure in Odoo CRM > Stages before migration. Pipeline assignment from Bizstim maps to Odoo team_id (Sales Team). Closed-won and closed-lost dates map to Odoo's date_closed field. The deal amount becomes Odoo expected_revenue or list_price depending on whether product lines are attached. We use crm.lead because Odoo 16+ combines Lead and Opportunity into one model with a type switch.

Bizstim deal pipelines map to Odoo CRM stage configurations. Each Bizstim pipeline becomes a set of crm.stage records within a named team. Stage order and probability percentages migrate to sequence and on_change_stage_id probability values. We configure the pipeline via crm.team records in Odoo before migrating any crm.lead data, ensuring stage_id references are satisfied at insert time. Bizstim stage names are preserved as stage names unless the customer requests standard Odoo stage naming (New, Qualified, Proposition, Won, Lost).

Bizstim client notes and free-text fields migrate to Odoo mail.message records linked to the res.partner via model=res.partner and res_id pointing to the partner id. The note body transfers as body field in HTML format. mail.message is the Odoo standard for all conversation history, notes, and internal communication on a partner record. We preserve the original creation date as date for chronological ordering. Binary attachments associated with notes must be identified during scoping and exported separately as they are stored outside the standard client API response.

Bizstim binary attachments stored within client or practitioner records migrate to Odoo ir.attachment linked via res_model=res.partner and res_id pointing to the target partner id. Attachment name maps to name field, binary content maps to datas field as base64-encoded bytes. External URLs stored in Bizstim convert to Odoo external attachment records with type=url. We extract attachments during the client and practitioner extraction phases and store them in a temporary file system before batch insertion via Odoo's ir_attachment XML-RPC endpoint. This mapping requires elevated permissions in Odoo.