Migrate from My Dental Clinic to Odoo CRM

My Dental Clinic patient records map directly to Odoo res.partner records. The patient's full name splits into firstname and lastname fields in Odoo. Email, phone, and address fields migrate directly. The original patient create date preserves as a custom datetime field since Odoo's create_date reflects the migration timestamp.

Insurance carrier name, policy number, group number, and subscriber relationship migrate as custom Char and Selection fields on res.partner. Odoo Studio creates these fields before migration runs. Claim filing status and insurance notes map to a custom Text field for reference.

Treatment plan procedure codes and descriptions migrate as custom Selection fields listing ADA codes plus a long-text field for provider notes. Historical treatment notes also become Odoo internal notes (mail.message with note subtype) attached to the contact record for provider reference.

My Dental Clinic appointment records with date, time, provider, and visit type map to Odoo calendar.event records. The original appointment start datetime and duration preserve. Provider maps to Odoo user_id by email match. Visit notes migrate as event description fields.

Patient billing history—charges, payments, adjustments—migrates as a custom JSON field on res.partner holding the ledger array. For practices requiring full accounting continuity, FlitStack creates corresponding Odoo account.move records with manual entry flag since dental billing codes require ADA-to-product mapping first.

My Dental Clinic provider records map to Odoo res.users by email address match. Providers without Odoo user accounts become inactive user records with a custom staff_type field, ensuring provider names appear in appointment history without granting system access. Inactive provider records retain the provider's name and contact information, allowing historical appointments to display correctly while preventing login. The staff_type field can be set to 'provider' for reporting and filtering purposes.

Patient documents—consent forms, treatment images, insurance cards—migrate as Odoo ir.attachment records linked to the corresponding res.partner. Files re-upload to Odoo's filestore. Inline images in notes download and rehost as attachments. The original filename and upload timestamp are preserved as custom fields (x_original_filename, x_original_upload_date). Large files are chunked during upload to avoid timeout. Access rights on attachments inherit from the contact record, ensuring only authorized staff can view sensitive documents.

Referral source tracking in My Dental Clinic (e.g., insurance network, colleague referral, marketing campaign) migrates as a custom Selection field on res.partner. Odoo's crm.lead module handles opportunity tracking separately if the practice uses Odoo CRM for case referrals. Selection options match My Dental Clinic source categories; admin can add new values via Odoo Studio. The referral can link to a crm.lead for follow‑up activities and conversion tracking.

Any custom fields unique to the My Dental Clinic setup—tooth charts, specific procedure codes, clinical flags—migrate as Odoo custom fields via ir.model.fields. Field type mapping applies: numeric dental measurements map to Float fields, yes/no clinical flags map to Boolean fields, and text observations map to Text fields.

If My Dental Clinic manages multiple clinic locations, each location becomes a separate res.company in Odoo, with patient records tagged by company_id foreign key. Multi-company setup requires Odoo Custom Plan and pre-migration configuration by the Odoo admin. After migration, company's users are linked to their res.company, enabling per‑company reporting and access control. Security rules restrict patient visibility to the owning company, and the admin can configure inter‑company sharing if needed.