Migrate from tab32 to Salesforce Sales Cloud

tab32 patient demographics (name, DOB, address, phone, email) map directly to Salesforce Contact. The patient's primary provider assignment resolves to Contact.OwnerId by provider email match. Multi-location patients use Account Contact Relationships when the patient has records at more than one practice.

tab32 patients marked as lead-source prospects who have not yet had an appointment route to Salesforce Lead with LeadSource populated from tab32's referral source field. Active patients with treatment history route to Contact; inactive leads with no treatment stay in Lead.

tab32 providers with active user logins map to Salesforce User records, preserving NPI, DEA number, specialty, and credential fields as custom fields. Providers who are also referring doctors map additionally as Contact records with a Provider_Type__c custom pick-list. These custom fields include License_Number__c, Specialty__c, and Credential_Expiry__c to capture complete professional history within Salesforce.

Each tab32 practice location becomes a Salesforce Account record with Type='Practice Location'. Billing address, phone, and taxonomy code map to Account fields. Multi-location DSO parent company becomes the Salesforce Account hierarchy root using ParentId. If the DSO uses Salesforce Territories, each location can also be assigned a Territory__c field to streamline reporting and quota allocation.

tab32 appointments with a start time and duration map to Salesforce Event with Subject, StartDateTime, EndDateTime, and WhoId (patient Contact). No-duration tasks (recalls, follow-ups) map to Salesforce Task. Provider assignment becomes Event.OwnerId resolved by provider email. When a provider does not have a Salesforce User, the appointment defaults to a DSO admin User and is flagged for later ownership correction.

tab32 treatment plans with procedure codes (CDT codes), tooth numbers, surfaces, fees, and provider notes migrate to a custom Treatment_Plan__c object with a lookup to the patient Contact and a related list on the Account. Procedure codes stored as Treatment_Code__c (text) with Description__c for the human-readable label.

tab32 insurance claims map to Salesforce Opportunity (for the billed amount) with Claim_Status__c, Payer_Account__c (lookup to insurance carrier Account), Subscriber_ID__c, and Group_Number__c as custom fields. Claim workflow stages (submitted, pending, paid, denied) map to Opportunity Stage values via value mapping.

tab32 insurance carriers and employer benefit plans become Salesforce Account records with Type='Insurance Carrier'. Carrier address, payer ID, and electronic submission settings map to custom fields. Patient coverage details (subscriber ID, group number, effective dates) live in a custom Dental_Coverage__c junction object between Contact and the carrier Account.

tab32 patient payments map to Salesforce Task with Type='Payment' recording amount, payment date, and payment method. Outstanding balances with a defined collection path become Opportunities with Stage reflecting collection status. Full payments close the related treatment plan Opportunity. For practices using Salesforce Payments, each settled transaction can also generate a corresponding Payment record linked to the Opportunity.

tab32 tooth chart and perio chart data migrate to a custom Dental_Chart__c object linked to the patient Contact. Tooth number, surface condition (MO, DO, MOD), perio probing depths, and mobility grades map to custom fields. Chart type (initial, recall, perio maintenance) stored as Chart_Type__c pick-list.

tab32 recall intervals (6-month, annual, perio) merge into Salesforce Tasks with reminder dates. Bulk recall campaigns (e.g., all patients due for hygiene in Q1) map to Salesforce Campaigns with Campaign Member status reflecting recall completion. We also preserve any validation rules defined on these fields in the mapping documentation.

tab32 custom fields on any object migrate as Salesforce custom fields with the __c suffix. Field types (pick-list, date, text, number) map to equivalent Salesforce field types. tab32 formula fields require recalculation in Salesforce as formula fields or flow-triggered updates.