How long does a PANDA Perio to Freshsales migration take?

Most PANDA Perio to Freshsales migrations complete within 48-72 hours for practices with fewer than 1,000 patient records and straightforward charting data. Practices with 5,000+ patient records, multiple providers, and active treatment plan histories extending back several years typically require 7-14 days. The longest phase is usually the custom field schema setup in Freshsales — each periodontal charting dimension (pocket depths, BOP, furcation, mobility, recession, staging/grading) requires a separate custom field, and the field creation and validation step takes 2-4 days. The migration run itself is 4-8 hours of clock time for most practices.

Will my PANDA Perio letter templates and workflow automations migrate to Freshsales?

No. FlitStack AI migrates data and schema only — PANDA letter templates, periodontal chart templates, appointment reminder automations, and treatment plan milestone alerts do not transfer. Freshsales has no native letter auto-population feature that mirrors PANDA's instant letter writing module. Your admin must rebuild PANDA letter templates as Freshsales email templates using merge fields, and any PANDA workflow automations must be recreated in Freshsales Workflows. FlitStack delivers a Letter Template Reference Document capturing your PANDA template field names and merge field structure to guide the rebuild. Workflow logic from PANDA is documented as a Workflow Rebuild Checklist for your admin.

What happens to my periodontal charting data (probing depths, BOP, furcation) in Freshsales?

Periodontal charting data — probing depths, bleeding on probing, furcation involvement, mobility, recession, and AAP stage/grade classification — has no native Freshsales equivalent since Freshsales is a sales CRM, not a clinical system. Each charting dimension becomes a separate custom field on the Contact record (e.g., Pocket_Depth_Avg_MM__c, BOP__c, Furcation__c, Mobility__c, Periodontal_Stage__c, Periodontal_Grade__c). The most recent visit's values migrate for each patient. Full longitudinal per-visit charting history is not typically migrated due to the tooth-site-level volume; if you need historical charting in Freshsales, discuss a per-visit charting log custom object with FlitStack before the migration run.

Can I migrate PANDA Perio treatment plans with CDT procedure codes to Freshsales?

Yes. PANDA Perio treatment plans map to a two-part structure in Freshsales: the overall case becomes a Freshsales Deal (with Deal Stage reflecting treatment status: Proposed, Accepted, In Treatment, Completed) and individual procedure line items (CDT codes, tooth sites, phases, scheduled dates) become records in a Dental_Treatment_Plan__c custom object linked to the Deal. The custom object must be created in Freshsales before migration — it requires Freshsales Pro or Enterprise plan. CDT codes migrate as text in Procedure_Code__c custom field. If your PANDA treatment plans include multi-phase sequences with healing intervals, the phase data maps to a Treatment_Phase__c custom pick-list (Phase I: Non-Surgical, Phase II: Surgical, Phase III: Maintenance).

How does PANDA Perio referral tracking map to Freshsales?

PANDA Perio referral tracking (referring dentist name, practice, referral date, referral count per source) maps to Freshsales Contacts with a Referring_Dentist__c custom checkbox. The referring dentist's practice name stores in the Contact's Company field. Referral date and total referral count per dentist store as custom date and number fields for reporting on top referral sources. The many-to-many relationship between one referring dentist and multiple patient cases requires a custom Referral_Case__c junction object if you need Freshsales reports showing which referral cases converted to accepted treatment — this is included in the migration plan if requested before the schema setup phase.

Does the migration affect my PANDA Perio account during the cutover?

No. FlitStack AI uses scoped read access to export data from PANDA Perio's SQL Server database — your team continues working in PANDA Perio throughout the migration. New patients added, appointments scheduled, and treatment plans updated in PANDA during the cutover window are captured in a 24-48 hour delta-pickup phase after the initial migration run. The delta pickup ensures Freshsales reflects PANDA's final state at go-live. No data is modified or deleted in PANDA during the migration. After the delta pickup is confirmed clean, the practice can sunset PANDA Perio or keep it running for clinical access only.

What Freshsales plan do I need to migrate all my PANDA data?

For a PANDA Perio migration, Freshsales Growth ($9/user/mo) covers standard Contact, Account, Deal, Event, and Note fields plus custom fields on those objects. The Pro plan ($39/user/mo) is required if you need custom objects — specifically the Dental_Treatment_Plan__c custom object for treatment plan procedure codes and phases. The custom objects feature (available in Pro and Enterprise) is the key plan differentiator for this migration. If your practice has fewer than 3 users and only needs Contact-level charting data migration (no treatment plan custom object), Growth may suffice. For multi-provider practices with active treatment plan pipelines, Pro is the recommended minimum. Enterprise adds field-level permissions and audit logs useful for multi-location practices.

How do I export data from PANDA Perio if I only have the desktop application?

PANDA Perio stores data in a SQL Server database on your office server (Express for small practices, Standard/Enterprise for larger setups). The export options are: (1) SQL Server query export — your IT admin or PANDA support runs a query against the PANDA database to extract patient records, clinical charts, treatment plans, and provider data into CSV files. This is the most complete option and captures all historical charting data. (2) PANDA built-in reports — the PANDA UI has exportable patient list reports and treatment plan reports accessible from the Reports menu, but these are limited to fields displayed in the UI and may not include tooth-site-level charting data. FlitStack can guide your PANDA admin through either export method and provide the field-to-CSV mapping required.

PANDA Perio to Freshsales Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

PANDA Perio and Freshsales occupy fundamentally different software categories, which makes this migration a cross-category data consolidation rather than a like-for-like platform switch. PANDA Perio stores periodontal charting, treatment plans, provider profiles, and clinical findings in a Windows-based SQL Server environment — it is a clinical record system designed for periodontists who manage complex periodontal cases and refer relationships with general dentists. Freshsales is a cloud-based CRM built for sales teams; its core objects are Leads, Contacts, Accounts, Deals, and Events with no native clinical or dental equivalent. FlitStack AI bridges this gap by mapping PANDA patient records to Freshsales Contacts, provider profiles to Contact records with custom role fields, and periodontal charting data to custom fields on the Contact object (Last_Pocket_Depth_MM__c, Gingival_Recession_MM__c, BOP__c, Furcation_Involvement__c, Mobility__c). Treatment plans and scheduled procedures map to Freshsales Deals with a custom Dental_Treatment_Plan__c custom object to hold procedure codes and treatment phase data. Appointments and completed visits map to Freshsales Events. Referral letters and clinical notes migrate as Notes attachments. The migration runs via CSV export from PANDA Perio's SQL Server database into Freshsales' bulk import API. Custom fields are pre-created before the migration run. A delta-pickup window captures any patient records modified during the cutover. FlitStack does not migrate PANDA letter templates, periodontal chart templates, or workflow automations — those require manual rebuild in Freshsales.

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.

Object mapping

How PANDA Perio objects map to Freshsales

Each row shows how a PANDA Perio object lands in Freshsales, 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

Freshsales

Contact

1:1

Fully supported

PANDA Perio patient records map 1:1 to Freshsales Contacts. Each patient becomes a Contact record with first name, last name, date of birth, contact phone numbers, email address, and home or mailing address. Original patient creation date is preserved as Original_Create_Date__c custom datetime field. Patients with multiple visits retain their full visit history as Events in Freshsales.

PANDA Perio

Patient Clinical Chart

maps to

Freshsales

Contact (custom fields)

1:1

Fully supported

PANDA Perio periodontal charting data — probing depths by tooth site, recession measurements, bleeding on probing (BOP), furcation involvement grades, and mobility grades — has no native Freshsales equivalent. Each charting dimension becomes a separate custom Number or Pick-list field on the Contact record (e.g., Most_Recent_Pocket_Depth_Avg__c, Furcation_Involvement__c, BOP__c). Historical charting visit dates are preserved as custom Date fields for longitudinal tracking.

PANDA Perio

Treatment Plan

maps to

Freshsales

Deal + Dental_Treatment_Plan__c (custom object)

1:1

Fully supported

PANDA Perio treatment plans with multiple phases, CDT procedure codes, tooth numbers, and healing intervals map to a Freshsales Deal representing the overall case, with a custom Dental_Treatment_Plan__c object storing individual procedure line items (procedure code, tooth site, phase, scheduled date, status). The Deal stage reflects the treatment plan's overall status (Consultation, Accepted, In Treatment, Completed, Lost).

PANDA Perio

Provider / Doctor

maps to

Freshsales

Contact

1:1

Fully supported

PANDA Perio provider profiles — periodontists, general dentists, dental hygienists — map to Freshsales Contacts with a custom Provider_Role__c pick-list field storing their credential type (Periodontist, DDS, DMD, RDH, Office Staff). Provider NPI numbers migrate as NPI__c custom field. Provider email addresses enable owner matching in Freshsales for treatment plan records they are assigned to.

PANDA Perio

Appointment / Visit

maps to

Freshsales

Event

1:1

Fully supported

PANDA Perio clinical visit appointments with date, time, provider, procedure type, and visit notes map to Freshsales Events linked to the patient Contact record. Event Subject reflects the visit type (Initial Consultation, Periodontal Maintenance, Surgical Procedure). Completed visit status maps to Freshsales Event status. Visit notes with clinical findings migrate as Notes attachments on the Event.

PANDA Perio

Referral Source (Referring Dentist)

maps to

Freshsales

Contact

1:1

Fully supported

PANDA Perio referral tracking — referring dentist name, practice name, referral date, and referral volume per source — maps to Freshsales Contacts flagged as referring dentists via a Referring_Dentist__c checkbox custom field. Practice name for the referring office stores in the Company field. Referral volume per dentist maps to a Referring_Dentist_Total_Referrals__c custom number field for tracking top referral sources in Freshsales reports.

PANDA Perio

Clinical Note / SOAP Note

maps to

Freshsales

Note (attachment)

1:1

Fully supported

PANDA Perio SOAP notes (Subjective, Objective, Assessment, Plan) and progress notes associated with each patient visit migrate as Freshsales Notes attached to the Contact record, with the Event (visit) as the parent context. Rich text formatting in PANDA notes is preserved where supported in the Note body. Original note creation timestamps are preserved.

PANDA Perio

Treatment Plan Letter

maps to

Freshsales

Note (attachment) + Email Template (manual rebuild)

1:1

Fully supported

PANDA Perio auto-generated treatment plan letters to patients and referring dentists migrate as PDF Notes attached to the Contact record. The letter content itself cannot be converted to Freshsales email templates automatically — the practice should export PANDA letter template definitions as a reference for rebuilding in Freshsales. Freshsales email templates for case acceptance and referral updates require manual creation post-migration.

PANDA Perio

Periodontal Classification

maps to

Freshsales

Contact (custom field)

1:1

Fully supported

PANDA Perio stages periodontal disease using the AAP classification system (Stage I-IV, Grade A-C). This classification maps to a custom pick-list field Periodontal_Stage__c on the Contact record, preserving the original staging date in a custom datetime field. Grade (A/B/C) maps to a separate Periodontal_Grade__c pick-list custom field.

PANDA Perio

Radiograph / Imaging Reference

maps to

Freshsales

File (attachment)

1:1

Fully supported

PANDA Perio stores references to radiograph imaging files and periapical X-rays linked to specific tooth sites. These file references migrate as Freshsales Files attached to the Contact record, with the imaging date stored in a custom Radiograph_Date__c field. Full-resolution imaging files are re-uploaded to Freshsales Files storage; size limits apply (Freshsales default 25MB per file).

PANDA Perio

Insurance / Billing Information

maps to

Freshsales

Contact (custom fields)

1:1

Fully supported

PANDA Perio insurance carrier, policy number, group number, and coverage percentage per procedure type map to custom fields on the Contact record (Insurance_Carrier__c, Policy_Number__c, Group_Number__c). Freshsales has no native insurance fields — these are stored as text custom fields for reference. Billing history beyond active coverage status is not migrated.

PANDA Perio

PANDA System User / Staff

maps to

Freshsales

Freshsales User

1:1

Fully supported

PANDA Perio staff user accounts (office managers, schedulers, billing staff) are Windows workstation-level user accounts, not contacts. These do not map to Freshsales Contacts. Staff who need CRM access are added as Freshsales Users by email invitation post-migration. Their historical activity logs in PANDA are not transferable.

PANDA Perio	Freshsales	Compatibility
Patient	Contact1:1	Fully supported
Patient Clinical Chart	Contact (custom fields)1:1	Fully supported
Treatment Plan	Deal + Dental_Treatment_Plan__c (custom object)1:1	Fully supported
Provider / Doctor	Contact1:1	Fully supported
Appointment / Visit	Event1:1	Fully supported
Referral Source (Referring Dentist)	Contact1:1	Fully supported
Clinical Note / SOAP Note	Note (attachment)1:1	Fully supported
Treatment Plan Letter	Note (attachment) + Email Template (manual rebuild)1:1	Fully supported
Periodontal Classification	Contact (custom field)1:1	Fully supported
Radiograph / Imaging Reference	File (attachment)1:1	Fully supported
Insurance / Billing Information	Contact (custom fields)1:1	Fully supported
PANDA System User / Staff	Freshsales User1:1	Fully supported

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

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

PANDA Perio gotchas		Freshsales gotchas
Severity	Issue	Severity	Issue
High	No public API — database extraction requires SQL Server access	Medium	Freddy AI is Pro-tier only despite heavy marketing
High	SQL Server Express 10GB limit can be migration-blocking	High	Post-migration emails and sequences are disabled
Medium	Open Dental bridge passes IDs only, not clinical data	Medium	Bot session credits are a one-time 500-session allocation
Medium	Treatment plan PMS codes differ from clinical letter descriptions	Medium	Phone credits charged per minute with no cap
Low	Custom periodontal findings are practice-specific	Low	File storage limits scale with plan tier

Pair-specific challenges

Periodontal charting data has no native Freshsales equivalent — plan your custom field schema before migration

PANDA Perio's core value proposition is its periodontal charting module: probing depths by tooth site, recession measurements, BOP, furcation involvement grades, and mobility classifications. Freshsales is a sales CRM with no clinical data objects — none of these fields exist natively. Each charting dimension must become a separate custom field on the Contact record (Pocket_Depth_Avg__c, BOP__c, Furcation__c, Mobility__c, Recession__c). The migration plan must enumerate every charting field your practice actively uses and pre-create the corresponding custom fields in Freshsales before data lands. Historical per-visit charting data is typically summarized to the most recent visit values rather than migrated per visit, due to the volume of tooth-site-level data. Decide upfront whether you need full longitudinal charting history or a current-state snapshot in Freshsales.
PANDA Perio uses a local SQL Server database — data export requires DBA-level access or PANDA admin export

PANDA Perio stores all patient records, clinical charts, treatment plans, and provider data in a SQL Server database (Express edition for small practices, Standard/Enterprise for larger setups). It has no native REST API and no cloud sync. The migration data source is either: (1) a SQL Server query export run by your PANDA administrator or IT team against the PANDA database, or (2) manual CSV exports from the PANDA Perio patient list and treatment plan screens. The SQL Server export route provides the most complete data including historical clinical charting records; the manual export route is limited to the fields available in the PANDA UI. If your PANDA installation is on a dedicated office server that your IT team manages, coordinate with them 2-3 weeks before the migration window to schedule the database export. FlitStack AI can work with either export format.
Treatment plan procedure codes (CDT codes) require a custom object in Freshsales — they do not map to standard Deal fields

PANDA Perio treatment plans store CDT (Current Dental Terminology) procedure codes, tooth site numbers, and treatment phase sequences as structured clinical data. Freshsales Deals have standard fields for deal name, amount, stage, close date, and owner — but no fields for procedure codes or dental treatment phases. The migration maps treatment plans to a Freshsales Deal (for case-level pipeline tracking: stage, amount, close date) plus a custom Dental_Treatment_Plan__c custom object (for procedure-level detail: CDT code, tooth site, phase, scheduled date, status). Creating a custom object in Freshsales requires the Pro or Enterprise plan. The migration plan must include custom object schema setup in Freshsales before the migration run. PANDA treatment plans with 10+ procedure line items will generate multiple Dental_Treatment_Plan__c records per Deal.
Letter templates and periodontal chart templates do not migrate — they require manual rebuild post-migration

PANDA Perio's instant letter writing module uses practice-specific letter templates that auto-populate with patient charting findings, diagnosis, and treatment plan details. These templates are stored in PANDA's template library and have no export mechanism. Similarly, PANDA periodontal chart templates (custom probing sites, classification settings, graphical report configurations) are PANDA-specific. Freshsales has no letter template auto-population feature — the practice must rebuild PANDA letter templates as Freshsales email templates (which support merge fields) or use Freshsales document generation integrations. Chart template configurations cannot be transferred and must be reconfigured manually within PANDA or abandoned in favor of Freshsales reporting. FlitStack AI can export the template field names and structure from PANDA as a reference document for the rebuild.
Referral tracking in PANDA requires a custom Contact field strategy in Freshsales — there is no native referral object

PANDA Perio tracks referring dentist names, practice names, referral dates, and referral volume per source as part of its referral management module. Freshsales has no native referral source object. The migration maps referring dentists to Freshsales Contacts with a Referring_Dentist__c checkbox, practice name stored in the Company field, and referral date and total referral count stored as custom fields. However, the many-to-many relationship between a referring dentist and multiple patient cases in PANDA cannot be fully represented in Freshsales without custom junction object logic. For practices where referral source tracking is a key revenue driver, the migration plan should include a custom Referral_Case__c junction object connecting the referring dentist Contact to patient Contact records, enabling Freshsales reports on referral-to-case conversion.

Migration approach

Six steps for a successful PANDA Perio to Freshsales data migration

Extract PANDA Perio data from SQL Server or UI export

FlitStack AI coordinates with your PANDA administrator or IT team to extract patient records, clinical charting data, treatment plans, provider profiles, appointments, and referral tracking from PANDA Perio's SQL Server database. For practices without database access, we guide the admin through PANDA's built-in export screens for patient lists and treatment plan reports. The extraction produces structured CSV files or a direct database connection string for FlitStack's migration engine. Custom charting fields unique to the practice (additional probing sites, custom classification schemes) are identified during this phase and added to the migration scope. This step typically requires 3-5 business days of coordination with the PANDA admin.
Design Freshsales custom field schema and custom object

Before any data moves, FlitStack AI creates a schema setup plan for all custom fields and the Dental_Treatment_Plan__c custom object in Freshsales. The plan enumerates every periodontal charting field (pocket depth, recession, BOP, furcation, mobility, periodontal stage/grade), every treatment plan detail field (CDT code, tooth site, phase), every insurance field, and every referral tracking field — with field type, pick-list values, and display label specified. For practices on Freshsales Growth plan, custom fields are supported but custom objects require an upgrade to Pro or Enterprise. The schema plan is delivered as a Freshsales field creation checklist so your admin can pre-create the fields, or FlitStack creates them via the Freshsales API on your behalf with your approval.
Run test migration with representative patient sample

A test migration runs against a sample of 50-100 patient records spanning a range of chart complexity — new patients, patients with active treatment plans, patients with historical charting data, and referring dentist records. FlitStack generates a field-level diff report comparing source values (PANDA charting fields) against destination values (Freshsales custom fields) so the practice can verify periodontal stage mapping, CDT code transfer, referral count accuracy, and provider email matching. Treatment plan Deal creation and custom object record generation are validated during this step. Any missing custom fields or value mapping gaps are corrected before the full migration run. Test migration findings are reviewed in a 30-minute call with the practice manager.
Execute full migration with delta-pickup window

The full migration loads all PANDA patient records, provider profiles, appointments, treatment plans, referral records, and clinical charting data into Freshsales. Data loads via Freshsales bulk CSV import API with custom field population via the Freshsales API for non-standard fields. A delta-pickup window of 24-48 hours runs in parallel with the go-live cutover, capturing any patient records modified in PANDA during the migration window (new appointments, updated treatment plans). After the delta pickup, FlitStack generates a reconciliation report showing record counts by object, custom field population rates, and any records that failed to load with error reasons. One-click rollback reverts all migrated records if reconciliation uncovers data integrity issues.
Rebuild letter templates and automations with FlitStack reference documentation

FlitStack AI does not migrate PANDA letter templates, periodontal chart templates, or workflow automations — these require manual rebuild in Freshsales. As part of the migration package, FlitStack delivers a Letter Template Reference Document that captures the field names, merge field syntax, and conditional logic from PANDA's template library (where exportable), plus a Workflow Rebuild Checklist for any appointment reminder or treatment plan milestone automations configured in PANDA. The practice's Freshsales admin uses these documents to recreate letter templates as Freshsales email templates and automate treatment plan follow-ups using Freshsales Workflows. FlitStack's support team is available for a 1-hour consultation call to review the rebuild approach.

Platform deep dives

Context on both ends of the pair

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.

Freshsales

Destination

Strengths

Generous free tier for small teams with core CRM functionality without per-seat costs.
All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
Freddy AI contact scoring and deal predictions available on Pro tier.
Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

Reports lack depth compared to competitors like HubSpot, with limited customization options.
Integration setup is poorly documented with no clear guides for connecting third-party tools.
AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
Bot sessions limited to 500 one-time allocation with no monthly refresh.

	PANDA Perio Source	Freshsales Destination
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.	Generous free tier for small teams with core CRM functionality without per-seat costs. All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency. Freddy AI contact scoring and deal predictions available on Pro tier. Multiple pipeline views with Kanban and list options across all plans.
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.	Reports lack depth compared to competitors like HubSpot, with limited customization options. Integration setup is poorly documented with no clear guides for connecting third-party tools. AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI. Bot sessions limited to 500 one-time allocation with no monthly refresh.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from PANDA Perio to Freshsales

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

PANDA Perio

Freshsales

How PANDA Perio objects map to Freshsales

What specifically takes care here

Six steps for a successful PANDA Perio to Freshsales data migration

Context on both ends of the pair

How hard is this migration?

Estimate your PANDA Perio to Freshsales migration cost

What are you migrating?

Frequently asked questions about PANDA Perio to Freshsales data migrations

Can't find your answer?

Related migrations to explore

Move from PANDA Perio.
Land in Freshsales, intact.

Migrate from PANDA Perio to Freshsales

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

PANDA Perio

Freshsales

How PANDA Perio objects map to Freshsales

What specifically takes care here

Six steps for a successful PANDA Perio to Freshsales data migration

Context on both ends of the pair

How hard is this migration?

Estimate your PANDA Perio to Freshsales migration cost

Frequently asked questions about PANDA Perio to Freshsales data migrations

Can't find your answer?

How long does a PANDA Perio to Freshsales migration take?

Will my PANDA Perio letter templates and workflow automations migrate to Freshsales?

What happens to my periodontal charting data (probing depths, BOP, furcation) in Freshsales?

Can I migrate PANDA Perio treatment plans with CDT procedure codes to Freshsales?

How does PANDA Perio referral tracking map to Freshsales?

Does the migration affect my PANDA Perio account during the cutover?

What Freshsales plan do I need to migrate all my PANDA data?

How do I export data from PANDA Perio if I only have the desktop application?

Related migrations to explore

Move from PANDA Perio. Land in Freshsales, intact.

Move from PANDA Perio.
Land in Freshsales, intact.