CRM migration
Field-level mapping, validation, and rollback between PANDA Perio and Salesforce Sales Cloud. We move data and schema; workflows are rebuilt natively in Salesforce Sales Cloud.
PANDA Perio
Source
Salesforce Sales Cloud
Destination
Compatibility
12 of 12
objects map 1:1 between PANDA Perio and Salesforce Sales Cloud.
Complexity
BStandard
Timeline
24–48 hours
Overview
PANDA Perio is clinical periodontal charting software purpose-built for periodontists. It stores patient demographics, tooth-by-tooth probing depths across six surfaces per tooth, bleeding-on-probing scores, treatment plans with ADA procedure codes, provider records, referral data, and correspondence letters — all in a SQL Server database on the practice network. Salesforce Sales Cloud has no native periodontal charting model, so FlitStack AI builds custom ClinicalExam__c, TreatmentPlan__c, TreatmentPlanLine__c, and Referral__c objects to hold every clinical record. We extract data directly from the PANDA Perio SQL Server via FlitStack's database connector, resolve provider names to Salesforce Contacts, and load everything via Salesforce Bulk API. Workflow automations are not a migration concern because PANDA Perio has none — any middleware integrations (Open Dental bridge, referral portals) must be rebuilt in Salesforce. The delta-pickup window captures any records modified in PANDA during the cutover so Salesforce reflects the final clinical state at go-live. The migration also preserves the original tooth numbering system used in PANDA (Universal, Palmer, or FDI) so the clinical team can interpret migrated charting data correctly without ambiguity.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a PANDA Perio object lands in Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
PANDA Perio
Patient
Salesforce Sales Cloud
Contact
1:1PANDA Perio Patient maps to Salesforce Contact. Core demographics (name, DOB, address, phone, email) map directly to standard Contact fields. The original PANDA chart number is preserved in PANDA_Chart_Number__c custom field for reference and delta-run de-duplication. This ensures each patient record can be uniquely identified across both systems and that any records created during the cutover window can be matched without creating duplicates in Salesforce.
PANDA Perio
PeriodontalCharting
Salesforce Sales Cloud
ClinicalExam__c
1:1PANDA Perio's periodontal charting (exam date, tooth numbering system, 6-surface probing, BOP, recession, mobility, furcation, plaque index) maps to a custom ClinicalExam__c object. Each surface of each tooth requires its own custom field (e.g., PocketDepth_MB__c, Recession_DB__c) since Salesforce has no native periodontal charting model.
PANDA Perio
PeriodontalCharting
Salesforce Sales Cloud
TreatmentPlan__c
1:1PANDA Perio TreatmentPlan maps to Salesforce custom TreatmentPlan__c object. Each plan links to the patient Contact via TreatmentPlan__c.Contact__c lookup. Status (proposed, accepted, in-progress, completed) maps to a custom Status__c pick-list field. ADA procedure codes stored in TreatmentPlanLine__c records linked to the parent TreatmentPlan__c.
PANDA Perio
PeriodontalCharting
Salesforce Sales Cloud
TreatmentPlanLine__c
1:1Each PANDA Perio treatment plan can contain multiple phases (extraction, bone graft, healing period, implant placement, restoration). Each phase becomes a separate TreatmentPlanLine__c record linked via TreatmentPlanLine__c.TreatmentPlan__c lookup. ADA_Code__c, Description__c, ToothSite__c, Sequence__c, and EstimatedCost__c are preserved from the source plan.
PANDA Perio
PeriodontalCharting
Salesforce Sales Cloud
TreatmentPlanLine__c
1:1Multi-phase treatment plans spanning months (PANDA Perio's Treatment Translation feature) produce complex, multi-step plans. Each clinical phase in the PANDA plan becomes a separate TreatmentPlanLine__c record. The full clinical narrative from PANDA's Treatment_Notes__c field is preserved in TreatmentPlan__c.Treatment_Notes__c custom text field.
PANDA Perio
Provider
Salesforce Sales Cloud
Contact
1:1PANDA Perio provider records (name, credentials, specialty, email) map to Salesforce Contacts with a custom Provider__c checkbox set to true. The original provider ID from PANDA is stored in Source_Provider_ID__c for traceability. A separate Salesforce user license is required if the provider needs login access to the Salesforce org.
PANDA Perio
Referral
Salesforce Sales Cloud
Referral__c
1:1PANDA Perio stores both incoming and outgoing provider-to-provider referrals with referring provider name, contact info, referral type, status, and notes. A custom Referral__c object with a Contact__c lookup to the patient captures all referral fields including Referral_Status__c pick-list (received, sent, accepted, declined, completed) and dates.
PANDA Perio
Letter
Salesforce Sales Cloud
ContentDocument (Salesforce Files)
1:1PANDA Perio generates correspondence letters for patients, specialists, and referring dentists. Letters and documents attach to the patient Contact record as Salesforce Files. The original PANDA chart number is preserved in a custom ChartNumber__c field on the ContentDocument link for traceability back to the source record.
PANDA Perio
PeriodontalCharting
Salesforce Sales Cloud
ClinicalExam__c
1:1PeriodontalCharting records with detailed 6-surface probing across all 32 teeth (plus implants) require up to 840 individual probing measurements. FlitStack maps each surface to a named custom field on ClinicalExam__c (e.g., PocketDepth_MB_UR6__c for the mesio-buccal of tooth #6 in the universal numbering system) to preserve the full clinical picture.
PANDA Perio
PeriodontalCharting
Salesforce Sales Cloud
ClinicalExam__c
1:1PANDA Perio stores the tooth numbering system used (Universal, Palmer, FDI) in the PeriodontalCharting record. This is preserved in ToothNumberingSystem__c pick-list on ClinicalExam__c so the clinical team knows which system was used when reviewing migrated records. This is critical for practices that used different numbering conventions across providers or locations to avoid misinterpretation of tooth positions in the migrated charting data.
PANDA Perio
Appointment
Salesforce Sales Cloud
Event
1:1PANDA Perio appointment records (session type, date, duration, provider) map to Salesforce Events with custom SessionType__c and Duration__c fields. The Appointment_ID__c from PANDA is preserved for reference. Events link to the patient Contact and provider Contact via standard WhoId and ContactId fields.
PANDA Perio
Provider
Salesforce Sales Cloud
Contact
1:1PANDA Perio provider credentials (DDS, DMD, MS, Board Certified) are stored as free text. FlitStack normalizes these into a custom Credentials__c multi-select pick-list on the Contact record. Specialty (Periodontics, Oral Surgery, Prosthodontics, General Dentistry) maps to a custom Specialty__c pick-list on the Contact.
| PANDA Perio | Salesforce Sales Cloud | Compatibility | |
|---|---|---|---|
| Patient | Contact1:1 | Fully supported | |
| PeriodontalCharting | ClinicalExam__c1:1 | Fully supported | |
| PeriodontalCharting | TreatmentPlan__c1:1 | Fully supported | |
| PeriodontalCharting | TreatmentPlanLine__c1:1 | Fully supported | |
| PeriodontalCharting | TreatmentPlanLine__c1:1 | Fully supported | |
| Provider | Contact1:1 | Fully supported | |
| Referral | Referral__c1:1 | Fully supported | |
| Letter | ContentDocument (Salesforce Files)1:1 | Fully supported | |
| PeriodontalCharting | ClinicalExam__c1:1 | Fully supported | |
| PeriodontalCharting | ClinicalExam__c1:1 | Fully supported | |
| Appointment | Event1:1 | Fully supported | |
| Provider | Contact1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
PANDA Perio gotchas
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
Salesforce Sales Cloud gotchas
Workflow Rules and Process Builder are retired
Bulk API batch quota exhaustion during large imports
Storage overage billing is non-obvious
Account-Contact many-to-many relationship mapping
Territory and team member import ordering dependencies
Pair-specific challenges
Migration approach
Extract data from PANDA Perio SQL Server database
FlitStack connects to the PANDA Perio SQL Server database on the practice network using read-only credentials. We extract all core tables: Patient (demographics, chart number), Provider (names, credentials, specialty), ClinicalExam (exam dates, charting type), PeriodontalCharting (all 6-surface probing measurements per tooth), TreatmentPlan and TreatmentPlanLine (ADA codes, descriptions, costs, status, notes), Referral (source, type, status, dates), Letter and Document (file names, binary content), and Appointment (session type, date, duration). We run SQL queries directly against the database to produce structured exports. This step is read-only — the PANDA Perio system remains fully operational during extraction.
Build Salesforce custom object schema and field inventory
Based on the PANDA Perio data model, FlitStack creates the Salesforce custom objects needed: ClinicalExam__c (with up to 840 probing depth fields, recession fields, BOP, mobility, furcation, plaque index), TreatmentPlan__c (with status, treatment type, estimated cost, clinical notes), TreatmentPlanLine__c (with ADA code, description, tooth/site, sequence, cost), and Referral__c (with referral type, status, referrer name, dates). We also add custom fields to the Contact record: PANDA_Chart_Number__c, Provider__c flag, Credentials__c pick-list, Specialty__c pick-list. FlitStack delivers a field-inventory document listing every custom field, its source column in PANDA, and the Salesforce API name before any data is loaded.
Run sample migration with field-level validation
A representative sample of 20–50 patient records migrates first — covering patients with simple and complex charting (full-mouth probing, multiple treatment plans, referrals). We generate a field-level diff between the PANDA Perio source data and the Salesforce destination records so the practice can verify that probing depths landed in the correct custom fields, ADA codes appear on the right TreatmentPlanLine__c records, and provider names resolved to the correct Contact. The sample migration validates the tooth numbering system mapping (Universal vs. Palmer vs. FDI) and confirms that multi-phase treatment plans produce the correct number of line items. No records are committed to the live Salesforce org during this step.
Execute full migration with delta-pickup window
The full patient record set migrates to Salesforce with Contact records created first (to resolve AccountId lookups for clinical exam and treatment plan links), followed by ClinicalExam__c records, TreatmentPlan__c and TreatmentPlanLine__c records, Referral__c records, and provider Contact records. Documents and letters from PANDA are re-uploaded as Salesforce Files and linked to the correct Contact record. A delta-pickup window of 24–48 hours runs in parallel: any records created or modified in PANDA Perio during the cutover window are synced to Salesforce so the destination reflects the final state at go-live. FlitStack generates a migration audit log and a record-count reconciliation report. One-click rollback is available if reconciliation identifies critical mismatches.
Post-migration review and go-live confirmation
FlitStack delivers a post-migration report showing record counts by object, a list of any records that failed validation with the root cause, and a sample of successfully migrated records for manual spot-checking. We walk the practice through the custom Salesforce objects, explain how to find migrated clinical data on each Contact record, and demonstrate how the TreatmentPlan__c pipeline view differs from the PANDA Perio treatment plan view. Any remaining delta records from the cutover window are committed. The practice confirms go-live readiness. Ongoing support for data corrections in Salesforce is available under the standard FlitStack post-migration service agreement.
Platform deep dives
PANDA Perio
Source
Strengths
Weaknesses
Salesforce Sales Cloud
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across PANDA Perio and Salesforce Sales Cloud.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
PANDA Perio: Not publicly documented.
Data volume sensitivity
PANDA Perio doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during PANDA Perio to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.
Walk through your PANDA Perio to Salesforce Sales Cloud migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave PANDA Perio
Other ways to arrive at Salesforce Sales Cloud
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.