Migrate your PANDA Perio data
Specialty periodontal charting and letter-writing software for periodontists. On-premise SQL Server application with no public API and no published migration tooling.
In its favor
Why people choose PANDA Perio
The signal that keeps PANDA Perio on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Periodontists choose PANDA Perio because it eliminates 5+ hours per week of manual letter writing by auto-generating referral correspondence from chairside charting entries.
Practices with complex periodontal cases value PANDA's 200+ chartable findings per tooth, covering everything from probing depth to furcation classification, all visible on a single screen.
Periodontists migrating from paper charts cite PANDA's memorization of individualized treatment-plan phrasing as the primary reason — the software adapts to how each clinician writes, reducing repetitive data entry over time.
Multi-location periodontal practices with existing Open Dental installations use PANDA's bridge to pass patient IDs and maintain synchronization between their practice management system and periodontal charting module.
Clinicians report that PANDA's comparison charting across up to 5 visits simultaneously gives them a powerful patient-education tool that general-practice CRMs cannot replicate.
The on-premise-only deployment requires dedicated Windows Server infrastructure and IT maintenance, pushing cost-conscious practices toward cloud-based alternatives with no local setup overhead.
No public REST API means integrations beyond Open Dental must be custom-built and maintained, frustrating practices that need bidirectional data flow with modern cloud platforms.
The small vendor team — three named employees with a 2-person management structure — raises concern for practices worried about long-term support continuity and software updates.
Larger multi-clinic periodontal groups report that SQL Server Express hits its 10GB database limit sooner than expected, forcing a costly SQL Server upgrade with no clear migration path documented.
Reasons to switch
Why people leave PANDA Perio
The recurring reasons buyers give for replacing PANDA Perio. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where PANDA Perio fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
PANDA Perio pricing overview
Pricing is per-practice based on workstation count rather than user count. The base license covers 5 workstations and 5 users; additional users beyond 5 are not individually priced but additional workstations carry per-seat fees. PANDA EMR is roughly 2.5–4× the cost of PANDA Lite depending on billing cycle, with annual billing providing meaningful savings.
PANDA Lite
Tier 1 of 3
$99/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on PANDA Perio's schedule — see our quote-based pricing →
What gets migrated
PANDA Perio object support
Object-by-object support for PANDA Perio migrations. Per-pair details surface during scoping.
Patients
Mapping requiredPatient records are identified by PatNum or ChartNum depending on how the office configured the Open Dental bridge. We map both identifiers and reconcile duplicates where practices have used both numbering schemes. Name, contact info, and guarantor fields are straightforward SQL columns.
Periodontal Charting
Mapping requiredCharting data is stored across multiple SQL tables tracking probing depth, BOP, gingival recession, furcation involvement, and tooth mobility per surface per tooth. We reconstruct the full periodontal record by joining encounter dates to tooth-specific findings. Custom finding types require field mapping against the destination schema.
Treatment Plans
Mapping requiredPANDA distinguishes between a PMS billing-code treatment plan (ADA codes) and a clinical letter treatment plan (step-by-step procedure narrative). Both exist in the database and we map them separately — the PMS version maps to the destination billing module, the clinical version maps to the patient letter record.
Progress Notes
Fully supportedSOAP notes, clinical notes, and treatment notes are stored as structured text fields in the encounter record. We extract them in full and import them as clinical note objects in the destination, preserving provider attribution and encounter timestamps.
Letters and Reports
Mapping requiredPANDA generates dynamic letters from charting data at the point of care. We export the final rendered letter content and metadata (letter type, referring dentist, generation date). Because letters are derived from charting, we validate that source data was migrated first.
Encounters/Visits
Fully supportedEncounter records are identified by date, provider, and patient. We import encounter history including visit reason, provider name, and associated clinical findings. Visit sequences are preserved to support periodontal comparison reports in the destination.
Referrals and Referring Dentists
Mapping requiredReferring dentist information is stored as structured contact records and referenced in letter templates. We map referring dentist names, addresses, and practice information to the destination's referral contact object.
Custom Findings and Templates
Mapping requiredPANDA allows practices to add custom clinical findings beyond the standard 200+ built-in entries. These are stored as user-defined fields in the database. We flag custom findings during discovery and map them to custom fields in the destination, noting any that have no direct equivalent.
Clinical Workflow Tasks
Mapping requiredThe Clinical Workflow Manager tracks flagged charts and pending tasks. Task records include patient reference, task type, flag status, and due date. We import task status and patient association; open tasks are flagged for the practice to verify in the new system.
Patient Motivation Reports
Mapping requiredPANDA generates patient-facing motivation reports from clinical findings to support case acceptance conversations. We export report content and the clinical data snapshot used to generate it. The destination system may require re-generation from the underlying charting data.
| Object | Support | Notes |
|---|---|---|
| Patients | Mapping required | Patient records are identified by PatNum or ChartNum depending on how the office configured the Open Dental bridge. We map both identifiers and reconcile duplicates where practices have used both numbering schemes. Name, contact info, and guarantor fields are straightforward SQL columns. |
| Periodontal Charting | Mapping required | Charting data is stored across multiple SQL tables tracking probing depth, BOP, gingival recession, furcation involvement, and tooth mobility per surface per tooth. We reconstruct the full periodontal record by joining encounter dates to tooth-specific findings. Custom finding types require field mapping against the destination schema. |
| Treatment Plans | Mapping required | PANDA distinguishes between a PMS billing-code treatment plan (ADA codes) and a clinical letter treatment plan (step-by-step procedure narrative). Both exist in the database and we map them separately — the PMS version maps to the destination billing module, the clinical version maps to the patient letter record. |
| Progress Notes | Fully supported | SOAP notes, clinical notes, and treatment notes are stored as structured text fields in the encounter record. We extract them in full and import them as clinical note objects in the destination, preserving provider attribution and encounter timestamps. |
| Letters and Reports | Mapping required | PANDA generates dynamic letters from charting data at the point of care. We export the final rendered letter content and metadata (letter type, referring dentist, generation date). Because letters are derived from charting, we validate that source data was migrated first. |
| Encounters/Visits | Fully supported | Encounter records are identified by date, provider, and patient. We import encounter history including visit reason, provider name, and associated clinical findings. Visit sequences are preserved to support periodontal comparison reports in the destination. |
| Referrals and Referring Dentists | Mapping required | Referring dentist information is stored as structured contact records and referenced in letter templates. We map referring dentist names, addresses, and practice information to the destination's referral contact object. |
| Custom Findings and Templates | Mapping required | PANDA allows practices to add custom clinical findings beyond the standard 200+ built-in entries. These are stored as user-defined fields in the database. We flag custom findings during discovery and map them to custom fields in the destination, noting any that have no direct equivalent. |
| Clinical Workflow Tasks | Mapping required | The Clinical Workflow Manager tracks flagged charts and pending tasks. Task records include patient reference, task type, flag status, and due date. We import task status and patient association; open tasks are flagged for the practice to verify in the new system. |
| Patient Motivation Reports | Mapping required | PANDA generates patient-facing motivation reports from clinical findings to support case acceptance conversations. We export report content and the clinical data snapshot used to generate it. The destination system may require re-generation from the underlying charting data. |
Gotchas
What to watch for in PANDA Perio migrations
Issues we've hit on past PANDA Perio migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No public API — database extraction requires SQL Server access
SQL Server Express 10GB limit can be migration-blocking
Open Dental bridge passes IDs only, not clinical data
Treatment plan PMS codes differ from clinical letter descriptions
Custom periodontal findings are practice-specific
| Severity | Issue |
|---|---|
| High | No public API — database extraction requires SQL Server access |
| High | SQL Server Express 10GB limit can be migration-blocking |
| Medium | Open Dental bridge passes IDs only, not clinical data |
| Medium | Treatment plan PMS codes differ from clinical letter descriptions |
| Low | Custom periodontal findings are practice-specific |
Leaving PANDA Perio?
Where PANDA Perio customers move next
12 destinations PANDA Perio can migrate to.
How a PANDA Perio migration works
Four steps, PANDA Perio-specific
Connect
Not publicly documented into PANDA Perio. Scopes limited to read-only on the data we move.
Map
We translate PANDA Perio-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate PANDA Perio quirks before production.
Migrate
Full migration with PANDA Perio rate-limit handling. Rollback available throughout.
FAQ
PANDA Perio migration FAQ
Answers to the questions buyers ask most during PANDA Perio migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your PANDA Perio migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate PANDA Perio.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your PANDA Perio setup and destination — written quote back within a business day.