Migrate from Dr.DENTES to Twenty CRM

Dr.DENTES Patient records map directly to Twenty People. Each patient becomes a People record with name, email, phone, address, and a link to the referring practice as a Company. Original patient create dates are preserved in a custom datetime field since Twenty's createdAt is set at import time.

When a Dr.DENTES patient record includes a guardian or emergency contact, that contact becomes a separate People record linked to the patient record via a custom relation field. Guardian relationships are not native to Twenty's schema and require a custom relation or linked Task note for retrieval.

Dr.DENTES practices or referring offices map to Twenty Companies. Company name, address, phone, and domain map directly to Twenty Company fields. If the source stores referring dentist NPI or specialty data, those migrate as custom fields on the Company record. Practice-level identifiers ensure downstream reporting can segment revenue by location or referral source.

Dr.DENTES appointment records (date, time, provider, procedure code, status) transform into Twenty Tasks linked to the Patient People record. Appointment type maps to Task title, scheduled date to due date, provider to assignee (resolved by email match against Twenty workspace members). Status is stored as a custom select field since Twenty Tasks do not have native appointment status workflows.

Dr.DENTES treatment plans — which include procedure codes, estimated costs, and completion status — map to Twenty Opportunities. Treatment plan total fee maps to Opportunity amount, planned start date to Expected Close Date, and procedure status to Opportunity stage (Proposal, Booked, Completed). Each treatment line item becomes a custom Notes attachment for reference.

Individual procedures within a Dr.DENTES treatment plan (e.g., D7140 extraction, D2750 crown) map to a custom Treatment Procedure object in Twenty. Each record links to the parent Opportunity and the Patient People record. Tooth number and surface data from Dr.DENTES is stored as custom text fields since Twenty has no native dental chart schema.

Dr.DENTES insurance claim records (claim ID, payer, submitted amount, status, payment received) migrate to a custom Insurance Claim object linked to the Patient People record. Claim status transitions (Submitted, Pending, Paid, Denied) map to a custom select field. Secondary claim linkage requires a custom relation field or Notes attachment since Twenty has no native claims object.

Dr.DENTES insurance payer records (insurance company name, address, payer ID) map to Twenty Companies with a custom payer_type select field set to 'Insurance Payer'. Linking insurance claims to payer companies enables reporting on revenue by insurance carrier across the patient population.

Dr.DENTES billing ledger entries — charges, payments, adjustments, and write-offs — migrate as records in a custom Billing Ledger object linked to the Patient People record. Each entry stores amount, type (charge, payment, adjustment), date, and payment method. Aging reports must be rebuilt as Twenty views with custom filters on ledger entry dates and types.

Dr.DENTES recall appointments (6-month hygiene recall, annual exam) migrate as Twenty Tasks with a custom recall_type select field. Due date is set to the recall target date, assignee to the primary provider. Recurrence must be rebuilt manually in Twenty's workflow builder since Twenty Tasks do not have native recurrence rules.

Dr.DENTES clinical notes and clinical attachments migrate as Twenty Notes linked to the Patient People record. Rich-text formatting in notes is preserved. If Dr.DENTES supports file attachments, those are downloaded and re-uploaded to Twenty Files linked to the Note or People record.

Dr.DENTES provider and staff user records resolve by email match against Twenty workspace members. Users without a matching email are flagged before migration — the practice must invite them to Twenty first or assign their records to a fallback owner. Provider specialties and NPI numbers migrate as custom fields on the workspace member profile.

Dr.DENTES custom intake forms, health history questionnaires, or satisfaction surveys migrate as custom objects in Twenty. Each response becomes a record linked to the Patient People record. Survey question fields become custom fields on the object — field types are mapped from the source (text, date, select, multi-select) to the closest Twenty field type equivalent.

Dr.DENTES supply or inventory tracking (if exported) maps to a custom Supply Item object in Twenty. Fields include item name, SKU, quantity on hand, reorder level, and supplier Company link. This object is optional and only included if the practice uses Dr.DENTES for supply management and wants to track those records post-migration.