Migrate from PANDA Perio to Twenty CRM

PANDA's patient record maps directly to Twenty's People object without transformation logic. Patient name, date of birth, contact phone, email address, and physical address fields translate on a 1:1 field basis. Insurance carrier, policy number, group number, and coverage percentage data migrate as custom fields appended to the People record. Referral source information similarly maps to a custom field, preserving the original referring dentist or practice name.

PANDA's periodontal examination data — pocket probing depths (6 sites per tooth), recession, clinical attachment level, furcation involvement, and tooth mobility — requires a custom Perio Exam object in Twenty. Each exam record links to a People record via a relation field. The 200+ clinical finding fields map to custom number, select, and text fields within the Perio Exam object.

PANDA treatment plans structured by procedure phases (extraction, bone graft, implant placement, restoration) transform into a custom Treatment Plan object linked to People. Each phase becomes a child record or a multi-select field on the Treatment Plan, preserving procedure codes, tooth numbers, and phase descriptions.

PANDA's progress notes and clinical notes migrate to Twenty's Notes object. Each note links to the associated People record and retains the original author (provider), creation timestamp, and formatted note content. Rich-text formatting from PANDA converts to Twenty's note body format.

PANDA's auto-generated correspondence letters have no direct Twenty equivalent. We preserve generated letter content as Notes linked to People records for reference. The letter template logic (dynamic field substitution from exam findings) must be rebuilt using Twenty's workflow builder or documented for external letter generation.

PANDA provider records (dentist name, credentials, NPI number) map to Twenty's People object with a 'Role' custom field set to 'Provider'. Provider-to-patient associations are preserved via the People-to-People relation where needed, or through the Perio Exam custom object linking patient to provider.

PANDA insurance carrier, policy number, group number, and coverage percentages migrate as custom fields on the People record. Dental insurance is a flat structure in PANDA — no separate object — so we flatten it into People-level custom fields rather than creating a related object.

PANDA referral source (referring dentist name, practice) merges into two Twenty fields: a custom 'Referral_Source__c' text field on People for the individual, and a Companies record created for the referring practice if not already present. This enables tracking both individual referrals and practice-level referral networks.

PANDA appointment records containing appointment date, assigned provider, procedure type, and operatory assignment map directly to Twenty Tasks linked to People records via the personId relation field. The task title captures the procedure type and date, while task status maps from PANDA's appointment outcome flags: Completed, No-Show, Cancelled, or Rescheduled values translate into Twenty's task status select options, preserving the full appointment history and outcome for each patient.

PANDA's ADA billing codes (D7210, D7953, etc.) attached to treatment plan phases migrate as a custom multi-select or text field on the Treatment Plan custom object. These are reference values only — PANDA Perio does not handle billing, so no accounting mapping is required.

The practice's own organization details, including practice name, primary business address, phone number, and National Provider Identifier (NPI), migrate as a Companies record in Twenty. This Companies record serves as the primary organization entry for the workspace, establishing the practice as an entity within the CRM. For multi-location dental practices, FlitStack creates a separate Companies record for each physical practice location, enabling location-level tracking of patients, providers, and appointments while maintaining a unified view across the organization.

PANDA's multi-visit comparison charting (viewing up to 5 visits simultaneously, adjusting baseline post-surgically, graphical comparison of probing and mobility) requires a custom Perio Comparison object. Each comparison links multiple Perio Exam records and stores the baseline exam reference as a relation field.