Migrate from Denticon to Twenty CRM

Denticon patient records map directly to Twenty People records. The patient's full name, email address, phone number, and postal address transfer as standard Twenty People fields. A custom field (Patient_ID__c) stores the original Denticon patient ID for traceability and delta-run de-duplication.

Denticon patients may have a guarantor who is a separate person (parent, spouse, or third-party) responsible for billing. FlitStack AI creates the primary patient as a Twenty People record and stores the guarantor's name and relationship as a custom text field (Guarantor_Name__c) on that record. If the guarantor is also a tracked contact, they receive a separate People record linked via a relation field.

Each Denticon Office ID (OID) — representing a physical practice location — maps to a Twenty Company record. The office name, address, and phone become Company fields. For multi-location DSOs, all OIDs are exported separately and loaded as individual Company records, with a custom pick-list field (Location_Type__c) set to 'Dental Practice' to distinguish them from referring provider offices.

Denticon's incoming and outgoing referral sources (external dental offices, specialists) are represented as Company records in Twenty. A custom pick-list field (Referral_Source_Type__c) is created to distinguish referring providers from internal practice locations, preserving the referral relationship without requiring a separate junction object.

Denticon providers (dentists, hygienists, specialists) are mapped to Twenty Workspace Members. A People record is created for each provider with a custom pick-list field (Provider_Role__c) storing their Denticon provider type. Their email address is used to match against invited Twenty workspace members; unmatched providers are flagged before migration for the team to invite first, per Twenty's warning that user references must exist before import.

Each completed or open dental appointment is treated as a line-item in a Twenty Opportunity representing that patient visit or treatment series. The Opportunity Name is constructed from the patient name and appointment date (e.g., 'Smith J - New Patient Exam 2025-03-15'). Custom fields capture the treatment type (Cleaning, Restorative, Surgical, etc.), provider assigned, and appointment status. Open vs. completed status maps to Opportunity Stage values created during Twenty setup.

Denticon treatment plans and individual procedure codes (ADA codes) have no direct equivalent in Twenty's standard schema. FlitStack AI exports each treatment plan as a Twenty Note attached to the patient People record, with a structured text format listing procedure codes, tooth numbers, surfaces, and fees. For practices that need searchable procedure data, custom fields (Last_Treatment_Code__c, Last_Treatment_Date__c) are created on the People object.

Denticon's RCM (Revenue Cycle Management) module — including insurance claims, claim status, adjustments, and payments — has no CRM equivalent in Twenty. FlitStack AI exports claim summaries as Notes on the patient record. For practices with complex billing histories, a custom object (Insurance_Claim__c) is created with fields for claim number, carrier, status, amount billed, and amount paid — this requires the team to configure the object in Settings → Data Model before migration runs.

Denticon's 2-way texting log and automated campaign delivery records map to Twenty Tasks. Each outbound or inbound patient message is created as a Task with Type='Message', linked to the patient People record. Original timestamps, message content, and delivery status are preserved in the Task description field.

Denticon allows two alphanumeric custom fields per patient record (each up to 25 characters) accessible in Office Setup screens. FlitStack AI creates matching custom fields on the Twenty People object (up to 2 custom fields per migration scope) and populates them from the Denticon export. Practices using the API-based custom field extension pattern store values in custom text fields named to match their Denticon field labels.

Denticon recall appointments (hygiene re-care, annual exam reminders) map to Twenty Tasks with a due date set to the recall date. A custom datetime field (Next_Recall_Date__c) is added to the People record so the recall window is visible directly on the contact without opening the task. Completed recalls are linked to the patient as a closed Task.

Denticon file attachments (treatment plan PDFs, insurance cards, signed consent forms) cannot be re-hosted inside Twenty's standard attachment model. FlitStack AI downloads all attachments, stores them in the customer's designated cloud storage, and creates a Note on the patient record with a link to the file. The customer configures their own storage bucket; FlitStack does not host files long-term.