Migrate from PANDA Perio to Nutshell

Panda Perio clinical data has no native CRM equivalent in Nutshell — everything beyond basic contact fields requires custom field creation

Panda Perio's data model is built around periodontal charts, probing measurements, procedure codes, and treatment-plan phasing — none of which have a home in Nutshell's standard Person/Account/Lead/Deal schema. Every probing depth, mobility grade, furcation classification, and CDT code must be either mapped to a custom field on the Person record or collapsed into a Note attachment. We create the custom fields upfront during the Nutshell schema setup phase, but the practice should audit which clinical fields are actually needed in the CRM versus which can remain as reference notes only. Over-mapping clinical data into Nutshell custom fields creates maintenance burden without CRM utility.

Panda Perio's letter-generation templates and automated correspondence do not export as usable templates in Nutshell

One of Panda Perio's core value propositions is its ability to auto-generate referral letters, patient letters, and clinical correspondence directly from charting data. These letter templates are tied to PANDA's template engine and do not export as standalone documents or Nutshell-compatible templates. We migrate the generated letter output as Note attachments on the Person record for historical reference, but the template logic itself cannot be transferred. Practices that rely on automated letter generation need to decide whether to continue using Panda Perio for that workflow or rebuild letter templates in a dedicated correspondence tool that integrates with Nutshell.

Referring doctor and provider relationships require deliberate Account linkage design before migration runs

Panda Perio tracks referring doctors and provider relationships as separate entity records linked to patients. In Nutshell, these need to become either Account records (for the referring practice) or custom Account-lookup fields on the Person record. If the practice has a large network of referring dentists, every referral link must be reconstructed in Nutshell manually after migration or via a custom junction field we create during the schema setup. The mapping plan for these relationships must be confirmed before the migration runs because retroactive linkage reconstruction is time-intensive.

Panda Perio workstation-per-seat licensing and multi-location setups complicate user provisioning in Nutshell

Panda Perio licenses are priced per workstation, not per user, and practices with 5–100 workstations pay accordingly. When migrating to Nutshell's per-user model, the practice needs to decide which staff members actually need CRM access. Clinical staff who only use Panda Perio for charting may not need Nutshell seats. We flag this during scoping and can provide a seat-sizing recommendation, but the seat assignment decision belongs to the practice's admin — provisioning too many Nutshell seats inflates the monthly cost, and provisioning too few creates data-access gaps for staff who need to see referral and case-status information.

Insurance and billing metadata from Panda Perio requires manual cleanup before it lands cleanly in Nutshell custom fields

Panda Perio insurance fields (carrier name, group number, subscriber ID, coverage type) are often entered freeform by clinical staff and contain inconsistencies — missing values, outdated carrier names, or merged payer records from past acquisitions. Nutshell's custom fields are plain text, so inconsistent data from Panda Perio transfers as-is unless pre-migration data cleansing is performed. We flag records with missing or malformed insurance fields before migration and provide a cleansing checklist, but the practice staff responsible for billing data owns the cleanup decision.