CRM migration

Migrate from PANDA Perio to Salesforce Sales Cloud

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 logo

PANDA Perio

Source

Salesforce Sales Cloud

Destination

Salesforce Sales Cloud logo

Compatibility

100%

12 of 12

objects map 1:1 between PANDA Perio and Salesforce Sales Cloud.

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

PANDA Perio logo

PANDA Perio

What's pushing teams away

  • 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.

Choosing

Salesforce Sales Cloud logo

Salesforce Sales Cloud

What's pulling them in

  • The AppExchange marketplace with 5,000+ prebuilt apps gives enterprises integrations for nearly every business workflow without custom development.
  • Native Einstein AI for lead scoring, opportunity insights, and predictive forecasting adds intelligence without a separate platform purchase.
  • Territory management, multi-currency support, and advanced forecasting satisfy the needs of complex B2B sales organizations with structured revenue teams.
  • Slack, Tableau, and CPQ are deeply integrated into the core platform, keeping the sales stack unified for teams already in the Salesforce ecosystem.
  • Organizations with a large, established Salesforce implementation choose it because switching costs — integrations, custom code, trained admins — are prohibitive.

Object mapping

How PANDA Perio objects map to Salesforce Sales Cloud

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

maps to

Salesforce Sales Cloud

Contact

1:1
Fully supported

PANDA 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

maps to

Salesforce Sales Cloud

ClinicalExam__c

1:1
Fully supported

PANDA 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

maps to

Salesforce Sales Cloud

TreatmentPlan__c

1:1
Fully supported

PANDA 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

maps to

Salesforce Sales Cloud

TreatmentPlanLine__c

1:1
Fully supported

Each 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

maps to

Salesforce Sales Cloud

TreatmentPlanLine__c

1:1
Fully supported

Multi-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

maps to

Salesforce Sales Cloud

Contact

1:1
Fully supported

PANDA 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

maps to

Salesforce Sales Cloud

Referral__c

1:1
Fully supported

PANDA 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

maps to

Salesforce Sales Cloud

ContentDocument (Salesforce Files)

1:1
Fully supported

PANDA 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

maps to

Salesforce Sales Cloud

ClinicalExam__c

1:1
Fully supported

PeriodontalCharting 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

maps to

Salesforce Sales Cloud

ClinicalExam__c

1:1
Fully supported

PANDA 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

maps to

Salesforce Sales Cloud

Event

1:1
Fully supported

PANDA 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

maps to

Salesforce Sales Cloud

Contact

1:1
Fully supported

PANDA 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.

Gotchas + challenges

What specifically takes care here

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 logo

PANDA Perio gotchas

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

Salesforce Sales Cloud logo

Salesforce Sales Cloud gotchas

High

Workflow Rules and Process Builder are retired

High

Bulk API batch quota exhaustion during large imports

Medium

Storage overage billing is non-obvious

Medium

Account-Contact many-to-many relationship mapping

Low

Territory and team member import ordering dependencies

Pair-specific challenges

  • Periodontal charting requires one custom field per tooth surface — up to 840 probing measurements for full-mouth charting

    PANDA Perio stores 6-surface probing measurements (MB, B, DB, DL, L, ML) across 32 teeth plus implants. Salesforce has no native periodontal charting model, so every surface of every tooth requires its own custom Number field on the ClinicalExam__c object. A full-mouth exam generates up to 840 individual probing depth measurements. We name each field by surface and tooth position (e.g., PocketDepth_MB_UR6__c for the mesio-buccal of tooth #6 using the Universal numbering system). This means the field count for practices with detailed charting can reach 500+ custom fields, which is the primary driver of upper-range pricing and schema complexity. We deliver a field-inventory document before migration so the practice admin can review and approve the custom field naming scheme before data lands.

  • Multi-phase treatment plans produce multiple TreatmentPlanLine__c records — clinical narrative gets flattened into a custom text field

    PANDA Perio's Treatment Translation feature generates multi-step treatment plans spanning months — extraction, bone graft, healing phase, implant placement, abutment, restoration. Each phase becomes a separate TreatmentPlanLine__c record linked to the parent TreatmentPlan__c, preserving ADA codes, descriptions, sequence, and costs. However, the full clinical narrative from PANDA's Treatment_Notes__c field (the prose explanation written to referring dentists) is preserved as a single long-text TreatmentNotes__c field on the TreatmentPlan__c record. Practices that rely on the full prose letter rather than the procedure list should attach the original PANDA-generated letter as a Salesforce File rather than relying solely on the migrated field. We surface this decision point during the migration planning call.

  • Provider data in PANDA Perio is text-based — matching to Salesforce Contacts requires a name-normalization step

    PANDA Perio stores provider records with structured fields (name, credentials, specialty, email), but incoming referrals and outgoing correspondence may reference providers by name text strings rather than by PANDA provider record ID. During migration, FlitStack resolves each provider name string to a Salesforce Contact record using email as the primary match key and fuzzy name matching as a fallback. Provider records that cannot be matched are flagged for manual resolution before the migration commits. The original PANDA provider ID is preserved in Source_Provider_ID__c on the Contact for audit traceability. Practices with a large network of referring dentists may need a manual review step to confirm provider matches.

  • PANDA Perio runs on a local SQL Server instance — FlitStack needs direct database access to extract data

    Unlike cloud SaaS platforms, PANDA Perio stores its database on a local SQL Server instance at the practice (SQL Server 2014 Express or higher, up to 10 GB on the free edition). There is no public API endpoint for FlitStack to connect to. FlitStack accesses the PANDA database directly via SQL queries against the practice SQL Server instance. The practice must provide database access via a secure remote session, VPN, or by exporting a SQL Server backup file (.bak or .mdf) that FlitStack can restore in a secure staging environment. The access setup process adds 2–5 business days to the project timeline depending on the practice IT team's availability and security requirements. We coordinate with the practice IT administrator during the onboarding call to establish the access method before migration planning begins.

Migration approach

Six steps for a successful PANDA Perio to Salesforce Sales Cloud data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

PANDA Perio logo

PANDA Perio

Source

Strengths

  • Comprehensive tooth-by-tooth periodontal charting with 200+ clinically relevant findings in a single chart view.
  • Real-time letter generation directly from charting data, eliminating manual transcription for referral correspondence.
  • Treatment-plan memorization learns individual clinician phrasing, reducing repetitive typing over time.
  • Comparison charting across up to 5 historical visits with adjustable surgical baseline, unique among periodontal tools.
  • Clinical Workflow Manager flags overdue charts and generates task lists from charting entries, improving recall compliance.

Weaknesses

  • On-premise Windows/SQL Server deployment only — no cloud hosting, SaaS option, or macOS/Linux support.
  • No public API documented; data extraction requires direct SQL Server database access or Open Dental bridge export.
  • Small vendor team of fewer than 10 employees raises long-term viability and support responsiveness concerns.
  • Pricing is per-workstation and per-month, which scales cost higher for multi-location practices faster than per-provider SaaS models.
  • No mobile or tablet-native application; only Windows-based Tablet PC support, limiting hardware flexibility.
Salesforce Sales Cloud logo

Salesforce Sales Cloud

Destination

Strengths

  • Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow.
  • Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer.
  • Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures.
  • Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization.
  • Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.

Weaknesses

  • Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price.
  • Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise.
  • Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant.
  • API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling.
  • Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across PANDA Perio and Salesforce Sales Cloud.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    PANDA Perio: Not publicly documented.

  • Data volume sensitivity

    B

    PANDA Perio doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your PANDA Perio to Salesforce Sales Cloud migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about PANDA Perio to Salesforce Sales Cloud data migrations

Answers to the questions buyers ask most during PANDA Perio to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations complete in 2–4 weeks of clock time, with most of that spent on the test migration phase and schema setup. The actual data transfer runs 24–72 hours depending on the number of patient records and how many clinical exams are stored per patient. FlitStack extracts the data directly from PANDA's SQL Server database and loads it into Salesforce via the Bulk API. Practices with complex multi-phase treatment plans across hundreds of patients fall toward the 10-day end of the range.

Adjacent paths

Related migrations to explore

Ready when you are

Move from PANDA Perio.
Land in Salesforce Sales Cloud, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day