Migrate from The Dental System to Odoo CRM

Odoo has no native dental data model — custom fields and module planning are required before data lands

Odoo CRM ships with a generalized res.partner and crm.lead schema. The Dental System's clinical fields (allergy flags, blood type, insurance metadata, ADA procedure codes, tooth-number references) have no native Odoo equivalent. We create custom fields on the res.partner record for patient-level clinical data and a custom treatment record model for procedure-level data. If your team uses an OCA dental module or a custom-built dental add-on in Odoo, those models must be installed and active before migration data is written — otherwise the custom field names will not resolve. We deliver a custom-field and module checklist as part of the pre-migration plan so the Odoo side is schema-ready before any data is extracted from The Dental System.

ADA/CPT procedure codes and diagnostic codes require custom field mapping and manual verification

The Dental System stores procedure codes and diagnostic codes (ICD-10) natively as structured fields. Odoo CRM has no built-in clinical coding model — these codes must migrate as custom Char fields on the treatment record. ADA codes especially can be alphanumeric (D0120, D2740) and may not survive a simple text import if source formatting is inconsistent. We flag malformed or missing codes in the pre-migration validation report and map every code we can resolve automatically. Codes that fail validation are preserved in a raw_custom_codes__c fallback field for manual review in Odoo after migration — no code is silently dropped.

Odoo API rate limits on external API connections extend the migration window for large attachment batches

Odoo's external XML-RPC API enforces a rate limit of approximately 1 request per second for some Odoo plans, and the batch import API has specific throttling behavior depending on your Odoo edition and hosting (Odoo Online, Odoo.sh, or self-hosted). The Dental System attachment data — patient forms, insurance card images, consent documents — often totals hundreds of megabytes. At 1 request per second for file creation and attachment linking, a 500-attachment batch alone can consume the better part of 10 minutes. We use Odoo's native bulk create via ORM where possible and throttle API calls to respect the rate limit, extending the cutover window accordingly. Self-hosted Odoo deployments can raise the limit via PostgreSQL configuration adjustments.

Multi-location dental groups must configure Odoo's multi-company setup before user assignments and data routing

If The Dental System manages multiple practice locations and you intend to run those as separate Odoo company records (for reporting segregation and accounting multi-company configuration), the company setup must precede the migration. Odoo requires each company to have its own data sequences, fiscal years, and chart of accounts if the Accounting module is active. We deliver a multi-company routing plan before migration: which practices map to which Odoo company records, how patient records are distributed across companies, and how staff users are assigned to the correct Odoo company and security groups. Running the migration without this plan can result in patient records landing in the wrong company partition.

The Dental System recall and patient-reminder workflows do not migrate — Odoo automation rules must be rebuilt

Recall intervals (6-month cleaning reminders, annual exam alerts) and patient-reminder workflows in The Dental System are automation constructs with no equivalent in Odoo's base CRM module. These rules are not data records — they are system-level automation logic that does not export. We provide a structured export of your active recall rules from The Dental System: trigger conditions, interval logic, and notification content. Your Odoo administrator uses this export as a rebuild reference when configuring Odoo CRM automation rules (IrCron triggers, activity templates, and mail templates). For practices with complex recall logic (conditional intervals based on treatment history), custom Odoo automation scripting or a Python module may be required.