Migrate from Dent-O-Soft to Odoo CRM

Dent-O-Soft patient records map directly to Odoo res.partner contacts. The patient's full name splits into firstname and lastname on res.partner. Email, phone, and address fields map 1:1 to their Odoo counterparts. Dent-O-Soft's patient_id becomes x_source_patient_id custom field for traceability and delta-run de-duplication, ensuring that repeated migration runs do not create duplicate contacts in Odoo.

Insurance provider name, policy number, and group number from Dent-O-Soft patient records migrate to custom fields x_primary_insurance_provider and x_insurance_policy_number on res.partner. Secondary insurance maps to x_secondary_insurance_provider as additional text fields. All insurance fields preserve the original Dent-O-Soft values exactly as entered, including any formatting or special characters present in the source data.

Dent-O-Soft stores procedure codes, dates, and notes in a treatment history table with multiple rows per patient. FlitStack concatenates this into a structured text block stored in x_treatment_history__c in Enterprise or x_treatment_history on Community, preserving the date, procedure code, and dentist name for each entry. Entries are separated by newlines for readability and searchability within the Odoo interface.

Dent-O-Soft appointment records containing date, time, practitioner, procedure_type, and status map to Odoo mail.activity entries linked to the patient res.partner. Activity type defaults to 'appointment' using mail.activity.type configuration, with the original appointment datetime stored in activity_date_deadline and appointment notes preserved in the activity note field including any HTML formatting that exists in the source records.

Dentists and hygienists in Dent-O-Soft migrate as separate res.partner records tagged with contact_type = 'practitioner' using a custom x_contact_category field. Their professional credentials store in x_credential, license numbers in x_license_number, and specialty designations in x_specialty custom fields on the partner record for complete practitioner profiles in Odoo.

Dental labs and material suppliers from Dent-O-Soft map to res.partner with supplier = True flag set on the partner record. Contact type set to 'supplier' in the x_contact_category custom field. Primary contact person name, email, and phone map directly to the corresponding res.partner fields, while lab-specific flags like is_lab store in x_is_dental_lab custom field.

Dent-O-Soft patients can have multiple emergency contacts stored as separate related table rows. Each emergency contact row becomes its own res.partner record with contact_type = 'emergency' in the x_contact_category field and a parent_id link back to the patient partner record using Odoo's child contact relationship. The relationship type between patient and emergency contact stores in x_emergency_relationship custom field.

Dent-O-Soft billing transactions including charges, payments, and adjustments have no direct Odoo CRM equivalent in the base CRM app. The migration preserves x_last_billing_date and x_outstanding_balance as custom Char fields on res.partner for reference. Full billing history export provided as CSV for Odoo Accounting module import, including invoice numbers, dates, amounts, and payment status for each transaction.

Treatment notes and clinical observations stored in Dent-O-Soft map to Odoo mail.message records attached to the patient res.partner. Author resolved by practitioner email match against Odoo system users. The body field preserves original note text exactly as entered, including any clinical terminology or formatting, with the creation datetime matching the original Dent-O-Soft timestamp to maintain clinical record chronology.

Automated reminder rules configured in Dent-O-Soft have no Odoo equivalent that migrates automatically between the two platforms. FlitStack exports reminder configuration as a structured JSON document that Odoo administrators use to rebuild automation rules in Odoo's base.automation or mail.activity.plan framework. The export includes trigger conditions, timing offsets, notification channels, and recipient filters from the source system.

Multi-location dental practices using Dent-O-Soft's practice identifier system map to separate res.company records in Odoo for each physical location. Each company's name, address, and NPI or tax ID stored in standard Odoo company fields including street, city, state_id, zip, and country_id. The practice name from Dent-O-Soft maps to the res.company name field, and location-specific contact information preserves for each branch.

Dent-O-Soft tracks referral source for new patients as a field on the patient record. This data transforms into crm.lead.source values on the original patient-contact record in Odoo, allowing practices to maintain referral tracking visibility within the CRM. FlitStack creates source tags in Odoo's crm.lead.source model matching the Dent-O-Soft referral source values, enabling reporting on referral trends by source.