Migrate from Denticon to Odoo CRM

Denticon patient records map 1:1 to Odoo res.partner contacts. Name, email, phone, address, and date of birth transfer directly. Partner type (patient vs. company) is set via res.partner.customer_rank. Dentists and referring providers also land as res.partner but are flagged separately.

Dental-specific patient data — insurance carrier, policy number, group number, subscriber ID, treatment plan codes — has no Odoo CRM equivalent. These transfer to custom Char/Selection fields on res.partner (Insurance_Carrier__c, Policy_Number__c) for reference and must be validated against Odoo's Contacts Insurance module if used.

Denticon appointment records do not map to a native Odoo CRM object. We translate each appointment into a crm.lead activity log entry (mail.message with date, provider, production type) and attach it to the corresponding res.partner lead. Appointment status (scheduled, completed, cancelled) maps to Odoo's activity state.

Denticon provider records (dentists, hygienists, office staff) resolve by email match to Odoo res.users accounts. Providers without email addresses are flagged for Odoo user account creation before migration. Odoo hr.employee records are also created for provider records that lack user access.

Denticon provider contact details (name, email, phone, specialty) also land in res.partner as type='contact' records. The provider_id reference on patient records maps to the corresponding res.partner.id in Odoo, maintaining the relationship between patients and their care providers.

Each Denticon office (OID) within a PGID maps to a separate res.company in Odoo. This requires multi-company configuration in Odoo settings. Companies are created first so res.partner and crm.lead records can reference the correct company_id foreign key during import.

Denticon referral sources (external incoming referrals with cost data) map to Odoo utm.source records. The referral cost field transfers to a custom Decimal field on crm.lead (Referral_Cost__c). Referring provider names link to the corresponding res.partner record if one exists.

Denticon accounts receivable, billing records, and payment history are accounting data outside Odoo CRM's scope. These migrate to Odoo Accounting (account.move) only if the Odoo Accounting module is active. FlitStack flags this as a separate migration scope requiring Odoo Finance configuration.

Denticon external referral form data and attachments map to crm.lead notes and ir.attachment records. The referral form URL and form-submission metadata transfer as custom fields on the lead. Any attachments included in the referral are downloaded and re-uploaded to Odoo's ir_attachment table.

Denticon's two alphanumeric custom fields on User Setup screens (Setup → Office, Provider, Referral, Account) migrate as custom Char fields on the corresponding Odoo models. These require Odoo Studio (Enterprise) or direct model XML modification (Community) to create before data import.

The Denticon PGID organization name maps to a top-level res.company in Odoo. If the Denticon setup uses the PGID Split feature to separate offices, each split office becomes a child res.company via parent_id. The top-level company holds global settings; child companies hold location-specific configurations.