Migrate from DentAdmin to Twenty CRM

DentAdmin patients map directly to Twenty People records. All contact fields (name, phone, email, address) migrate as standard Twenty fields. Belgian healthcare identifiers (RIZIV professional codes, Mutuality numbers) are stored as custom text fields on the People record since Twenty has no native Belgian healthcare field. The original DentAdmin patient ID is preserved as Source_System_ID__c for delta-run de-duplication.

Referring dentists and specialist providers from DentAdmin map to Twenty Companies with a custom 'ProviderType' field set to 'Referral' or 'Specialist'. The company's name, address, and phone migrate as standard Company fields. If DentAdmin stores multiple provider addresses per dentist, the primary address becomes the Company record and additional addresses are preserved as custom fields or notes.

Mutuality and insurance company records from DentAdmin map to Twenty Companies with a custom 'CompanyType' field set to 'Insurance'. The company's name and registration number migrate as standard fields. Insurance policy numbers and coverage tiers attached to patients migrate as custom fields on the People record rather than on the Company record.

DentAdmin appointments become Twenty Tasks linked to the Patient (People record) via the Task's ' Person' relation and to the treating provider via the 'Assignee' field mapped to a Twenty Workspace Member. Appointment type (check-up, treatment, consultation) maps to a custom 'AppointmentType' select field. Date and duration migrate as Task due date and a custom duration field. Room and chair assignments from DentAdmin are stored as custom text fields.

DentAdmin treatment records have no direct Twenty CRM equivalent — Twenty has no native dental-procedure object. We create a custom 'Treatment' object in Twenty with fields for procedure code (mapped from DentAdmin's RIZIV procedure list), tooth number or quadrant, date performed, treating provider, associated Patient (People relation), and treatment cost. Tooth-number notation (FDI, Universal) is preserved as a text field to avoid data loss on format interpretation.

DentAdmin's invoicing module does not map to any Twenty CRM standard object — Twenty has no native invoicing. Invoice records migrate as a custom 'Invoice' object with fields for invoice number, date, amount, patient (People relation), treatment reference (Treatment custom object relation), and payment status. Original invoice PDFs are exported from DentAdmin and re-uploaded as file attachments to the Invoice record in Twenty.

DentAdmin document attachments (treatment plans, lab prescriptions, clinical images) associated with a patient become Twenty Notes linked to the People record. If DentAdmin exports attachments as files rather than inline content, the file is downloaded to local storage and re-uploaded to Twenty's file storage, with the file URL embedded in the Note body. Large archives (panoramic X-rays, intraoral scans) may exceed Twenty's default file size limits and are flagged for manual handling.

DentAdmin's RIZIV billing engine and accounting module are healthcare-financial constructs with no CRM equivalent. RIZIV procedure codes and Mutuality billing logic do not migrate — those records become reference data on the Treatment custom object, and the billing workflow needs to be rebuilt in Twenty or handled in a separate accounting tool. We preserve all financial transaction records as a custom 'BillingTransaction' object for historical reference.

Appointment reminder sequences, recall workflows, and treatment-plan follow-up sequences in DentAdmin have no direct equivalent in Twenty CRM. They must be rebuilt in Twenty's workflow builder or as an external automation layer. We export DentAdmin workflow definitions as a structured reference document so your Twenty admin can rebuild them in the correct order.

DentAdmin's built-in clinical and financial reports (RZIV-code utilization, patient retention, treatment revenue by provider) do not migrate. The underlying data — appointments, treatments, invoices — is fully migrated, and the Twenty dashboard builder can reconstruct those reports from the migrated records. We provide a report-mapping worksheet listing each DentAdmin report and its Twenty equivalent using the migrated data.