Migrate from tab32 to Twenty CRM

tab32 Patient records map directly to Twenty CRM People. Patient first name, last name, date of birth, phone, email, address, and emergency contact fields translate to the corresponding Twenty People fields. Original patient ID stored as a custom field (tab32_Patient_ID__c) for traceability and delta-run de-duplication.

tab32's practice or office location records map to Twenty CRM Companies. Practice name becomes Company name, address maps to the Company address fields, phone maps to the main phone field. Each DSO location becomes a distinct Company record so pipeline reporting can aggregate across locations.

tab32 Provider records (dentists, hygienists, specialists) map to Twenty CRM Workspace Members. Provider specialty (GP vs. specialist) and license number map to custom text fields on the member profile since Twenty does not have a native specialty field. Providers who are also sales contacts map as both People and Workspace Members.

tab32 appointment records (date, time, provider, operatory, procedure) map to Twenty CRM Tasks linked to the People (patient) record. The appointment status (confirmed, completed, no-show) maps to Task status. Custom fields capture the CDT procedure code, operatory, and provider assignment since Twenty Tasks lack native scheduling fields.

tab32 treatment plans list procedures with CDT codes, tooth numbers, fees, and clinical notes. These require a custom Treatment Plan object in Twenty CRM with a relation to the People record. Each plan line item becomes a child record or a multi-select field on the treatment plan, depending on the volume of line items per patient.

tab32 perio pocket depth records (six sites per tooth, BOP, furcation, mobility) have no Twenty CRM equivalent. We create a custom Perio Exam object linked to the People record, with numeric fields for each tooth site and a date field for the exam date. Historical perio exams are preserved as separate records ordered by exam date.

tab32 insurance claim records (claim ID, status, submitted amount, paid amount, payer, CDT codes, adjustment reasons) map to a custom Insurance Claim object linked to the People record. Claim status values (submitted, pending, paid, denied) map via value mapping to the custom pick-list in Twenty.

tab32 tooth chart records (surface conditions per tooth using the Universal Numbering System) require a custom Tooth Condition object linked to People. Each tooth number (1–32) plus surfaces (M, O, D, B, F, L) map to a custom pick-list field. Surface condition values (amalgam, composite, missing, implant, crown) also map as pick-list values.

tab32 patient payment records (payment date, amount, method, provider adjustment, write-off) map to a custom Payment Record object linked to the People record. Payment method (credit card, check, insurance payment, plan) maps as a custom pick-list. Provider adjustments and write-offs stored as separate numeric fields.

tab32 fee schedules define procedure fees per provider or location. These map to a custom Fee Schedule object with a relation to the Company (practice location) and a text field for CDT code + fee amount pairs. For DSOs with location-specific fees, multiple Fee Schedule records are created per Company.

tab32 file attachments (consent forms, insurance cards, treatment plan PDFs) re-upload as Twenty CRM Notes attached to the corresponding People record. File size limits from Twenty's storage configuration apply. Inline clinical images downloaded from tab32 and re-hosted or attached as Note records.