Migrate from Dental-Exec to Twenty CRM

Dental-Exec patients map directly to Twenty's People object. All contact fields (name, email, phone, address) are direct mappings. Dental-specific properties such as date of birth, medical history flags, and insurance references move as custom fields on the People record. Owner assignment resolves by email match against invited Twenty Workspace Members.

Dental-Exec appointment records (date, time, provider, treatment type, status) map to Twenty Tasks. The task is linked to the corresponding People record via personId. Appointment duration maps to task due-date and completion fields. Cancelled or no-show statuses map to custom task status values defined in Twenty's data model before import.

Dental-Exec treatment plans include procedure codes, tooth numbers, stages (proposed, in-progress, completed), and notes. A custom Treatment object is created in Twenty to hold these fields. The Treatment object is linked to the People record via a relation field. Procedure code values may require a value-mapping table if Twenty's select field options are pre-defined.

Dental-Exec insurance records (carrier name, policy number, group number, subscriber relationship, claim history) have no native equivalent in Twenty. A custom Insurance object is created with fields for carrier, policy number, group number, subscriber ID, and coverage type. It is linked to the People record via a relation field. Active versus inactive coverage status is mapped to a custom select field.

Dental-Exec tracks referring dentist or doctor names and referral source codes. In Twenty, this becomes a custom text or select field on the People object (e.g., Referral_Source__c). If the practice uses a defined list of referral sources, a select field with defined options is created before import to allow filtering in Twenty's views.

Dental-Exec staff and provider records map to Twenty Workspace Members. The import requires that all providers be invited to Twenty and accept their invitations before the migration runs, because task assignments (ownerId and assignee) use the Twenty Workspace Member ID. Staff without email addresses in Dental-Exec require a fallback email or manual assignment in Twenty after migration.

Dental-Exec clinic or practice records map to Twenty Companies. Practice name, address, phone, and specialty are direct field mappings. For multi-location practices, each location is a separate Company record, and the People records are linked to the appropriate location via the companyId relation.

Dental-Exec payment records (amount, date, method, associated treatment) are stored as a custom Payment object in Twenty, linked to the People record and optionally to the Treatment record. Payment method values (cash, card, insurance) are mapped to a custom select field. Outstanding balance is tracked as a custom currency field.

Dental-Exec recall intervals (e.g., '6-month cleaning due') map to Twenty Tasks with a future due date and a custom task type of 'Recall'. The task is linked to the People record. Recurrence information from Dental-Exec is noted as a text field on the task since Twenty's task model does not have native recurrence scheduling in all tiers.

Dental-Exec file attachments (PDF treatment plans, claim documents, imaging references) are migrated as Twenty Notes with a custom type field set to 'Attachment'. The original filename and a reference URL are stored in the Note body or a custom text field. Files exceeding Twenty's storage configuration are flagged before the full run so limits can be adjusted.

Any custom fields defined in Dental-Exec for tooth-chart data, claim status codes, NPI numbers, or HIPAA consent flags are created as custom fields in Twenty before import. These include select fields for procedure code categories, date fields for consent签署 dates, and checkbox fields for treatment plan milestones. All custom fields must be present in Twenty's data model before the CSV import runs, per Twenty's field-first import requirement.