Migrate from PANDA Perio to Microsoft Dynamics 365 Sales

PANDA Perio patient records map directly to Dynamics 365 Contacts. Patient demographics including name, date of birth, contact information, address, and phone numbers translate directly to Contact standard fields. Primary provider assignment resolves to Contact OwnerId via email match against Dynamics system users. Chart numbers and billing types from PANDA Perio migrate to custom fields on the Contact record for clinical reference and practice management integration.

When PANDA Perio stores referring dental practice or employer information, those entities map to Dynamics 365 Accounts. The referring practice name, address, and contact details populate Account standard fields. Personal patients map to Contacts without an Account link; business-referred patients create an Account record representing the referring practice with a lookup relationship from the patient Contact record.

PANDA Perio stores guarantor information per patient for billing responsibility tracking. The guarantor maps to the same Contact record structure, with a parent-contact relationship established in Dynamics 365 when multiple family members are migrated together. This preserves family billing hierarchies while maintaining individual Contact records for each family member.

PANDA Perio treatment plans contain procedure codes, phases, clinical notes, and status tracking. Dynamics 365 has no native treatment plan entity. We create a custom TreatmentPlan table in Dataverse to store plan headers including plan number, date, status, and provider assignment. Procedure line items map as child records in a linked TreatmentPlanProcedure table with procedure codes, tooth-site references using universal numbering, and fee information.

Each PANDA Perio visit containing periodontal charting (pocket depths, BOP, furcation, mobility) maps to a custom PerioVisit table linked to the Contact via a lookup relationship. Charting data for each tooth-site stores as JSON or delimited custom fields since Dynamics 365 does not support dental chart grid structures natively. Visit dates, provider assignments, and clinical findings are preserved for historical reference and treatment outcome tracking.

PANDA Perio clinical progress notes and SOAP notes migrate to Dynamics 365 Annotations attached to the Contact record. Note dates become Annotation Subject lines for chronological organization, while note body content populates the Annotation Body field. Rich-text formatting is preserved where possible; complex formatting converts to plain text with HTML markup retained for readability and reference purposes.

PANDA Perio's dynamic letter templates with provider-specific phrasing and conditional logic cannot migrate directly to Dynamics 365. We export template definitions as reference documentation including field names, conditional logic patterns, provider signature blocks, and procedure code references. This documentation accelerates rebuilding via Dynamics 365 Word Templates or Power Automate. Existing sent letters are preserved as PDF attachments on the Contact record.

PANDA Perio chart flags including recare needed, treatment incomplete, and referral pending statuses map to Dynamics 365 Tasks with appropriate category and due date assignments. The original flag type is preserved in a custom Contact field (Workflow_Flag__c) for filtering, reporting, and bulk operations. Task subjects reference the flag type and patient name for clear identification in the Dynamics 365 timeline view.

PANDA Perio file attachments including images, X-rays, consent forms, and clinical photographs re-upload to Dynamics 365 SharePoint integration or Dataverse file columns attached to the Contact record. SharePoint document libraries provide scalable storage for large attachment volumes with folder structures mapped to match PANDA Perio organization. File size limits of 125 MB per file apply in Dataverse native storage; SharePoint integration bypasses this limitation for very large imaging files.

PANDA Perio providers and doctor records resolve to Dynamics 365 system users via email address matching. This OwnerId assignment links patient records to their responsible provider in Dynamics 365. Unmatched providers are flagged in a resolution report for manual user creation or reassignment to a default provider Contact record. Proper owner resolution ensures record visibility, task assignment, and accountability tracking in Dynamics 365.

PANDA Perio visit dates, providers, procedure codes, and visit types map to a custom Appointment entity linked to Contact. The custom entity stores structured visit metadata while maintaining relationship context. Visit-level activities including examinations, surgeries, and consultations also create Dynamics 365 Activity records for timeline visibility and workflow automation triggers. Historical appointments are preserved for recall reminders and treatment history review.

PANDA Perio insurance carrier names, policy numbers, group numbers, and coverage details map to a custom InsuranceInfo table linked to Contact. Insurance company names create or link to Account records for carrier reporting and communication tracking. The custom entity stores complete policy details while the Account link provides carrier-level aggregation for claims reporting, coverage analysis, and provider network verification within Dynamics 365.