Migrate from Curve Dental to Pipedrive

Curve Dental patient demographics — name, email, phone, address — map directly to Pipedrive Person fields. Primary provider assignment stores in a custom Person field. Curve patients without email receive a placeholder address flagged for manual review before migration commits.

Curve's responsible party contact (guarantor) migrates as a separate Pipedrive Person record linked to the patient Person via a custom relationship field. Primary flag indicates whether this person is the patient themselves or a guardian/guarantor.

For group practices, the practice or DSO entity stores as a Pipedrive Organization. Individual solo-practice patients typically have no separate organization record; the Organization field on Person is left blank or assigned to a default 'Individual Patient' org.

Each Curve Dental treatment plan becomes a Pipedrive Deal. The deal name uses the patient name plus plan date. Treatment plan status (Presented, Accepted, In Progress, Completed, Declined) maps to Pipedrive deal stage values via value-by-value mapping. Estimated fee migrates to deal value.

Individual procedure line items — ADA code, tooth number, surface, fee, date, provider — migrate as Pipedrive Activity notes with custom fields capturing the procedure code and clinical detail. Multiple procedures on one treatment plan create multiple activity entries linked to the parent Deal.

Past appointments (date, type, provider, status) migrate as Pipedrive Activity tasks with due dates matching the original appointment date. The activity subject uses the appointment type. Cancelled and no-show appointments receive a separate activity status flag via custom field.

Curve Dental hygiene recall dates and specialty follow-up dates have no native Pipedrive equivalent. We create custom date fields on the Person object (Recall_Date_Hygiene__c, Recall_Date_Specialty__c) and populate them from Curve patient properties. Automated recall sequences must be rebuilt as Pipedrive automation triggers on these date fields.

Insurance carrier name, group number, subscriber ID, and eligibility verification status map to custom text fields on the Pipedrive Person record. Separate insurance carrier organizations can be linked via Organization relationship if the practice tracks carriers as reusable entities.

Curve Dental provider and staff user accounts resolve to Pipedrive users by email match. Unmatched providers are flagged as inactive or mapped to a migration-service owner until the practice creates Pipedrive user accounts for all active staff.

Curve Dental custom patient properties and treatment plan fields that practices have created over time must be individually inventoried. Each custom field receives a corresponding Pipedrive custom field of matching type (text, date, picklist, number). Custom fields without a Pipedrive equivalent are preserved as text for reference.

Curve Dental referral source fields (Referring Doctor, Marketing Source) map to Pipedrive custom picklist fields on Person. Picklist values are mapped one-by-one; unmapped values default to a generic 'Other' option for admin review.

Curve Dental clinical chart notes and periodontal charting data have no CRM equivalent in Pipedrive. We export these as attached text files or PDF references linked to the patient Person record. Clinical documentation should remain in a dental clinical system or be referenced manually.

Curve Dental x-ray and imaging files are not migrated to Pipedrive's file storage (5–100 GB per Pipedrive plan). Imaging should remain in Curve Dental or a dedicated imaging/DICOM system. Pipedrive's file attachments work for documents and PDFs but are not designed for radiographic image libraries.

Insurance claim submission history and status tracking inside Curve Dental has no Pipedrive equivalent. Claim records should remain in Curve Dental or a dedicated dental billing system. Pipedrive Deal records can reference a claim ID as a custom field for cross-system lookup but cannot replicate claim lifecycle tracking.