Migrate from Dentrix to Twenty CRM

Dentrix Patient record maps directly to Twenty People. The patient name, date of birth, contact information, address, and medical alerts translate as direct fields or custom fields on the People object. Medical alerts (allergies, conditions) require a custom Alert__c multi-select field in Twenty since the platform has no native clinical-alert mechanism.

Referring dentists, oral surgeons, and specialist offices stored as referring providers in Dentrix map to Twenty Company records. Company name, practice name, address, phone, and NPI number transfer as standard Company fields. Referring provider type (oral surgeon, endodontist, etc.) maps as a custom Type__c pick-list on the Company object.

Insurance carriers from Dentrix (Delta Dental, Cigna Dental, MetLife, etc.) merge into a separate Company record type in Twenty, distinguished from referring providers via a custom Company_Type__c field set to 'Insurance Carrier'. This allows linking patients to their insurance plan Company record while keeping the insurer separate from referral sources.

Dentrix appointments map to Twenty Tasks linked to the People record. Each appointment task captures the appointment date, provider assigned, procedure codes performed, and status (completed, no-show, cancelled). Recurring recall appointments become recurring Tasks in Twenty — the platform supports due date-based recurring tasks on the Task object.

Open treatment plans in Dentrix map to Twenty Opportunities representing the remaining treatment value. The Opportunity Stage maps to treatment plan status (Proposed, Scheduled, In Progress, Completed, Cancelled). Treatment plan procedure codes and estimated fees transfer as line items using Twenty's Opportunity model or as custom fields if the practice uses a simplified single-value approach.

Dentrix clinical progress notes attach to the Patient record and map to Twenty Notes linked to the People record. We preserve the original note date, provider author, and full note body. Clinical notes use Twenty's rich-text Note capability, but per Twenty's documentation, Notes are free-form and not searchable via the standard filter — they appear in the record timeline.

Patient-specific insurance details (carrier, group number, subscriber ID, eligibility dates, coordination of benefits) require custom fields on the People object: Insurance_Carrier__c (lookup to Company), Group_Number__c, Subscriber_ID__c, Eligibility_Start__c, Eligibility_End__c, and Subscriber_Relationship__c. These fields must be created in Twenty Settings → Data Model before the People import runs.

Dentrix billing ledger entries (charges, payments, adjustments, insurance payments, write-offs) do not map to any standard Twenty object. We create a custom Ledger_Entry__c object with fields for Entry_Date__c, Type__c (charge/payment/adjustment/writeoff), Amount__c, Description__c, Provider__c (relation to Company), and Patient__c (relation to People). Each entry links to the People record. This requires Twenty Organization-tier or a self-hosted instance to create multiple custom objects.

CDT (Current Dental Terminology) procedure codes performed at each appointment do not have a native equivalent in Twenty. We map them as a custom Procedure_Code__c text field on the Task object, storing the CDT code (e.g., D0120, D2750) and description. Practices using procedure codes for production tracking may prefer a separate Procedure__c custom object linked to Task for more granular reporting.

Dentrix documents attached to patient charts (consent forms, insurance cards, referral letters in PDF/Word format) export from Dentrix and re-upload to Twenty as native file attachments on the People record. We download the files from Dentrix's document management path and attach them to the corresponding People record during migration. PDF and image files re-host directly; Word documents may require format conversion.

Dentrix provider and staff accounts (dentists, hygienists, office managers, billing staff) resolve against Twenty WorkspaceMembers by email match. If a provider email exists in Dentrix and a matching email invite is sent to Twenty before migration, records assign to the correct owner. Unmatched providers flag as 'Unassigned Provider' and must be resolved post-migration.

Dentrix imaging files (bitewing X-rays, panoramic radiographs, intraoral photos, CBCT scans in proprietary or DICOM format) have no migration path to Twenty CRM. The imaging viewer in Twenty is not designed for clinical radiology. We export a manifest of imaging file names and dates linked to the patient People record, but the actual image files must remain in Dentrix or be exported separately to a dedicated dental imaging PACS system.