Migrate from tab32 to Nutshell

tab32 Patient records map 1:1 to Nutshell Person records. The patient's full name splits into firstName and lastName on the Nutshell Person. DOB, address, phone, and email transfer as standard fields. Insurance data and recall-interval fields become Nutshell custom fields on the Person record.

tab32 practice locations map to Nutshell Company records. Practice name, address, phone, and timezone transfer as standard Company fields. For DSOs with parent-company hierarchies, the top-level DSO becomes the parent Company in Nutshell and each location is a child Company linked via the parentId relationship.

tab32 appointments map to Nutshell Tasks (for tasks like follow-up calls) and Events (for scheduled visits). The appointment date and time become the Task due date or Event start/end time. Provider ID resolves to the Nutshell User by email match. CDT procedure codes, appointment type (hygiene, restorative, surgical), and operatory location become custom fields on the Activity record.

tab32 treatment plans include procedure description, CDT code, treatment status (proposed, accepted, completed), estimated cost, and provider recommendation. These transfer as a structured Note on the associated Person record in Nutshell. Active treatment-plan status is preserved as a custom pick-list field on the Person so sales or ops teams can see ongoing care context at a glance.

tab32 provider profiles (dentist name, specialty, NPI number) map to Nutshell User records via email match. When a provider is a treating clinician on a patient record without a corresponding Nutshell login, the provider name and specialty migrate as a custom field on the Person record so clinical attribution is preserved.

tab32 stores insurance carrier name, group number, subscriber ID, subscriber relationship, and coverage percentages per patient. Nutshell has no native insurance fields, so FlitStack creates custom text and pick-list fields on the Person record: Insurance_Carrier__c, Insurance_Group_Number__c, Insurance_Subscriber_ID__c, and Coverage_Level__c (single/family).

tab32 recall intervals trigger re-care appointments (e.g., 6-month hygiene recall). The next recall date migrates as a custom date field (Next_Recall_Date__c) on the Person record in Nutshell. This enables ops teams to build task automations in Nutshell around recall follow-up without rebuilding from scratch.

tab32 tooth-chart and perio exam data are clinical records with procedure-level detail. Because Nutshell is a CRM and not a clinical system, this data migrates as structured Notes attached to the Person record. FlitStack maps perio pocket-depth readings to a Note with a standardized format (Tooth-Surface-Pocket-Depth) so clinical staff can review historical perio status in Nutshell.

tab32 insurance claim records include claim status (submitted, pending, paid, denied), amount billed, amount paid, and adjusted amount. Claim status and last-claim-date migrate as custom fields on the Person record. Each claim submission date becomes a Note or Task on the Person so the billing history is accessible to the ops team in Nutshell.

tab32 patient attachments (insurance cards, treatment consent forms, imaging referrals) are files associated with a patient record. FlitStack downloads these files and re-uploads them as attachments on the corresponding Nutshell Person record. File size limits follow Nutshell's attachment constraints. Files that exceed size limits are converted to hosted links stored as a Note.

tab32 tracks outstanding patient balances and accounts receivable. The current balance migrates as a custom currency field (Outstanding_Balance__c) on the Nutshell Person record. This is a reference field only — revenue cycle management is handled in the dental PMS or billing system, not in Nutshell's CRM context.

tab32 prospective patients (leads from marketing campaigns, new-patient intake forms, or walk-in inquiries) map directly to Nutshell Lead records. Lead source, inquiry date, and referred-by information transfer as standard Nutshell Lead fields or custom fields if tab32 captures additional referral context.