Migrate from Pearl Dental Software to Pipedrive

Pearl patient records map directly to Pipedrive People. Name, email, phone, mobile, and address fields transfer as standard Pipedrive Person fields. Medical-alert flags, NHS/private classification, and referring-dentist fields migrate as custom Person fields because Pipedrive has no native clinical-history equivalent.

Pearl stores address as separate line1/line2/city/county/postcode fields. These map to Pipedrive's formatted address sub-field set on the Person record. County and country are stored as custom fields where postcode-to-county mapping is required, since Pipedrive does not run address validation automatically during import. The full structured address is visible on the Person profile in Pipedrive after migration.

Pearl treatment plans become Pipedrive Deals. The treatment-plan title generates the Deal name. Total plan cost maps to Deal value. Plan status (Active, Complete, Cancelled) maps to Pipedrive deal status and a custom pipeline-stage mapping. Each treatment plan is one Deal in Pipedrive regardless of how many line items it contains.

Pearl treatment stages (Examination, Diagnosis, Treatment Proposed, Treatment In Progress, Treatment Complete, Review) map to Pipedrive pipeline stage values. Each stage gets a probability value and a forecast category applied in Pipedrive. The mapping table is delivered in the migration plan before the full run.

Individual treatment line items (extractions, fillings, crowns, hygiene visits) migrate as Pipedrive Products. Product name, description, and price transfer. Products are linked to the parent Deal via a deal-product association, allowing Pipedrive to show per-treatment breakdown on the Deal record.

Pearl's tooth-chart data (which teeth have which findings) has no native Pipedrive equivalent. FlitStack creates a custom multi-select field (Tooth_Chart__c) on Person to store affected tooth numbers as comma-separated values. Detailed clinical findings transfer as Notes with a custom Tooth_Number__c field on the Note so context is preserved.

Pearl appointments map to Pipedrive Activities. Appointment type (Check-up, Hygiene, Treatment, Emergency) maps to Activity type. Scheduled appointments become Events with start/end times. Recall appointments become Tasks with a due date. Provider (dentist) assignments resolve by email match to Pipedrive users — unmatched providers are flagged before migration.

Pearl free-text chart notes migrate as Pipedrive Notes attached to the Person record. The Note body preserves the original clinical text. A custom field (Note_Timestamp__c) stores the original Pearl note date and provider so the clinical timeline is retained in Pipedrive.

Pearl provider records are matched to Pipedrive users by email address. Where no email match exists in Pipedrive, the provider name is stored in a custom field (Treating_Dentist__c) on the Deal record. This ensures no provider assignment is silently dropped during migration. The custom field approach preserves provider visibility even when the provider does not have an active Pipedrive user account at migration time.

Pearl stores a referring-dentist reference on patient records. Where the referrer has a practice name, FlitStack creates a Pipedrive Organization and links it via a custom field (Referring_Dentist_Org__c) on the Person. If no practice name exists, the referrer name is stored as a text custom field (Referring_Dentist__c).