Migrate from PANDA Perio to HighLevel

PANDA Perio patient records map directly to HighLevel Contacts using a one-to-one field mapping. The patient's legal name, date of birth, contact phone numbers including mobile, email address, and full mailing address all transfer as standard Contact fields in HighLevel. This mapping preserves the complete patient identity information needed for day-to-day practice operations. HighLevel's contact record becomes the primary patient identity after migration and serves as the central record for all patient-related data.

PANDA Perio's clinical summary fields — last periodontal classification (Healthy / Gingivitis / Stage I–IV / Periodontitis), most recent probing depths per sextant, and BOP percentage — do not have a native HighLevel equivalent. We create custom fields on the Contact record: Last_Perio_Classification__c, Last_Probing_Summary__c, BOP_Percentage__c, and Last_Exam_Date__c.

PANDA Perio's charting comparison report — displaying up to 5 visits side-by-side with color-coded change indicators — is a rendered report with no structural equivalent in HighLevel. We export this report as a PDF from PANDA and attach it to the corresponding HighLevel Contact record. The PDF preserves the visual clinical context that cannot be stored in text fields alone.

A PANDA Perio treatment plan (e.g., 'Non-surgical periodontal therapy, 3-month re-evaluation, potential implant site preparation') maps to a HighLevel Opportunity. The plan name becomes the Opportunity name, the estimated treatment value maps to Amount, and a custom 'Treatment_Stage__c' field tracks phases: Diagnosis, Active Therapy, Re-evaluation, Maintenance.

PANDA Perio treatment plan phases — Diagnosis, Initial Therapy, Re-evaluation, Surgical Therapy, Maintenance — map to custom HighLevel pipeline stage values. We configure a 'Perio Treatment' pipeline in HighLevel with these stages so the periodontal treatment workflow is visible as a standard Opportunity pipeline.

PANDA Perio tracks referring dentists and their practices for correspondence. These map to HighLevel Company records. The referring practice name, address, phone, and website transfer as standard Company fields. Each Contact's primary referral source is linked to the corresponding Company via the Contact-to-Company relationship.

PANDA Perio visit records — appointment date, procedure type, provider name, and clinical notes — map to HighLevel Tasks or Appointments linked to the Contact. Original visit dates are preserved in the task start time; procedure descriptions become the task subject or appointment title.

PANDA Perio's InstaNotes system generates structured progress notes from charting data. These transfer as HighLevel Notes attached to the Contact record. The structured nature of InstaNotes means they render cleanly as text notes without needing PDF conversion, unlike the charting comparison report.

PANDA Perio stores primary and secondary insurance carrier names and group numbers. HighLevel has no native insurance field. We create custom fields Insurance_Primary_Carrier__c, Insurance_Group_Number__c, and Insurance_Secondary_Carrier__c on the Contact record to preserve this information for front-desk staff reference.

Each PANDA Perio patient record has an internal system identifier used for record management within the platform. We store this identifier as a custom field Source_System_ID__c on the corresponding HighLevel Contact record. This field enables delta-run deduplication if the migration runs incrementally rather than in a single batch, ensuring no duplicate records are created during phased migration approaches. The field also serves as a permanent audit trail linking each HighLevel record back to its source PANDA Perio entry.

PANDA Perio's clinical recall triggers — scheduling patients for periodontal maintenance based on AAP classification intervals (e.g., 3-month recall for Stage III/IV, 6-month for Stage I/II) — are built-in clinical logic with no HighLevel equivalent. These must be rebuilt as HighLevel Workflows using date-based triggers and the Last_Exam_Date__c custom field we migrate. FlitStack provides a rebuild reference document as part of the migration package.