Migrate from PANDA Perio to Zoho CRM

PANDA Perio patient demographics (name, DOB, contact info, insurance data) map directly to Zoho CRM Contact fields. The primary address block and phone/email fields transfer 1:1. Insurance details stored in PANDA's guarantor fields map to custom text fields on the Contact record since Zoho CRM has no native insurance sub-object.

PANDA Perio's tooth-by-tooth charting (6-point probing per tooth, BOP, recession, furcation, mobility, Miller classification) has no Zoho CRM equivalent. We create a PANDA_Charting custom module with lookup to Contact. Each charting visit becomes a record in this module, preserving examination date, provider, and per-tooth findings as multi-line or subform fields.

PANDA's comparison charting — which overlays pocket depths and BOP across multiple visits to track disease progression — transfers as separate visit records within the PANDA_Charting module, all linked to the same Contact. The comparison logic (viewing 5 visits simultaneously) cannot migrate; it requires manual reconstruction in Zoho Analytics or a Zoho Creator dashboard.

PANDA Perio treatment plans (extraction sequences, implant staging, bone grafting phases) map to Zoho CRM Deals with custom fields for procedure codes (ADA codes), tooth numbers affected, treatment phase, and clinical notes. The PANDA treatment translation engine (which generates narrative for referring dentists) does not transfer — we export the treatment plan data and rebuild as Zoho Blueprint workflows or email templates.

Structured SOAP notes (Subjective, Objective, Assessment, Plan) and free-text progress notes in PANDA Perio transfer as Zoho CRM Notes attached to the Contact record. We preserve the original note date, provider name, and full note body. Rich formatting (bolding, lists) may be simplified to plain text depending on export format from PANDA's SQL database.

ADA billing codes stored in PANDA treatment plans (e.g., 7210 Surgical Extraction, 6010 Implant Fixture) can map to Zoho CRM's Products module (for line-item quoting) or stored as a multi-select pick-list custom field on the Deal record. We surface both options in the mapping plan — practices using Zoho Books for billing should use the Products module; pure clinical tracking can use custom pick-list fields.

PANDA Perio stores referring dentist names and practice information as part of the patient record. These map to Zoho CRM Account (for the referring practice) and Contact (for the individual dentist). Referral source tracking can then power Zoho CRM's campaign attribution and referral source reporting.

PANDA's Clinical Workflow Manager flags charts for follow-up actions (unconfirmed appointments, pending referral letters, unsent reports). These translate to Zoho CRM Tasks with due dates and the original flag description preserved in a custom field. PANDA's automatic letter-tracking does not transfer — rebuilding as Zoho CRM workflow rules is the recommended path.

PANDA's patient education and motivation reports (graphical comparison of probing depths, visual bone-loss diagrams) have no Zoho CRM equivalent. We export these as PDF files and attach them to the Contact record in Zoho CRM as file attachments. The interactive/motivational component requires rebuilding in a Zoho Creator app or using Zoho Show's presentation capabilities.

PANDA Perio integrates with Open Dental via the bridge module, passing patient ID and provider information. This integration data (PMS-level appointment and billing data) does not migrate to Zoho CRM — it belongs in the practice management system, not the CRM. We exclude this from the migration scope and flag it for the practice to re-establish the Open Dental integration separately.