Migrate from Dent-O-Soft to Twenty CRM

Patient records map to Twenty's People object. Name, email, phone, address, and date of birth migrate directly. Insurance carrier is stored as a link to a Company record (created or matched first). Original patient ID is preserved in Source_System_ID__c custom field for traceability and delta-run deduplication.

Dental insurance carriers are organizations, not people, so they migrate to Twenty's Companies object. Carrier name becomes the Company name; address and phone map directly. A custom field (Carrier_Type__c) is set to 'Insurance Carrier' to distinguish from practice or lab Company records.

Treatment plans migrate to Twenty Opportunities with planned treatment amount mapped to Amount, plan status mapped to Opportunity stage via value mapping (Proposed → 'Initial Exam', Approved → 'Treatment Plan', Completed → 'Closed Won'), and provider as the Opportunity owner resolved by email match to Twenty workspace members.

Individual procedures attached to a treatment plan split into two paths: procedure fee and tooth code are custom fields on the parent Opportunity (linked by opportunityId); procedure history (dates, surfaces, materials) migrates as a custom Procedure custom object linked to the People record. Tooth number and surface use custom fields; ADA procedure codes require value mapping against Twenty custom select options.

Appointments map to Twenty Tasks. Appointment date and time become Task dueDate and startTime; provider becomes the Task assignee matched by email to Twenty workspace members; appointment type is stored in a custom Task_Type__c field; notes and clinical instructions become the Task body or an attached Note.

Clinical notes, progress notes, and periodontal chart entries migrate to Twenty Notes attached to the relevant People record. The note subject is set from the note type or date; the body contains the full clinical text. Per-tooth charting data is stored as a custom Note or custom object depending on structure complexity.

Twenty has no native insurance claim object. We create a custom InsuranceClaim object with fields for claim number, carrier (lookup to Company), patient (lookup to People), service date, billed amount, paid amount, adjustment, adjustment reason, and claim status. Claim status uses a custom select with values matching the source (Pending, Submitted, Paid, Denied, Appeal).

Lab work orders migrate to a custom LabPrescription object with lab name (lookup to Company), prescription date, due date, status, tooth number, shade, material, design instructions, and patient link. Lab vendor records are created as Companies with type 'Dental Lab' before prescriptions are imported.

Dent-O-Soft recall intervals (6-month cleaning, annual exam) become Tasks with a due date calculated from the last appointment date plus the recall interval. A custom field Recall_Type__c stores the recall category (prophy, perio maintenance, exam). The Task is linked to the People record and assigned to the practice's default owner.

Referring dentists and specialists split based on Dent-O-Soft type: if stored as an organization, they become Companies with type 'Referral Source'; if as an individual, they become People records linked to a referring Company. A custom field Referral_Source__c marks the relationship.

Treatment consent forms, insurance cards, and clinical documents migrate as Twenty Notes attached to the relevant People record. For image files, we note the file type and size; images are re-uploaded to Twenty's file storage and linked. File size limits per Twenty storage configuration apply.

Patient payment history and ledger entries migrate to a custom Payment object linked to People and Opportunity. Fields include payment date, amount, payment method, applied-to procedure, and balance. Payment totals are not automatically rolled up — a custom rollup field or report is built post-migration.