Migrate from Pure Chart to Nutshell

Clinical tooth-chart data and procedure codes have no native Nutshell home

Pure Chart stores tooth-chart observations, ADA procedure codes, and clinical notes as structured objects. Nutshell's schema has no clinical equivalent — it is built for general sales and marketing contacts. Tooth numbers, surface designations, and per-tooth procedure flags must be stored as custom text fields on Person or Deal records, or attached as notes. Your team will need to review these post-migration to determine whether to collapse clinical data into summary fields or keep it as reference notes. FlitStack surfaces the full structure in the mapping plan so your Nutshell admin can decide how to display it.

Appointment scheduling is not transferable — the calendar lives outside Nutshell

Pure Chart appointments are native schedule objects with provider, slot time, room, and procedure type. Nutshell has no built-in appointment scheduling object — it supports Activities and Tasks but not a calendar-slot model. We map appointments to Nutshell Deals representing the treatment plan with the scheduled date as a reference field, and create Activity records for the time slot. Actual re-booking of future appointments requires a calendar integration (Google Calendar, Outlook) configured in Nutshell after migration, or a rebuild of the recall workflow using Nutshell email sequences.

Insurance carrier and policy data requires custom field creation before data lands

Every patient in Pure Chart carries insurance carrier name, policy number, group number, and coverage percentage. Nutshell has no native insurance field on the Person object. Before migration runs, your Nutshell admin (or our team) must create four custom fields on the Person object: Insurance_Carrier__c, Insurance_Policy_Number__c, Insurance_Group_Number__c, and Insurance_Coverage_Percent__c. If these fields do not exist at migration time, insurance data is either skipped or stored in a generic notes field. We flag this as a pre-migration requirement in the schema setup plan.

Recall and follow-up sequences must be rebuilt — Pure Chart automation does not transfer

Pure Chart recall reminders (e.g., six-month hygiene recall, post-procedure follow-up) and automated patient communications are built within Pure Chart's workflow engine. These have no equivalent in Nutshell's automation model. Nutshell offers email sequences and task rules but the logic is platform-specific. FlitStack can export your Pure Chart workflow definitions as a reference document for your Nutshell admin to use during the rebuild phase, but the automations themselves do not migrate.

Multi-location practices create one Company per location in Nutshell

Pure Chart supports multi-location dental organizations with separate practice records. In Nutshell, each location becomes a separate Company record. If Pure Chart stores a parent-organization hierarchy, that hierarchy does not map to any native Nutshell construct — we store the parent organization name as a custom field on each location's Company record. Contact assignments (which provider at which location sees which patient) require post-migration review to ensure Person-to-Company associations are accurate across all locations.