Migrate from Gensolve Practice Manager to Odoo CRM

Gensolve has no self-service API — export is a manual file-archive process

Gensolve Practice Manager does not expose a self-service REST or GraphQL API for data extraction. Instead, Gensolve support generates a ZIP archive containing your database export on request — you must contact your account manager and wait for the archive to be produced. This means FlitStack cannot initiate an automated pull. We coordinate with your Gensolve account manager to receive the archive, decompress it, and stage the data before Odoo import. The manual handoff point is a scheduling risk on the Gensolve side — account manager availability and data extraction turnaround time add unpredictable days to the project plan. We recommend opening the export request with Gensolve at discovery kickoff to avoid this delay.

Odoo has no native clinical notes object — treatment notes require custom field and attachment strategy

Gensolve stores clinical SOAP notes, treatment notes, clinical correspondence, and practitioner observations as first-class records in its schema. Odoo CRM has no clinical-note object — crm.lead and res.partner do not include clinical content fields natively. FlitStack migrates clinical note content as a long-text custom field (x_clinical_notes) on res.partner, preserving the note body, note type, and original create date as companion custom datetime fields. For extensive historical note archives exceeding 10,000 characters per client, we generate PDF exports from Gensolve and attach them as ir.attachment records linked to the partner. You should decide before migration whether practitioners will enter new clinical notes in Odoo custom fields (low complexity) or whether your Odoo implementation will add a clinical-notes module from the Odoo Apps Store — this decision affects the final field-mapping plan.

Gensolve Xero accounting integration breaks — transactions cannot be migrated to Odoo Accounting

Gensolve Practice Manager integrates with Xero for invoicing, billing, and payment recording. Gensolve does not export Xero transaction data in a format that maps cleanly to Odoo's account.move schema — the chart of accounts structures, tax codes, and journal entry IDs are Xero-specific and non-portable. FlitStack exports a summary of Gensolve/Xero transaction totals (total invoiced, total paid, outstanding balance) per client as an ir.attachment on the res.partner record. For ongoing accounting continuity, you must choose one of two paths: (1) disconnect the Gensolve-Xero link, close the books in Xero up to the migration date, and rebuild invoicing workflows in Odoo Accounting going forward; or (2) use the Odoo Xero connector (available in Odoo Apps) to re-establish the link after go-live. Historical Xero data remains in Xero and is not migrated into Odoo.

Gensolve practitioner-to-Odoo-user resolution requires email matching before appointment migration

Gensolve stores practitioners as internal user accounts tied to appointment ownership and clinical note authorship. Odoo calendar.event requires a user_id (res.users) for the event owner. If a Gensolve practitioner's email does not match an existing Odoo res.users email, the appointment owner cannot resolve automatically. FlitStack generates a pre-migration owner-resolution report listing all Gensolve practitioner emails and their Odoo user match status. Unmatched practitioners must either be invited to Odoo as users before migration or their appointments are assigned to a fallback Odoo user with an annotation noting the original practitioner. This resolution step must complete before the calendar.event import runs, as Odoo does not allow updating user_id on completed events without write access.

Odoo import requires pre-creation of custom fields — data cannot land in non-existent fields

Gensolve custom fields on custom forms are created dynamically in Gensolve's Oracle schema and do not have a pre-announced schema that Odoo can discover. Before the migration import runs against Odoo, FlitStack must read the Gensolve export's field definitions, create each corresponding ir.model.fields record in Odoo Developer Mode, and verify that the field is correctly linked to the res.partner or product.product model. If a custom field is missed during the pre-creation step, the import will either skip the value silently (char/text fields) or throw a validation error (required or relational fields). We mitigate this by running a field-inventory pass on the Gensolve export before any import attempt, and by performing a dry-run import in an Odoo sandbox to catch missing field definitions before production data lands.