Migrate from tab32 to monday CRM

tab32 patient records map to monday CRM contacts. Patient first name, last name, email, phone, address, and date of birth map to standard monday CRM contact fields. Multiple phone numbers (home, cell, work) use monday CRM's additional-phone custom columns. The mapping also includes patient gender and preferred contact method, stored as optional custom fields on the Contact record.

tab32 providers (dentists, hygienists, specialists) map to monday CRM contacts with a Provider_Role__c custom column identifying their role. monday CRM has no native practitioner object, so the Contact Person type is the closest structural equivalent and supports the same field set as patient contacts.

tab32 practice or location records map to monday CRM company records. Practice name, address, phone, and NPI number map to standard monday CRM company fields. For multi-location DSOs, each location becomes a separate Company record linked to patient contacts via monday CRM's Contact-Company relationship.

tab32 appointments map to monday CRM deals representing each visit. Appointment date maps to CloseDate, status to deal Stage, and provider assignment to a custom Deal_Provider__c column. Practices using monday's board structure may prefer appointments as sub-items under the patient Contact for tighter patient-level grouping.

tab32 treatments (procedure code, tooth number, surface, fee, clinical notes) merge into a monday CRM deal representing the patient visit. CDT code maps to a custom CDT_Code__c column; tooth number and surface map to separate custom columns; clinical notes map to a long-text Deal_Clinical_Notes__c column. ADA procedure descriptions are stored as a text column for staff reference.

tab32 insurance records (carrier name, policy number, group number, subscriber relationship, covered procedures, coverage percentages) map to custom columns on the patient Contact record in monday CRM: Insurance_Carrier__c, Policy_Number__c, Group_Number__c, Subscriber_Relation__c, and Coverage_Pct__c. Claim status is tracked via a custom Insurance_Claim_Status__c column.

tab32 tooth chart and periodontal chart data (surface-level charting, pocket depths, mobility, recession) have no native monday CRM equivalent. We serialize this clinical data as a JSON-formatted string or plain-text block in a Contact_Tooth_Chart__c long-text column. Staff interpret the data manually; a separate board tracks perio recall schedules as dated deals.

tab32 imaging files (X-rays, intraoral photos, panoramic images) attach to patient records. monday CRM stores files on the board level. We re-upload images as monday CRM file attachments and store the original tab32 image reference URL in a Contact_Imaging_URL__c column for traceability. Inline images in clinical notes are downloaded and rehosted.

tab32 recall records (6-month cleaning, annual exam, perio maintenance) map to monday CRM deals with a custom Recall_Type__c column and a Next_Recall_Date__c custom date column. Automated monday CRM automations then trigger reminders based on this date column post-migration. The recall interval stored in tab32 maps to a numeric Interval_Days__c column, enabling monday CRM automations to calculate next due dates dynamically and flag overdue recare.

tab32 claims ledger, adjustments, write-offs, and payment history map to monday CRM as a combination of custom columns and deal line items. monday CRM has no native revenue-cycle management module; claims status, adjustment reasons, and payment reference numbers require a custom column set. FlitStack flags this as a rebuild area for your monday setup.

tab32 user accounts and owner assignments on records resolve to monday CRM users by email match. Unmatched owners are flagged before migration. monday CRM's user model is simpler than tab32's multi-location permission sets — permission levels, office access restrictions, and role-based access must be reconfigured in monday CRM settings post-migration.

tab32 custom properties on any object (extended patient fields, referral source tracking, clinical flags) map to monday CRM custom columns of the matching type (text, number, date, multi-select). monday CRM's column type must be selected at creation — incorrect type choices require column recreation and data reimport.